OSI + Gotek (youtube video)

[HOWARDHB]

...and you can have, in excess of, 30 000 OSI disk images in/on it !

[davisgw]

bxdanny,
In order to get working Gotek images for all 9 Dos/65 floppies, I downloaded your Dos65-cln.zip, the "cleaned" version of the disks I had uploaded from the original disk dumps I own. Then I used OSIHFE to convert them....the good news is the Gotek will boot all of them! Good job!

Now I have a puzzling question for anyone. The Dos/65 documentation states that a Warmstart is executed if a <ctrl-c> is executed at the prompt. If I do this on my C1p after booting from a floppy, the system reboots as expected, except it appears to reboot from disk. But if I do this on my C1p after booting from the Gotek the system does NOT reboot, though the Gotek indicates that it is being accessed. I've tried this with several images with the same result. Can there be something unique about the Gotek that causes this to fail?

[davisgw]

Since I neglected to offer the set of Gotek Dos/65 images, I'm posting them here. I guess I wasn't thinking....

[davisgw]

I have a couple new issues with my Superboard 600D systems with Gotek as drive A and a floppy drive as B. The issues came about because I needed to rebuild Dos/65 with changes that support 12x48 video, since my original release supports only 24x24 video. And in the process of the rebuild I discovered that my two floppy system has a flakey A drive. After much swearing I was able to rebuild the system on a floppy but could not copy the rest of the files so I ended up with a Gotek image with only the rebuilt system, but not the rest of the program files.
So I would like to do an image to image copy of files. Does anyone know a way to do that without copying from A to B and then B to A?

Secondly, as I previously noted, after booting Dos/65 from a Gotek image, executing a <ctl-c> at the command prompt forces a warm start of Dos/65 but it is not successful, requiring a cold boot. But I've discovered the problem is much worse in that it apparently tries to execute a warm start after execution of a program like MOVE or COPY, requiring a cold boot. When booting from a floppy this does not happen. I have tried booting Dos/65 using the Loader disk image and also from my ROM loader with the same result. Does anyone have an idea how to debug why this fails on Gotek? I suspect that OSIHFE does not correctly convert Dos/65 because of the different formatting.
What do you think Mark?

[Mark]

You could dump the disk contents, or at least the 1st 5 tracks as read by the OSI, real drive & Gotek using OSIDump or DiskTool to see if there is a difference being read by the disk controller.

Generally do all your DOS/65 Gotek images fail the same way and work on the real drive?

How are you creating the working floppies? DiskCopy from Gotek? Are they original?

Can you create or overwrite a Gotek image, Format it with DOS/65, Copy a real disk using DOS/65 and post the resulting hfe?
(And does that disk fail just like the ones created with OSIHFE?)

I guess the opposite may be useful too - Copy a system disk from Gotek to real using DOS/65 and see if that exhibits problems.

Do you have a GreaseWeazle? If so, can you create a SCP image of a working floppy?

Thanks.

[bxdanny]

So I would like to do an image to image copy of files. Does anyone know a way to do that without copying from A to B and then B to A?

Since everything on the DOS/65 disk EXCEPT track 0 uses a format compatible with OS-65D, you could probably use the OS-65D copier on Tutorial Disk 5 to do the copy ("A" to "A"). It would just be a question of knowing which track to start from. Track 1? Track 2 or 3? Wherever the transition from "system code" to "file system" occurs. Now, if it occurs in the middle of a track, then I guess this won't work, but I don't think that it does.

P.S. I see that Mark has responded to your other questions, so don't miss his message.

[davisgw]

You could dump the disk contents, or at least the 1st 5 tracks as read by the OSI, real drive & Gotek using OSIDump or DiskTool to see if there is a difference being read by the disk controller.
This should show whether OSIHFE is not converting the image correctly....I don't think it gets beyond track 0, assuming a '0_' on the Gotek means track 0 is current. The Gotek looks like it is repeatedly trying to read track 0. I looked at the listing for the warm start and checked the code with the monitor and the vector looks correct, but did not check the warm start destination yet.

Generally do all your DOS/65 Gotek images fail the same way and work on the real drive? Yes.

How are you creating the working floppies? DiskCopy from Gotek? Are they original? The working floppies are from the original as are the Gotek images. I will try copying from the Gotek as your last suggestion. I was hoping to see a different result with the image from the rebuilt system disk using the supplied SYSGEN utility but the result was the same.

Can you create or overwrite a Gotek image, Format it with DOS/65, Copy a real disk using DOS/65 and post the resulting hfe?
(And does that disk fail just like the ones created with OSIHFE?)I have formatted side 2 of an image and copied to it. Not sure what you are asking with the second question. All the real disks are copies and work fine when booted but the hfe does not.

I guess the opposite may be useful too - Copy a system disk from Gotek to real using DOS/65 and see if that exhibits problems. This is an interesting suggestion and I will try it tomorrow.

Do you have a GreaseWeazle? If so, can you create a SCP image of a working floppy? No.

[Mark]

Can you create or overwrite a Gotek image, Format it with DOS/65, Copy a real disk using DOS/65 and post the resulting hfe?
(And does that disk fail just like the ones created with OSIHFE?)I have formatted side 2 of an image and copied to it. Not sure what you are asking with the second question. All the real disks are copies and work fine when booted but the hfe does not.

What I need is real drive A: Gotek drive B:. Boot DOS/65. Use Format.com from DOS/65 disk 3 to format Gotek (having mounted any hfe you like). Use Copy.com from disk 1 "COPY ALL" from Drive A to drive B. This will make a system image on the Gotek with the timing from your OSI. Please post this.
Then make Gotek drive A and Real drive B, and see if the Gotek boots and still exhibits problems with warm start.

From your followup saying Gotek appears stuck on track 0 -- it could be there isn't enough gap before the start of data. DOS/65 waits 800us after index END to start reading, at which point it resets the disk ACIA which could cause loss of sync. FlashFloppy starts sending track image bits at index start. Its not clear how long the index lasts, so I'm not sure how much delay is needed before writing data to get "at least 800us after index". Your generated HFE will have that information.

Cheers

[Mark]

I figured out that DOS/65 track 0 is short by 4 bytes when encoded with HFE. This doesn't show up in the OSI dump image though. This will prevent DOS/65 from loading due to a short read.

If you can post the HFE with Dos/65 as requested in the previous message, that would be great to see timings. But I'm pretty sure this is the problem.
(No need to swap drive letters & try booting from it unless you are curious.)

I'll post an updated OSIHFE soon.
-Mark

[davisgw]

I believe I have proven the OSIHFE error you found in the track 0 conversion is correct. I did the following to prove it.
1) I tried to use the Dos65 COPY utility to copy from the Gotek flash drive A to real floppy B. It has the options SYSTEM, DATA, and ALL. If I tried to copy DATA only it was successful. If I tried to copy SYSTEM or ALL it failed every time reading track 0.
2) If I booted from the real floppy this worked every time.
3) I connected my third Gotek to my original two floppy system and plugged in the same flash drive. The result was the same as number 1 above.
Then I used Disktool to dump the contents of the flash drive image. So I'm attaching the zip containing the following files:

dos65600floppydump - the dump of the rebuilt floppy, system only.
dos65600hfedump - the dump of the OSIHFE Gotek image
dos65600image - the Gotek image file, system only

I hope this is all you require because I'm drained....
Let me know what you find. Thanks for your help!