China DOS Union

This afternoon I ran into a problem where XMSDSK would hang, and after messing with it for quite a while I finally realized it was because I had removed the floppy drive myself. I'm not too clear on exactly what effect the two drive letters A: and B: have on this command, but in short, if at least one of them is empty then XMSDSK definitely can't run normally, regardless of whether you let it choose a drive letter by default or manually specify another one. No choice, I simply used the SUBST command to virtualize both A and B first, and then ran XMSDSK. It actually worked. Some of you guys using notebooks may run into this situation, so I hope this helps a bit

Is pluto_zj saying that using xmsdsk requires dual floppy drives? I really can't understand that.
Also, xmsdsk is running into huge problems on my new 845 motherboard; after solving one, another pops up. I'm really at my wits' end right now.
Anyone with experience, come share your thoughts...

This has nothing to do with dual floppy drives. Because after DOS boots on a computer with a floppy drive, both A: and B: are mapped as floppy drives, so they are not empty, and XMSDSK can be used normally; but if DOS is booted on a computer without a floppy drive, then A: and B: are both empty drive letters. At most the system may map the CDROM to drive A:, and then B: is still unused. In this situation XMSDSK cannot run successfully, so you have to use the SUBST B: ... command to occupy the unused drive letter first, and only then run XMSDSK.

I just tried disabling the floppy drive in the BIOS, and then running XMSDSK. There was no problem, but A: and B: still seemed to exist at that time, they just couldn't be read. Then I used KILLDRV to delete both drive letters A: and B:, and ran XMSDSK again. As a result, XMSDSK automatically made A: into a RAM virtual drive. Using this method I actually created three XMSDSK drive letters, namely A:, B:, and G:, because when the XMSDSK drive letter is A: or B:, the XMSDSK /U command seems unable to exit automatically.

Probably related to the hardware specs...

Hehe, wengier is really fierce. I think these problems may vary from machine to machine, but discussions like this do let you learn some tricks.

The following is quoted from pluto_zj's post at 2003-5-4 22:53:23:
Hehe, wengier is really incredible. I think these problems may vary from machine to machine, but discussions like this do let you learn some methods.

What does “太猛了” mean?

wengier is too good. Hehe...... seems like there's nothing left for us to do..

What environment are you using XMSDSK in? Is it wengier's 71 boot disk?

No, it's a boot disk with my romdos kernel. I also tried it with the original 98 disk...

I'm the same as you. At first I used 98's IO。SYS; both XMSDSK and HIRAM。EXE would crash. After switching to Wengier's IO。SYS, XMSDSK could be used (I didn't try HIRAM), but considering that most usage environments still use the original 98 IO, I switched to RAMDISK。SYS instead.

I'm using the romdos kernel....

Under the ROM-DOS kernel, XMSDSK sometimes cannot be used directly and parameters must be added, otherwise it will also hang.