Unable to successfully read anything on new v4.0 board #387
Replies: 2 comments 14 replies
-
Firstly if you can, ditch the GUIs for now and test gw on the command line. You're bypassing a layer of abstraction this way and gw command line isn't too unfriendly. Maybe concentrate on one type of disk for now, say PC 1.44M 3.5" disks. And concentrate on reading a couple of cylinders during testing, rather than a whole disk: You may need Your errors look like you are off by one cylinder in your reads. Note unexpected sector reports with cylinder (C) reported as 79 when Greaseweazle is trying to read cylinder 78 (for example). That's the first thing to sort out. I would say that's a drive calibration error unless you see the same on multiple 3.5 inch drives? |
Beta Was this translation helpful? Give feedback.
-
Hi there and thanks for replying! Sorry for my delays, holidays and whatnot. :) The GUIs just generate and pass command lines anyway, but I get your point about removing abstraction so I did try that, but sadly got the same results, at least when using the same commands. I updated my GW to the latest firmware and then ran the command you got using two different 1.44MB PC floppy disks. These are the results I got: C:\COMSTUFF\Greaseweazle>gw read --tracks=c=0-1 --format=ibm.1440 "c:\comstuff\no save\test.img"
C:\COMSTUFF\Greaseweazle>gw read --tracks=c=0-1 --format=ibm.1440 "c:\comstuff\no save\test1.img"
These are retail disks from a boxed copy of X-Wing that I have. The first disk got 6% of sectors apparently and the second for 0%. For kicks, I reformatted the command and tried a 1.2MB disk from my Teac drive and got this: C:\COMSTUFF\Greaseweazle>gw read --tracks=c=0-1 --drive=b --format=ibm.1200 "c:\comstuff\no save\test1.img"
Basically the same results. This 3.5" was brand new in box, but it's also a more "modern" drive (it advertised supporting Windows Vista on the box). I don't have another one, but I can see if I can track one down. I'm surprised that I'm getting the exact same result on a totally different drive though, that was sold to me as tested. Do you think that's still the root cause here or could it possibly be something else? Thanks again. :) |
Beta Was this translation helpful? Give feedback.
-
Hey all. I'm at my wit's end here and I'm hoping someone might have an answer for me. The fine folks at the VCF forums have been trying to help me out and there's a lot of information in the thread over there. But, I'll try to give a synopsis here.
I have a v4.0 Greaseweazel board I purchased on eBay. I've got a new old stock 3.5" drive and a Teac FS-55GFR 5.25" drive. The GW has the most current firmware. I'm on Windows 11 Pro. I'm using the FluxMyFluffyFloppy GUI for the GW tools, but have tried the straight command-line as well.
Initially, I tried ripping Atari ST disks (the main reason I bought it), but have also tried ripping Commodore 64 5.25" disks and regular DOS 3.5" disks. Nothing has worked. No matter what I try to rip, I get variants of this:
So far, I've tried the following:
I'm hoping I don't have defective hardware here, but I am honestly at a loss of what to do now. I know this isn't just bad disks because I get the same constant errors, regardless of the disks or the drive.
Does anyone have any steps I could pursue to try to figure this out? Thank you in advance.
Beta Was this translation helpful? Give feedback.
All reactions