...First of all thank you for the development of this wonderful driver!
You're welcome, I'm sure.
I forgot something. Even after the installation of the service I can only run from a PC that my img system known befor...
...Is there what to do to save these steps?? if no ,can i copy the file from grub4dos?
If it won't boot on new hardware, that's explained by my previous post: Either the drivers are not loaded by NTLDR (so are not available at boot-time) OR the devices along the device path to the backing disk are not being driven (have no associated driver for their PnP device IDs in the CDDB
Some "driver packs" might populate the CDDB with nice entries, but I find it unlikely that a "driver pack" could support every
PnP ID... CDDB would be monstrous! Modern hardware with new IDs might not even be in a "driver pack" which is older than the hardware.
This is why wimb
's method is so useful: You boot to a RAM disk first; nothing beyond WinVBlock is required for a RAM disk. This is roughly equivalent to you copying the image to the HDD and booting it first; since all of your storage controllers are in IDE mode, you always have IDE boot-time drivers. Unfortunately, WinVBlock doesn't support giant RAM disk images so your 6 GB
image won't work as a RAM disk. I don't even know if GRUB4DOS
could load such an image to RAM, though karyonix
has done some PAE
work for it, if I recall correctly.
There is another way and that is to find the device IDs for the target hardware, then pre-populate those IDs into the CDDB in the image. For example: On my computer I have a USB host controller with PCI VEN
dor ID 8086
ice ID 2836
. So I would look it up at the PCI Devices web-site
and see that it is a USB EHCI
controller. So I would make a .REG
file for a CDDB entry like this:
Windows Registry Editor Version 5.00
(You can find the ClassGUID
out by exploring, by looking at another USB host controller's value, or by asking someone.)
It is fairly easy to find PCI VEN & DEV IDs by using Syslinux
and the H
I don't know that GRUB4DOS can help you to copy your image file to the local HDD. That might require NTFS
write support; something many people not using Windows desire, but few people enjoy in a stable fashion.