中国DOS联盟

Use GRUB to create a fake A drive. The A drive only loads himem.sys in the config. Then, booting GRUB from the A drive can start successfully.

But in the same situation, if you use loadsys to load usbaspi.sys and di1000dd.sys, and then uninstall these two USB drivers, theoretically the situation should be the same as the beginning, but executing GRUB will freeze and the following error message appears: Probing ROM INT vectors If hang, unload a device driver or TSR and try again

I wonder if anyone has a solution. I've tried different versions of GRUB and different versions of loadsys, and the same problem occurs. I wonder if there's a conflict between GRUB and loadsys?

grub.exe is very sensitive to the interrupt vector table. Hardware drivers generally need to take over and modify interrupt vectors. If a program used to uninstall a driver does not completely uninstall the driver to be uninstalled and fails to fully restore the original interrupt vectors before the driver was loaded, running grub.exe will cause a system crash.

Find a better uninstall tool, perform the uninstall cleanly, and leave no loopholes.

If this is the case, how to confirm whether the interrupt vector is completely restored, and what software or methods are there to know whether the interrupt vector is the same as the original?

This technology itself is not difficult, but someone needs to do this work.

I believe there were many tools in the DOS era. If you look patiently, you should be able to find a satisfactory one.

Came over from another forum... Just digging around casually