restore-disk not working #8
Comments
|
From @chrisoliphant : Tried PCMCIA serial as well as USB serial, but the same error message writing any PDD1 disk image. After format I can get directory (empty) no problem. Drop a file on the disk, get DIR no problem, but am trying to make a utility disk since I got just a bare drive and an arcadeshopper cable which both seem to work fine. After formatting completes Being a Linux newb I don't have any other boxes to try this on, but am out of troubleshooting ideas. **** EDIT *** |
|
From @chrisoliphant : |
|
From @chrisoliphant : The drive does have a new belt. I ordered up a null modem cable and will give it a shot, but it looks like REX classic is the best option anyway. I really think the drive and serial are working as I made a small text file in nano, used the PDD save command to write it to the disk. It appeared in a directory listing and was able to use load to copy it back to the host. It seems everything is working fine except for disk dump and restore disk. BTW, here is a verbose level 3 output of a disk dump attempt that fails followed in the next code block by a successful copy of a file from the disk to the host. Here is the successful read of a test file on the disk and saving to the host |
|
Got an option ROM with TS-DOS and the drive works fine. PDD works fine for moving individual files from a Linux host to the floppy and then reading the floppy from the M100, and vice-versa. Only disk dump and disk restore have the issue as originally experienced. |
|
I'll chime in with my experiences - I'm getting exactly the same thing. I'm particularly interested in reconstituting a stock utility disk for the PDD1 (even though I know there are and have boostrapped better DOSes). pdd.sh seems to be my best hope of building that specific disk. My test mule is a mid-2000's Lenovo that has physical serial ports (I bought it new and spec'd out every port imaginable because I knew it would be useful someday!). I put in a freshly wiped drive and put RHEL 9.4 Linux on it. (I also tried an older Fedora just for kicks, it's all behaving the same.). I was thrilled to see formatting and other communications to the PDD1 working fine, but specifically restore disk gives me the same failure mode discussed above: I'm an old hand at Linux, serial, and GitHub... let me know how I can help debug. If there's an older commit level you think is worth trying, I can get that going. |
|
OK I'll take another look today. Definitely many/most old versions worked, but I don't know a particular old commit off hand. My undisciplined development has bitten me because basically I have several commits where all kinds of unrelated stuff changed all in one commit, and the breakage is certainly in the middle of one of those. I should rewrite in c using dl2 as a model. (which works great and on mac and freebsd and even in cygwin) The whole bash thing was originally just a stunt anyway to see if it was possible. |
|
I totally respect the stunt, and I'm going to reimplement in C if we can't get this resolved. :-) |
|
Success! I backed off HEAD 1 by 1, and ended up 5 or so back: So it was last working (for me) at this commit: |
|
Awesome. Thanks for finding that. |
|
I'm waiting on a PDD2 now - I'll be exercising this some more :-) |
|
restore-disk is working for me all the way to current, on both a fast and a slow machine. Framework laptop with 12th gen i7, ftdi usb adapter going through a thunderbolt 3 hub that is also running 2 monitors and gigabit at the same time. I have a few different older laptops but nothing with a real serial port. I have some old sco osr5 boxes in storage but man I don't relish dragging one of those out... ...found 3 old laptops with real parallel ports but no serial. ok found basically my first laptop from my first real IT job, Dell D300XT, real serial port but only a mobile p2 300mhz and only 32bit, and missing it's pata drive. No nic so can't boot that way. Might be able to burn a cd, if any distro still offers a 32-bit build. Curse you for making me even think about trying to find and pay actual money for some old 2.5" pata drive from ebay and a pcmcia nic just to try to boot this thing.... I've been using a Vaio P as my low-end test machine. 1.3ghz atom with 2g ram from 2008 or 2009. Similarly an even older Vaio TZ which has a pentium-m, forget the speed. The Vaio P is actually running lubuntu 17.0 and deadly slow. It's a 32bit cpu so I can only even upgrade it to 18.0. Holy cow the P took something 30 seconds just to load the disk image. I know reading the disk image and converting into hex pairs in bash arrays is inefficient but still the whole disk is only 100k and must still be only about 300k-400k in ram. Those seem like they should still be tiny numbers even for a 1.3ghz Atom. On that Vaio P, restore-disk worked in both the v3 branch (de92713) and the latest version. So, so far I can't duplicate the exact error, though I do know that the latest versions are somehow not right. Freebsd and mac stopped working, and if the old commit works for you but not the latest on the same machine, well that means there is something there that isn't just a bad serial cable or something on your end. I'll keep looking. Maybe the one success was a fluke. |
|
Fresh installed current antiX on the Vaio P. Last few commits fail a simple LS on it. 222ade1 works, so that's another last-before-breakage milestone to bookmark. |
|
...and nevermind. Today, same machine, same drive, same disk... checkout main, ls works fine. Nothing special about 222ade1 |
Some problem with restore-disk, moved from discussion #6
Moved to an issue because the drive and serial connection seems ok and file transfers work, only restore-disk fails.
The text was updated successfully, but these errors were encountered: