I suspect there must be something else, but I can not figure out what it might be. But here driver is unable to read even sector 1 at head 0 track 0 (boot sector) to identify the geometry. My assumption was that I just *2 track number, at least it must yield correct reading of data. I have problems finding information on how to support older 360k formats on newer drives. The same custom driver works properly with 3.5' drives' 1.44M and 720k formats, and with 5.25' drive's 1.2M format, only 360k is having problems. The FDC speed set is 250 kb/s (CR1=1, CR0=0). Here's what I send to controller: 46 00 00 00 01 02 01 2A FFĪnd here's what I get in response 40 01 00 00 00 01 02

The controller returns 'address mark not found'. I am using the same drive to read data from 360k diskette back using custom driver. When you copy files to it the used disk space will automatically increase.I formatted several 5.25' diskettes with 360k and 1.2M on the Windows XP PC using 1.2M (HD) drive. If you for example create a sparse file of 4GB, mount it in FileDisk and format it to NTFS, it will only take up 24MB on disk but look like a normal disk of 4GB. To see how much disk space a file actually uses right click on the file and choose Properties. A sparse file is a file where suficiently large blocks of zeros aren't allocated disk space. FileDisk can also use CD/DVD images.įileDisk will use sparse files as disk images if the underlying file system supports it. An example of use for this driver is if you have made plans spending the weekend writing a RAID driver for NT but find you are short of disks. A console application is included that let you dynamically mount and unmount files. Try FileDisk (also comes bundled with WinImage):įileDisk is a virtual disk driver for Windows that uses one or more files to emulate physical disks.

Formatting 720k floppy disk in window 7