Feel like I'm close to success 5.25" floppies circa 1983 ;) #504
Replies: 4 comments 5 replies
-
|
Is there really a problem? Early IBM PC formats were 8 sectors per track. That was later increased to 9. |
Beta Was this translation helpful? Give feedback.
-
|
Understood. My hesitation is from a couple things.
|
Beta Was this translation helpful? Give feedback.
-
Use the format ibm.320 instead of ibm.360 for your conversion. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks a bunch for the info. I tried |
Beta Was this translation helpful? Give feedback.
-
|
Loading the IMG file into HxC doesn't tell you much; I don't think HxC has even worked out the geometry correctly. What you want to do is load the raw dump into HxC and view that. Then we can see how many sectors per track, the sector IDs, interleave and so on. Can you share/upload a raw dump here? Another thing to try is |
Beta Was this translation helpful? Give feedback.
-
|
Thanks @keirf I gave `ibm.scan' a shot. Had some interesting messages along the way but the results look much better. Interestingly, the .img file won't load into HxC and gives "Load error! Read file error!" I dumped raw files to HxC and it didn't look so great to me so I'll leave that to you to judge. Please let me know if there is something specific in HxC I missed as I am learning. Again, I really appreciate the help on this long overdue project. Data is only 41 years old after all. :) 
Sneak peek at the initial design for the awesome enclosure I made for my GW.
|
Beta Was this translation helpful? Give feedback.
-
|
Silly me I had wrong cyl and step as args. I used Now off to see if I can make heads/tails of this old source. Thanks guys. |
Beta Was this translation helpful? Give feedback.
-
|
What do you guys recommend as the best PC emulator (prefer Mac but have Windows box too)? Specifically this code was XT-era so I am looking for the simplest way to take my .IMG files and mount and get the contents to a modern box. So far I have had some very bizarre results with some of the emulators and how the IMG file is interpreted with many of the emulators I have tried so far. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @keirf I had to drop this for a bit but I think I may have stumbled upon why my perfect scans/encoding worked but didn't. Let me set it up by explaining real quick. While I can grab the raw data and then encode it at 100%, things were ever so slightly off from one emulator to the other. I could see directory structure, analyze files using TYPE, and it always felt like there was some weird offset. Like I would look at a .C file and instead of expected C source, I would see a batch file. I'd look at a .ASM file and instead of my old assembly language source I would see C source. I'd see an EXE and try to execute and while I did get some of it to load (game) that was close to complete development, the EXE would lock up or display weird artifacts. Upon deeper review of all of the files on the disks, something kept popping up and a lightbulb turned on. In the disassembly areas and in the directory structures I saw JDOS from Tall Tree Systems. Then I remembered the old development box had a 3MB RAM disk (awesome and fast for the time) and we used JDOS. One slight difference with JDOS is it gave the ability to fit slightly more stuff on a floppy when formatted with their drivers. I have seen mentioned they do 10 sectors. I don't recall exactly but I want to say 400k capacity. I'm hoping anybody can read this and make some sense out of this and maybe help me figure out how to properly decode these disks or if somebody can help make a new JDOS format. I did a little more digging and found some old docs for what I think we had the JRAM-AT. Check em out as they are fairly detailed https://minuszerodegrees.net/manuals.htm#Talltree There is more stuff and specs on the net too. Have any of you ever encountered one of these and have a path where I can get all of my files off the disks cleanly? Thanks a ton. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hey there,
Got the GreaseWeazle all set up (Mac command line) and have tried a bunch of settings on 2 different drives (TEAC-505 and TEAC55) with same results. I read as raw without many args and it looks good to start. I searched a lot of places and here and have yet to find the clue I am lacking.
Then I do the convert to create an image file and these are the only settings that have gotten me this close to 88% consistently with all disks I've tried. My understanding is the summary should be all periods and 100%, correct?
I open up the image in HxCFloppy Emulator and it feels "close".
I see a lot of valid data in the hex dump from xxd except for a few chunks that look like this:
Any idea what I am missing?
Beta Was this translation helpful? Give feedback.
All reactions