OSDev.org

Hey everyone,

I have a quick question reguarding partcopy and drive letters.

I use Virtual Floppy Drive (VFD) on Windows XP.

If the drive letter is A:, I can easily use partcopy to copy
the boot image without any problems. However, (It is
still floppy drive 0), if I change drive letters in Windows,
I get errors...

Drive letter B, when executing partcopy, gives me a (Pretty standard, it
seems) "Failed to write destination at offset 0" error from partcopy.
This does not make sense to me, because it is still floppy drive 0.

Any other drive letter, partcopy gives me a "Divide error". It is litterally
that vauge Boot.bin is a standard 512 byte floppy image.

I only have one floppy drive being emulated by VFD as "Floppy Drive 0",
but it only works as Drive "A".

Does anyone know why?

Heres the command line of what I am using: Boot.bin is a standard 512 byte floppy boot image.

As I said before, This works--but only works if the letter assigned to
the drive is "A". Does anyone have suggestions?

Thanks

Also, please excuse me if this is an easy question

I searched google for some documentations for partcopy (or,
anything), but did not find what I was looking for.

I use linux myself - sounds like shoddy windows code!

I have been thinking about this, and I have just thought:

What if the command prompt is the problem?

For example, whenever I try to access the d: (Recovery partition)or
e: drive (CD drive), I either get "Device not ready" or no error
(Bt it still doesnt change)

have you tried -f1 instead of -f0 for b: since b: is considered to be floppy number 2. It is irrelevant whether or not you have 2 floppies, from my understanding.

Sorry, I should have mentioned I tried both -f0 and -f1.