VOGONS


First post, by freeSCO

User metadata
Rank Newbie
Rank
Newbie

Hello,

I don't know how many of you run into the same issue but I'm sure a lot of you did.

So I have collection of heaps of images such as:

FreeDOS-1.2bootfloppy.img Windows98_No_Ramdrive.img WindowsXP_Home_Disk3.img WindowsXP_Pro_Disk4 […]
Show full quote

FreeDOS-1.2bootfloppy.img Windows98_No_Ramdrive.img WindowsXP_Home_Disk3.img WindowsXP_Pro_Disk4.img
MSDOS-6.22 Windows98_SE.img WindowsXP_Home_Disk4.img WindowsXP_Pro_Disk5.img
Microsoft Network Client 3.0 Windows98_SE_No_Ramdrive.img WindowsXP_Home_Disk5.img WindowsXP_Pro_Disk6.img
Win311 WindowsME.img WindowsXP_Home_Disk6.img WindowsXP_Pro_SP1_Disk1.img
Windows2000_Advanced_Server_Disk1.img WindowsME_No_Ramdrive.img WindowsXP_Home_SP1_Disk1.img WindowsXP_Pro_SP1_Disk2.img
Windows2000_Advanced_Server_Disk2.img WindowsNT_3.51_Disk1.img WindowsXP_Home_SP1_Disk2.img WindowsXP_Pro_SP1_Disk3.img
Windows2000_Advanced_Server_Disk3.img WindowsNT_3.51_Disk2.img WindowsXP_Home_SP1_Disk3.img WindowsXP_Pro_SP1_Disk4.img
Windows2000_Advanced_Server_Disk4.img WindowsNT_3.51_Disk3.img WindowsXP_Home_SP1_Disk4.img WindowsXP_Pro_SP1_Disk5.img
Windows2000_Pro_Disk1.img WindowsNT_4.0_Server_Disk1.img WindowsXP_Home_SP1_Disk5.img WindowsXP_Pro_SP1_Disk6.img
Windows2000_Pro_Disk2.img WindowsNT_4.0_Server_Disk2.img WindowsXP_Home_SP1_Disk6.img WindowsXP_Pro_SP2_Disk1.img
Windows2000_Pro_Disk3.img WindowsNT_4.0_Server_Disk3.img WindowsXP_Home_SP2_Disk1.img WindowsXP_Pro_SP2_Disk2.img
Windows2000_Pro_Disk4.img WindowsNT_4.0_TerminalServer_Disk1.img WindowsXP_Home_SP2_Disk2.img WindowsXP_Pro_SP2_Disk3.img
Windows2000_Server_Disk1.img WindowsNT_4.0_TerminalServer_Disk2.img WindowsXP_Home_SP2_Disk3.img WindowsXP_Pro_SP2_Disk4.img
Windows2000_Server_Disk2.img WindowsNT_4.0_TerminalServer_Disk3.img WindowsXP_Home_SP2_Disk4.img WindowsXP_Pro_SP2_Disk5.img
Windows2000_Server_Disk3.img WindowsNT_4.0_Workstation_Disk1.img WindowsXP_Home_SP2_Disk5.img WindowsXP_Pro_SP2_Disk6.img
Windows2000_Server_Disk4.img WindowsNT_4.0_Workstation_Disk2.img WindowsXP_Home_SP2_Disk6.img allinone.img
Windows95a.img WindowsNT_4.0_Workstation_Disk3.img WindowsXP_Pro_Disk1.img
Windows95b.img WindowsXP_Home_Disk1.img WindowsXP_Pro_Disk2.img
Windows98.img WindowsXP_Home_Disk2.img WindowsXP_Pro_Disk3.img

These boot fine with directly putting them into VirtualBOX or VMWARE's floppy emulator.

However when I write them out to the gotek only very few boots. Solution is usually if it's a msdos image then boot in the same version of msdos and do sys A:, you can imagine this becomes a hassle after a time.

Also are people care to share their GOTEK BACKUP 120 disks collections?

floppy-disks.jpg

Thanks

Reply 1 of 2, by Thermalwrong

User metadata
Rank Oldbie
Rank
Oldbie

I've been getting something similar with my Gotek working on an HP Vectra VL400 motherboard recently - the gotek is detected and working, it does a floppy seek during boot and the floppy can be read in Windows. The image I'm using is of a Windows 98 bootdisk, or DOS 6.22 disk 1, both of which used to work.
I haven't figured it out yet, but whatever the problem is, it's affecting both Flash Floppy firmware and the regular gotek firmware?

Reply 2 of 2, by freeSCO

User metadata
Rank Newbie
Rank
Newbie

Hello,

The issue is not similar. I have no problem with accessing the disks from an existing Win98 or DOS setup from the given computer.
They have the content on them what's inside the img, there is nothing wrong with that.

However they do not boot. Using the "bootable" option in the Gotek Floppy Emulator does not make much sense only in case you create new disks (not using predone image files). That bootable option is basically just puts a dos 7.0 based boot record and command.com on the virtual disk. If you use an .img it will overwrite whatever is on the virtual disk slot anyway.