opencbm-user Mailing List for OpenCBM
Brought to you by:
strik
You can subscribe to this list here.
2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(3) |
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2005 |
Jan
(3) |
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(18) |
Nov
(12) |
Dec
|
2008 |
Jan
(1) |
Feb
(6) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(16) |
2009 |
Jan
(5) |
Feb
(5) |
Mar
(3) |
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
(3) |
Oct
(17) |
Nov
(43) |
Dec
(9) |
2010 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
(4) |
Jun
|
Jul
(4) |
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
(2) |
2011 |
Jan
(11) |
Feb
(14) |
Mar
(3) |
Apr
(4) |
May
(1) |
Jun
|
Jul
|
Aug
(1) |
Sep
(1) |
Oct
(5) |
Nov
|
Dec
(1) |
2012 |
Jan
(21) |
Feb
|
Mar
|
Apr
(5) |
May
(32) |
Jun
(20) |
Jul
(5) |
Aug
|
Sep
|
Oct
(3) |
Nov
(5) |
Dec
|
2013 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
(4) |
Jul
|
Aug
|
Sep
(18) |
Oct
(7) |
Nov
|
Dec
(3) |
2014 |
Jan
|
Feb
(13) |
Mar
(6) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(3) |
2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(4) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2016 |
Jan
|
Feb
(2) |
Mar
(4) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(8) |
Dec
(1) |
2017 |
Jan
(1) |
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
(13) |
Sep
|
Oct
(3) |
Nov
(2) |
Dec
|
2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(9) |
Dec
|
2019 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
2020 |
Jan
|
Feb
(7) |
Mar
|
Apr
(14) |
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
(6) |
Oct
|
Nov
|
Dec
|
2021 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
(4) |
Oct
|
Nov
|
Dec
|
2022 |
Jan
(3) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2024 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(24) |
Jul
(4) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Myke C. <AdminDev@MykeC.net> - 2024-07-23 20:13:52
|
One other lesson I learned along the way: After the 1571 attempt had failed and I resigned myself to using 1541 format for this breakdown / reassemble process... my instinct was to use FORMAT.COM's "C64 Single-Sided Disk" option because I really didn't know what a "C128 Single-Sided Disk" even is. But I found out. I know that in CP/M, a freshly-formatted 1571 disk has 336k free. So I was surprised to see only 129k free after having formatted a disk using the "C64 Single-Sided" option. I went with it anyway... only to find "Big Blue Reader 128" doesn't recognize that format. By that I took a clue that the difference between "C64 Single-Sided" and "C128 Single-Sided" disks is... the C64 format uses GCR which the 1541 understands. The "C128 Single-Sided" format uses MFM which "Big Blue Reader 128" recognizes without issue. So after reformatting all of those disks one more time as "C128 Single-Sided" disks... the planets aligned and harmony filled the universe. Myke |
From: Myke C. <su...@my...> - 2024-07-23 19:22:59
|
The workflow I used which solve the problem: Each of my 5 CP/M 1581 disks contain about 5 sides worth of 1541 data. So I used CP/M's FORMAT.COM to format *five* 5.25" floppies as *C128 Single-Sided" disks. Then I used "Big Blue Reader 128" to file-copy all of the files from one CP/M 1581 diskette to the 5 CP/M single-sided 1571 diskettes. Then I used OpenCBM's "nibread" to rip each single-sided diskette as a .G64 image. Then in VICE, I used "Big Blue Reader 128" to file-copy the files from each .D64 image back into a single CP/M-formatted .D81 image. Then I did this same breakdown / recombination technique 4 more times to have my 5 original 1581 CP/M floppies as .D81s in VICE. Yes, it took all day to do this but it worked. Lessons learned along the way: It was important to choose the "single-sided" format option because "nibbling" these disks is necessary to complete the task and I don't find that available for anything other than single-sided floppies. I first attempted to copy each CP/M 1581 source disk to three CP/M 1571 disks... but sometimes (but not always) the random binary "garbage" appearing in CBM's directory Track 18 would cause OpenCBM's "d64copy" to "hang" and never start copying the disk. That's the reason why nibbling single-sided disks was required. It's also important to know when using CP/M's FORMAT.COM to format C128 Single-sided disks... you must not flip the disk and format Side B as yet another C128 Single-sided disk. Even though it's a single-sided formatting operation... FORMAT.COM still formats all 70 tracks on both sides of the physical disk. When doing Single-sided formats... you must literally treat each disk as a single-sided floppy - totally unlike what is normal in the standard CBM floppy world. This was my first time working with the Single-sided format option. I've never needed it before and, quite honestly never understood its purpose and value... until now. Myke |
From: Myke C. <su...@my...> - 2024-07-21 17:44:02
|
This is really odd. I have *six* .d81 images of CP/M-formatted 3.5" disks with datestamps from July 13th/14th - just 8 days ago. One of them is an intentionally blank CP/M .d81 for the purpose of easily creating a fresh work disk by simply copying and renaming the image. When I write that image to a physical floppy, there's no issue. When I attempt to immediately read that very same physical floppy, I get an immediate "[Fatal]" error message before the drive has even attempted to read the disk. Here is the command line I'm running in Linux which gives me this error: imgcopy -v --no-warp -t -s -2 -d 1581 8 test.d81 Now, I will admit... at times I have been working with "Big Blue Reader 128" when copying some CP/M files from disk-to-disk. Perhaps I created a blank, standard .d81... and formatted it for CP/M in VICE... and then copied the files to those .d81s from .d71 images using either PIP.COM or BBR-128 and I just don't remember that's how I did it? I don't remember doing that. Regardless, I'm not having any success with imaging a physical 1581 floppy formatted for CP/M on my real C128... yet the same command line works perfectly with all my standard CBM-formatted 1581 disks. Hmmmm... I'll keep experimenting with it until hopefully I find something which works. Myke |
From: Myke C. <su...@my...> - 2024-07-21 01:20:07
|
Hello, Yesterday I found a set of 5 CP/M 1581 disks I'd prepared for myself back in the late 1990s. I noticed they still have the old DATE.COM on them which isn't Y2K-OK. So I thought I'd just make some .D81s from them and make the necessary revisions in VICE on my Linux box since that would be the fastest, easiest way for me to fix that little problem right now. But when I tried to create the image, it failed... because CP/M formats a 1581 disk differently from how it formats with a 1571? All I'm seeing with these is a single, small USR file... which looks nice compared with seeing whatever random binary content happens to reside on what would normally be the directory track... but it also seems to be making it "impossible" to image the disk as well. What am I missing here? Myke |
From: Myke C. <su...@my...> - 2024-06-17 17:37:51
|
VICE needed 4 libraries installed before it would fully compile on my Linux Mint box. Had to do a small amount of Googlin' to find a couple of them but after that... the installation procedure was as smooth as silk! $ c1541 headisk-monster-vii.side0.big-disk.in-effect-mode.d64 -list 0 "in effect mode " aa 2a 180 "flash" prg< 74 "laserwaves" prg< 25 "max headroom" prg< 8 "new year's 1989" prg< 68 "skate or die!" prg< 2 "strobe.bas" prg< 1 "strobe.ml" prg< 1 "strobe.ml.boot" prg< 85 "tubular bells" prg< 89 "vincent" prg< 0 "................" usr 7 "load" prg< 124 blocks free. Perfeito! Que legal! Muitobrigado! :) That's so awesome! Thanks Uffe, Myke On 6/14/24 19:50, Uffe Jakobsen wrote: > Myke Carter writes: >> >> More than anything right now, I would like to know if there's a way to >> list the directories of these .d64 and .d71 images I made yesterday >> from the command line without requiring me to actually use them in >> VICE or whatever. I used to keep VICE for both 64 and 128 installed >> on my Linux box but with a PC keyboard, no C= joysticks and no virtual >> disks to load... I couldn't do much more than stare at the "READY." >> screens. >> > > VICE releases should contain the "c1541" binary > > The c1541 binary allows you to list the contents of a disk image file in > a terminal/DOS box window (without starting VICE) > > The command syntax is like this: > > c1541 <disk-image-file-name> -list > > Example command and output: c1541 NeosCheesePaintV2Joy.d64 -list > 0 "neos cheesepaint" 64 2a > 35 "cheese v2 joy2" prg > 81 "a.che" prg > 81 "b.che" prg > 81 "c.che" prg > 81 "d.che" prg > 81 "e.che" prg > 81 "f.che" prg > 126 blocks free. > > For more options try: c1541 -help > > /Uffe |
From: Myke C. <su...@my...> - 2024-06-16 19:24:13
|
On 6/14/24 15:57, Kate Lawson wrote: > You should probably gently clean the disk heads if getting new read errors after it worked for a while. Hi Kate. I took your advice and also watched this video on YouTube for exactly how to do that. https://www.youtube.com/watch?v=ph3LIP7JqQ8 I've always used a 5.25" head cleaning disk in the past. I didn't previously realize how to do that with a Q-tip and 91% Isopropyl alcohol like I use to keep my Pioneer cassette deck's head clean. So this helped me to at least get my 1571 back to a state of being able to read Track 18 and show me a directly listing again. It's still extremely temperamental, though, and wants to throw curveballs at me every other disk with "27" and/or "21" read errors or "74" drive not ready reports. Very frustrating. Additionally, even though I can get the drive to respond and show directory listings... It *still* will not successfully read disks which I know are in perfectly fine condition. I've learned how to issue the "i" and "i0" commands using "cbmctrl". I've also used that to format one particular disk I know was previously formatted and empty. Doing that helps to get the head back on track for about 1 or 2 directory reads before the drive lapses back into Problemsville. And still it fails to not give me read errors now every time I try to create a new image. And my 1541-II is just non-responsive now for whatever reason... So I'm looking at options for buying new, refurb'd hardware. Got some good choices there. I will most likely buy two - possibly 3 - 1571s and send my current drives in for repair while I'm proceeding with the news ones to get these boxes and boxes of floppies virtualized. See anything else I might possibly try before I do all of that? Myke |
From: Myke C. <su...@my...> - 2024-06-15 17:49:45
|
Thank you for that suggestion. I've never heard of v1541commander before. There are so many things which have been developed - both software and hardware - while I've been away. My head is spinning! haha Having used Linux for 25-years, I love my "bash" command line utilities when they're clearly the better choice but I've always used a blend of both GUI and CLI with both Linux and my Commodores. I'll definitely give it my consideration! Thanks. Myke On 6/15/24 13:20, Uffe Jakobsen wrote: > Myke Carter writes: >> OK. Thanks! It's been awhile since I last installed and ran VICE on >> my Linux box. This weekend, I would do well to try and get that >> running again so I can do this. > > If you are looking for something with graphical UI - similar to DirMaster > > v1541commander is available for both Linux and Windows > > https://csdb.dk/release/?id=187433 > > /Uffe |
From: Uffe J. <uf...@uf...> - 2024-06-15 17:20:57
|
Myke Carter writes: > OK. Thanks! It's been awhile since I last installed and ran VICE on my > Linux box. This weekend, I would do well to try and get that running again > so I can do this. > If you are looking for something with graphical UI - similar to DirMaster v1541commander is available for both Linux and Windows https://csdb.dk/release/?id=187433 /Uffe |
From: Myke C. <su...@my...> - 2024-06-15 00:42:11
|
Wow... Thanks! I've never heard of DirMaster before. I've bookmarked that for future reference. I do have a Win10 laptop but usually I keep it over in a dark corner with its power off. :) I was a solid ComMoDore enthusiast from 1988-1999 (I highlight "CMD" in that name because without them, I'd have most likely been unable to continue using my C64c and C128D for as long as I did. Even then I despised Windows. I first heard of Linux in 1997. My Commodores required me to acquire basic Unix shell commands because in those days, using an ISP's Unix shell account was my only way to access the Internet with my Commodores at home. So when I was effectively forced by a 1999 career change to buy a common "PeeCee", I insisted on setting it up as a Linux / Windows dual-boot system. I loved Linux from the start. I've despised Microsoft as far back as I can remember. And to this day, nothing's changed. Many times I tell people when they ask me why I like Linux so much... I tell them "Linux has a personality which is the closest to Commodore's personality I've ever found on standard PC hardware." So... whatever I do, I'm going to try to make it work on Linux first. And then if that can't be done, I'll consider the Windoze route. Thanks, though. I'm curious to know what's available so I can make the best decisions. Myke On 6/14/24 19:58, Kate Lawson wrote: > The c1541 utility can give you virtual access to a d64, list files, copy them into or out of the image. But you might be better off with a GUI utility like DirMaster. > > https://style64.org/dirmaster |
From: Myke C. <su...@my...> - 2024-06-15 00:31:46
|
OK. Thanks! It's been awhile since I last installed and ran VICE on my Linux box. This weekend, I would do well to try and get that running again so I can do this. Excellent reply and fast too! I appreciate it. Myke On 6/14/24 19:50, Uffe Jakobsen wrote: > > VICE releases should contain the "c1541" binary > > The c1541 binary allows you to list the contents of a disk image file in > a terminal/DOS box window (without starting VICE) > > The command syntax is like this: > > c1541 <disk-image-file-name> -list > > Example command and output: c1541 NeosCheesePaintV2Joy.d64 -list > 0 "neos cheesepaint" 64 2a > 35 "cheese v2 joy2" prg > 81 "a.che" prg > 81 "b.che" prg > 81 "c.che" prg > 81 "d.che" prg > 81 "e.che" prg > 81 "f.che" prg > 126 blocks free. > > > For more options try: c1541 -help > > /Uffe > > > _______________________________________________ > opencbm-user mailing list > ope...@li... > https://lists.sourceforge.net/lists/listinfo/opencbm-user |
From: Kate L. <ka...@ro...> - 2024-06-14 23:58:43
|
The c1541 utility can give you virtual access to a d64, list files, copy them into or out of the image. But you might be better off with a GUI utility like DirMaster. https://style64.org/dirmaster > On Jun 14, 2024, at 1:33 PM, Myke Carter <AdminDev@MykeC.net> wrote: > > More than anything right now, I would like to know if there's a way to list the directories of these .d64 and .d71 images I made yesterday from the command line without requiring me to actually use them in VICE or whatever. I used to keep VICE for both 64 and 128 installed on my Linux box but with a PC keyboard, no C= joysticks and no virtual disks to load... I couldn't do much more than stare at the "READY." screens. |
From: Uffe J. <uf...@uf...> - 2024-06-14 23:50:52
|
Myke Carter writes: > > More than anything right now, I would like to know if there's a way to list > the directories of these .d64 and .d71 images I made yesterday from the > command line without requiring me to actually use them in VICE or whatever. > I used to keep VICE for both 64 and 128 installed on my Linux box but with a > PC keyboard, no C= joysticks and no virtual disks to load... I couldn't do > much more than stare at the "READY." screens. > VICE releases should contain the "c1541" binary The c1541 binary allows you to list the contents of a disk image file in a terminal/DOS box window (without starting VICE) The command syntax is like this: c1541 <disk-image-file-name> -list Example command and output: c1541 NeosCheesePaintV2Joy.d64 -list 0 "neos cheesepaint" 64 2a 35 "cheese v2 joy2" prg 81 "a.che" prg 81 "b.che" prg 81 "c.che" prg 81 "d.che" prg 81 "e.che" prg 81 "f.che" prg 126 blocks free. For more options try: c1541 -help /Uffe |
From: Myke C. <su...@my...> - 2024-06-14 20:33:15
|
On 6/14/24 15:57, Kate Lawson wrote: > You should probably gently clean the disk heads if getting new read > errors after it worked for a while. Hi Kate. Thanks for that reminder. :) All my C= gear has basically been in climate-controlled storage at U-Haul since 1999. I do recall having a 5.25" floppy drive head cleaning diskette which used to work well with a couple drops of that 91% isopropyl alcohol added to it. Other than that, I don't recall how to clean the heads on these drives. They're not openly accessible even when the cases are opened. > For backing them up, it’s faster to use nibread and then “nibconv > FILE.nib FILE.d64”. It is more tolerant of errors than d64copy and > you can also set the retries higher just in case the disk is a little > dirty and subsequent passes succeed. I've seen mention of these "nibread" and "nibconv" tools but they're not in my /usr/local/bin directory... so I'm guessing they're not available as part of OpenCBM? There are so many little details to learn all at the same time every time I start to do this... it gets overwhelming. :) More than anything right now, I would like to know if there's a way to list the directories of these .d64 and .d71 images I made yesterday from the command line without requiring me to actually use them in VICE or whatever. I used to keep VICE for both 64 and 128 installed on my Linux box but with a PC keyboard, no C= joysticks and no virtual disks to load... I couldn't do much more than stare at the "READY." screens. My 1571 stopped reading disks yesterday. It got so far and suddenly stopped. I only have one of them. I think I need to knock its head back on track but I don't remember the command for doing that and I don't even have my Commodores setup, plugged in and turned on just yet to issue it even if I did know. I tried my 1541-II but it's apparently not reading disks either. It comes on and just sits there looking prettier than an original 1541. So I tried my original 1541, too, and it just sits there and does nothing either. This is the trouble I had 11 years ago when I bought my ZoomFloppy and tried doing this in 2013. So I'm 3 for 3 at the moment... with none of my drives working for making more disk images. And none of my four 1581s are good for this either. I keep reading online for options that work with 1581 floppies because I have a lot of those too. Looks like I'm going to need to find and buy an internally mountable 3.5" floppy drive for my Linux box because my USB 3.5" drive doesn't have what it needs either. Too many things failing at the same time are exactly why I had to abandon this effort before. This time, however, I'm seriously considering paying for some repairs or like-new refurbs. It's getting ridiculous. Myke |
From: Myke C. <AdminDev@MykeC.net> - 2024-06-14 20:32:08
|
On 6/14/24 15:57, Kate Lawson wrote: > You should probably gently clean the disk heads if getting new read > errors after it worked for a while. Hi Kate. Thanks for that reminder. :) All my C= gear has basically been in climate-controlled storage at U-Haul since 1999. I do recall having a 5.25" floppy drive head cleaning diskette which used to work well with a couple drops of that 91% isopropyl alcohol added to it. Other than that, I don't recall how to clean the heads on these drives. They're not openly accessible even when the cases are opened. > For backing them up, it’s faster to use nibread and then “nibconv > FILE.nib FILE.d64”. It is more tolerant of errors than d64copy and > you can also set the retries higher just in case the disk is a little > dirty and subsequent passes succeed. I've seen mention of these "nibread" and "nibconv" tools but they're not in my /usr/local/bin directory... so I'm guessing they're not available as part of OpenCBM? There are so many little details to learn all at the same time every time I start to do this... it gets overwhelming. :) More than anything right now, I would like to know if there's a way to list the directories of these .d64 and .d71 images I made yesterday from the command line without requiring me to actually use them in VICE or whatever. I used to keep VICE for both 64 and 128 installed on my Linux box but with a PC keyboard, no C= joysticks and no virtual disks to load... I couldn't do much more than stare at the "READY." screens. My 1571 stopped reading disks yesterday. It got so far and suddenly stopped. I only have one of them. I think I need to knock its head back on track but I don't remember the command for doing that and I don't even have my Commodores setup, plugged in and turned on just yet to issue it even if I did know. I tried my 1541-II but it's apparently not reading disks either. It comes on and just sits there looking prettier than an original 1541. So I tried my original 1541, too, and it just sits there and does nothing either. This is the trouble I had 11 years ago when I bought my ZoomFloppy and tried doing this in 2013. So I'm 3 for 3 at the moment... with none of my drives working for making more disk images. And none of my four 1581s are good for this either. I keep reading online for options that work with 1581 floppies because I have a lot of those too. Looks like I'm going to need to find and buy an internally mountable 3.5" floppy drive for my Linux box because my USB 3.5" drive doesn't have what it needs either. Too many things failing at the same time are exactly why I had to abandon this effort before. This time, however, I'm seriously considering paying for some repairs or like-new refurbs. It's getting ridiculous. Myke |
From: Myke C <su...@my...> - 2024-06-14 06:55:01
|
And I spent a good portion of last evening / this early morning creating my first ever .d71 an .d64 backups of quite a few of my vintage 5.25" floppies. But, in typical 1571 fashion, one disk in particular was full of read errors... and now my drive refuses to read another disk directory. It keeps telling me either "drive not ready" or I get a "27" error on Track 18 which I distinctly remember as being the one in the middle where the directory is stored. So until this drive is working again, I'm back to being stuck with a bunch of floppies still needing to be virtualized for the simple sake of long-term preservation. I'm thinking it may be time to re-introduce this drive to Ye Olde Headknocker but I'll first have to connect it up physically to one of my C= computers... and even then I can't quite remember what the command is that makes it knock its head back into whack. And I also know that's bad for the drive, but it always worked so well and nothing else seems to be getting me anywhere right now. Oh well / Sigh, Myke |
From: Myke C. <su...@my...> - 2024-06-14 01:13:49
|
Hey! I have some good news! Just for kicks, I thought I'd switch to using a different serial cable and suddenly I got different results from both my 1581 and 1571. $ sudo cbmctrl detect 8: 1581 That didn't happen before. Whenever I tried to list a disk directory, though, this is all it said: $ sudo cbmctrl dir 8 0 74,drive not ready,00,00 So I switched back to my 1571 to see what it would do, and... $ sudo cbmctrl dir 8 0 0 ."geos128 1571 " g1 2a 2 "geos128" prg 152 "geoboot128" prg 137 "128 desktop" usr 91 "128 configure" usr 16 "GEOiNTRO" usr 3 "sMARTtrack 128" usr 14 "aUTOsMARTtIME" usr 7 "cHANGEbsw1.2" usr 4 "system error 2.1" usr 5 "nEWfONT" usr 5 "gILLIGAN" usr 5 "nUtEK" usr 23 "PREFERENCE MGR" usr 2 "pREFERENCES" usr 22 "PAD COLOR MGR" usr 2 "pAD cOLOR pREF" usr 15 "ALARM CLOCK" usr 18 "CALCULATOR" usr 20 "NOTE PAD" usr 8 "GEOmAKEbOOT128" usr 40 "TEXT MANAGER" usr 43 "PHOTO MANAGER" usr 18 "paint drivers" usr 2 "128 rboot" prg 67 "geomerge" usr 60 "geolaser" usr 67 "text grabber 128" usr 2 "c128 gENERIC i" usr 2 "c128 gENERIC ii" usr 4 "pAPERcLIP ii" usr 3 "fLEETsYSTEM 4" usr 6 "wORDwRITER 128" usr 141 "geowrite 64" usr 141 "geowrite 128" usr 32 "gEOoRGANIZER" usr< 50 "rEAD mE" usr 3 "128 comm 1351(A)" usr 3 "128 comm 1351" usr 3 "128 joystick" usr 3 "1571 bOOT fIX" usr 38 blocks free. 00, ok,00,00 Interesting! I have 4 JiffyDOS'd 1581s. I tried all 4 of them. One of them complains with a muted knocking sound whenever I insert a disk. One of them makes an odd, fluctuating high-frequency tone instead - and doesn't seem to indicate that it's properly seating the disk and opening the sliding door. The other two *seem* perfectly fine but, no matter what disk I insert, all 4 of them report: $ sudo cbmctrl dir 8 74,drive not ready,00,00 So I don't know what the issue is there. The 1571, however, seems to be working normally. I even tried inserting a CP/M disk into it and got this: $ sudo cbmctrl detect 8: 1571 $ sudo cbmctrl dir 8 0 ."cp/m plus " 65 2a 64695 "g..J....cB#...-" l.?< 51895 "B1.M1 M.)C.)..J;" el_< 8038 ".X.?B..:.4.Jy..." seq< 65219 ").W0M.)Mn7.t1M.)"*del 30751 "...M.(M.7M.7M.7" l_.< 14206 ".7M.7M.7C.)X..p"*sr? 10524 "4....X..rB .>.2"*el_ 66,illegal track or sector,55,83 So... is that an indication that I can also backup the 1571 CP/M disks? I know the filesystem or track/sector layout is different (as seen above) but is that feasible too? Or no go? Myke |
From: Myke C. <su...@yk...> - 2024-06-14 00:54:27
|
I have good news! Just for kicks, I thought I'd switch to using a different serial cable and suddenly I got different results from both my 1581 and 1571. $ sudo cbmctrl detect 8: 1581 I didn't even get that with the previous serial cable. Whenever I tried to list a 1581 directory, though, this is all it said: $ sudo cbmctrl dir 8 0 74,drive not ready,00,00 So I switched back to my 1571 to see what it would do, and... $ sudo cbmctrl dir 8 0 0 ."geos128 1571 " g1 2a 2 "geos128" prg 152 "geoboot128" prg 137 "128 desktop" usr 91 "128 configure" usr 16 "GEOiNTRO" usr 3 "sMARTtrack 128" usr 14 "aUTOsMARTtIME" usr 7 "cHANGEbsw1.2" usr 4 "system error 2.1" usr 5 "nEWfONT" usr 5 "gILLIGAN" usr 5 "nUtEK" usr 23 "PREFERENCE MGR" usr 2 "pREFERENCES" usr 22 "PAD COLOR MGR" usr 2 "pAD cOLOR pREF" usr 15 "ALARM CLOCK" usr 18 "CALCULATOR" usr 20 "NOTE PAD" usr 8 "GEOmAKEbOOT128" usr 40 "TEXT MANAGER" usr 43 "PHOTO MANAGER" usr 18 "paint drivers" usr 2 "128 rboot" prg 67 "geomerge" usr 60 "geolaser" usr 67 "text grabber 128" usr 2 "c128 gENERIC i" usr 2 "c128 gENERIC ii" usr 4 "pAPERcLIP ii" usr 3 "fLEETsYSTEM 4" usr 6 "wORDwRITER 128" usr 141 "geowrite 64" usr 141 "geowrite 128" usr 32 "gEOoRGANIZER" usr< 50 "rEAD mE" usr 3 "128 comm 1351(A)" usr 3 "128 comm 1351" usr 3 "128 joystick" usr 3 "1571 bOOT fIX" usr 38 blocks free. 00, ok,00,00 Interesting! Myke |
From: Myke C. <su...@my...> - 2024-06-13 19:23:44
|
Correction. In my previous email I incorrectly wrote: $ sudo cbmctrl 8 I acutally ran: $sudo cbmctrl dir 8 Sorry for that misktake. Myke |
From: Myke C. <su...@my...> - 2024-06-13 19:20:28
|
I've now connected the ZoomFloppy to my Linux desktop via USB. I've tried 2 tests first with a 1571 and again with a 1581. Both dipswitches are "up" on each device for Device #8. $ sudo cbmctrl 8 The ZoomFloppy's blue light flashes rapidly. The terminal appears to be waiting for some data... a directory listing, presumably... which never arrives. I press Ctrl-C to break the attempt and get back to my prompt. $ sudo cbmctrl reset The drive's activity light flashes appropriately. The ZoomFloppy's blue light stops flashing. The same thing happens with both drives: 1571 and 1581. And that's pretty much where things are. This seems to be where things stopped, too, when I first bought my ZoomFloppy and tried using it with an original, breadbox-brown 1541. Ideas? Myke |
From: Myke C. <su...@my...> - 2024-06-13 17:56:39
|
On 6/13/24 08:44, Steven Hirsch wrote: > > So, "apt install libncurses5-dev" should get you past that point. So to actually install all the "stuff"... I ran this (with no errors): $ sudo make -f LINUX/Makefile install install-plugin-xum1541 And now I have these new additions in /usr/local/bin/: -rwxr-xr-x 1 root root 53656 Jun 13 13:50 cbmctrl -rwxr-xr-x 1 root root 15512 Jun 13 13:50 cbmformat -rwxr-xr-x 1 root root 15536 Jun 13 13:50 cbmforng -rwxr-xr-x 1 root root 51936 Jun 13 13:50 d64copy -rwxr-xr-x 1 root root 48304 Jun 13 13:50 cbmcopy lrwxrwxrwx 1 root root 7 Jun 13 13:50 cbmread -> cbmcopy lrwxrwxrwx 1 root root 7 Jun 13 13:50 cbmwrite -> cbmcopy -rwxr-xr-x 1 root root 39344 Jun 13 13:50 d82copy -rwxr-xr-x 1 root root 52000 Jun 13 13:50 imgcopy -rwxr-xr-x 1 root root 31120 Jun 13 13:50 samplelibtransf -rwxr-xr-x 1 root root 14616 Jun 13 13:50 testlines -rwxr-xr-x 1 root root 15488 Jun 13 13:50 frm_analyzer -rwxr-xr-x 1 root root 23248 Jun 13 13:50 cbmrpm41 -rwxr-xr-x 1 root root 14552 Jun 13 13:50 cbmlinetester -rwxr-xr-x 1 root root 3006 Jun 13 13:50 opencbm_plugin_helper_tools -rwxr-xr-x 1 root root 69128 Jun 13 13:50 xum1541cfg Looks successful and healthy to me. Next steps... Myke |
From: Myke C. <su...@my...> - 2024-06-13 17:55:57
|
On 6/13/24 08:44, Steven Hirsch wrote: >> So, what must I do to make the "ncurses.h" file be present on my >> system in the location OpenCBM is expecting to find it? > > On my Ubuntu 18.04 system /usr/include/ncurses.h is a symlink to > /usr/include/curses.h and is provided by this package: > > libncurses5-dev > > So, "apt install libncurses5-dev" should get you past that point. OK. Tried that. 'libncurses5-dev' is not present in the standard repos. So I tried a couple of other variations on the name just for fun's sake and got the same from those. $ sudo apt-get install libcurses5-dev [sudo] password for mykec: Reading package lists... Done Building dependency tree... Done Reading state information... Done E: Unable to locate package libcurses5-dev $ sudo apt-get install libcurses-dev Reading package lists... Done Building dependency tree... Done Reading state information... Done E: Unable to locate package libcurses-dev $ sudo apt-get install libcurses Reading package lists... Done Building dependency tree... Done Reading state information... Done E: Unable to locate package libcurses So I searched online for "linux mint install libncurses5-dev" and found this page which claims to be able to install it remotely using "aptUrl" whenever you click the big, green "Install" button: https://community.linuxmint.com/software/view/libncurses5-dev I've *never* used that approach to install anything before and didn't even know it was possible... but it seems to have provided what OpenCBM needs. I went back and ran "make -f LINUX/Makefile opencbm plugin-xum1541" and got no errors that time. Now on to complete the install. Thanks. The OpenCBM documentation seems to be missing this information. Myke |
From: Myke C. <my...@my...> - 2024-06-13 17:23:27
|
On 6/13/24 08:44, Steven Hirsch wrote: >> So, what must I do to make the "ncurses.h" file be present on my >> system in the location OpenCBM is expecting to find it? > > On my Ubuntu 18.04 system /usr/include/ncurses.h is a symlink to > /usr/include/curses.h and is provided by this package: > > libncurses5-dev > > So, "apt install libncurses5-dev" should get you past that point. OK. Tried that. 'libncurses5-dev' is not present in the standard repos. So I tried a couple of other variations on the name just for fun's sake and got the same from those. $ sudo apt-get install libcurses5-dev [sudo] password for mykec: Reading package lists... Done Building dependency tree... Done Reading state information... Done E: Unable to locate package libcurses5-dev $ sudo apt-get install libcurses-dev Reading package lists... Done Building dependency tree... Done Reading state information... Done E: Unable to locate package libcurses-dev $ sudo apt-get install libcurses Reading package lists... Done Building dependency tree... Done Reading state information... Done E: Unable to locate package libcurses So I searched online for "linux mint install libncurses5-dev" and found this page which claims to be able to install it remotely using "aptUrl" whenever you click the big, green "Install" button: https://community.linuxmint.com/software/view/libncurses5-dev I've *never* used that approach to install anything before and didn't even know it was possible... but it seems to have provided what OpenCBM needs. I went back and ran "make -f LINUX/Makefile opencbm plugin-xum1541" and got no errors that time. Now on to complete the install. Thanks. The OpenCBM documentation seems to be missing this information. Myke |
From: Steven H. <snh...@gm...> - 2024-06-13 12:44:13
|
On Thu, 13 Jun 2024, Myke Carter wrote: > OK. Here are the details of my OpenCBM installation experience so far > running Linux Mint which is Debian-based. > The compilation from source began but ultimately bombed out at the following > step: > > make[1]: Entering directory > '/home/mykec/Desktop/opencbm-0.4.99.104/opencbm/cbmlinetester' > gcc -g -O2 -D_FORTIFY_SOURCE=2 -Wall -I../include -I../include/LINUX > -DPREFIX=\"/usr/local\" -DOPENCBM_CONFIG_FILE=\"/etc/opencbm.conf\" > -fstack-protector -DHAVE_NCURSES -o cbmlinetester.o -c cbmlinetester.c > cbmlinetester.c:19:11: fatal error: ncurses.h: No such file or directory > 19 | # include <ncurses.h> > | ^~~~~~~~~~~ > compilation terminated. > make[1]: *** [../LINUX/prgrules.make:20: cbmlinetester.o] Error 1 > make[1]: Leaving directory > '/home/mykec/Desktop/opencbm-0.4.99.104/opencbm/cbmlinetester' > make: *** [LINUX/Makefile:87: BUILDSYSTEM.opencbm/cbmlinetester.all] Error 2 > > ------------------------------------------------------------------------ > So, what must I do to make the "ncurses.h" file be present on my system in > the location OpenCBM is expecting to find it? On my Ubuntu 18.04 system /usr/include/ncurses.h is a symlink to /usr/include/curses.h and is provided by this package: libncurses5-dev So, "apt install libncurses5-dev" should get you past that point. |
From: Myke C. <su...@my...> - 2024-06-13 08:46:52
|
I run the headers installation line again. Here's the output I received (which is the same as it was the first time): $ sudo aptitude install linux-headers-`uname -r` linux-headers-5.15.0-112-generic is already installed at the requested version (5.15.0-112.122) linux-headers-5.15.0-112-generic is already installed at the requested version (5.15.0-112.122) No packages will be installed, upgraded, or removed. 0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B of archives. After unpacking 0 B will be used. |
From: Myke C. <su...@my...> - 2024-06-13 08:40:42
|
OK. Here are the details of my OpenCBM installation experience so far running Linux Mint which is Debian-based. I downloaded "opencbm-0.4.99.104.tar.gz" and extracted it in my ~/Desktop folder. I "cd"d into "opencbm-0.4.99.104" from there. I read a couple of README files and compiled the docs. Within the docs folder I began using "less" to read "opencbm.txt". Since I am installing this for use with my ZoomFloppy purchased in 2013, I am focused on "xum1541". ------------------------------------------------------------------------ "For Debian based systems, it is enough to install the package `libusb-1.0-0-dev'." I did that successfully with "sudo apt-get install libusb-1.-0-dev". So far, so good. ------------------------------------------------------------------------ "In order to compile the kernel module, you will need the headers that correspond to your current running kernel. For debian-based systems, you can accomplish this by running aptitude install linux- headers-`uname -r` as root." I ran that command as well and saw that it needed to install 0 new files. It went through various motions of searching, etc. and ultimately installed nothing new. ------------------------------------------------------------------------ "The compile-time configuration is located in `opencbm/LINUX/config.make'. Check the KERN_FLAGS line if you're running kernel 2.0.x or if you don't want to use the Linux parport subsystem for some reason. Same goes for SMP machines." I am running "Kernel: 5.15.0-112-generic" so this doesn't apply to me. I "grep"d for the "KERN_FLAGS" line anyway just to see what's there. There is no "KERN_FLAGS" line. There is, however, a "KERNEL_FLAGS" line. 2, in fact. 1 is commented out. The other is not. ------------------------------------------------------------------------ "Example: In case you are compiling for the xum1541 cable, use make -f LINUX/Makefile opencbm plugin-xum1541" Since that's what I'm wanting to do, that is is exactly what I did. ------------------------------------------------------------------------ The compilation from source began but ultimately bombed out at the following step: make[1]: Entering directory '/home/mykec/Desktop/opencbm-0.4.99.104/opencbm/cbmlinetester' gcc -g -O2 -D_FORTIFY_SOURCE=2 -Wall -I../include -I../include/LINUX -DPREFIX=\"/usr/local\" -DOPENCBM_CONFIG_FILE=\"/etc/opencbm.conf\" -fstack-protector -DHAVE_NCURSES -o cbmlinetester.o -c cbmlinetester.c cbmlinetester.c:19:11: fatal error: ncurses.h: No such file or directory 19 | # include <ncurses.h> | ^~~~~~~~~~~ compilation terminated. make[1]: *** [../LINUX/prgrules.make:20: cbmlinetester.o] Error 1 make[1]: Leaving directory '/home/mykec/Desktop/opencbm-0.4.99.104/opencbm/cbmlinetester' make: *** [LINUX/Makefile:87: BUILDSYSTEM.opencbm/cbmlinetester.all] Error 2 ------------------------------------------------------------------------ So, what must I do to make the "ncurses.h" file be present on my system in the location OpenCBM is expecting to find it? Myke |