1 Reply by geo411m

(41 replies, posted in Universal Imaging)

Galapo wrote:

Note, though:

1. You are limited by memory limits:
http://forum.driverpacks.net/viewtopic. … 932#p17932
http://www.911cd.net/forums//index.php? … p;p=142720

2. You are limited to drivers which maintain separate driver names and service names.

Regards,
Galapo.

OverFlow wrote:

unfortunately that is a no no... and we can't recomend it to others.

licence violation.

For anyone who is interested, the memory limit has been fixed with SP3. Now we don't have to worry about licence violation.

Go to forum: Universal Imaging

2 Reply by geo411m

(41 replies, posted in Universal Imaging)

Galapo wrote:

Note, though:

1. You are limited by memory limits:
http://forum.driverpacks.net/viewtopic. … 932#p17932
http://www.911cd.net/forums//index.php? … p;p=142720

2. You are limited to drivers which maintain separate driver names and service names.

Regards,
Galapo.

I found a way around the memory limit. I’ve been using the NTLDR from the longhorn/vista beta and it has no problems. The bonus to using it is it has the ability to detect and update the HAL on the fly. With PEIMG and NTLDR I’ve created an image that’s worked on all the machines I have tested it on (two laptops  with SATA drives and two desktops one with SATA drives).

Go to forum: Universal Imaging

3 Topic by geo411m

(41 replies, posted in Universal Imaging)

I think I found a solution to getting a working universal image. All that needs to be done is to get PEIMG from WAIK and use it to inject the drivers into your image like winpe2.0. You must make sure you have a folder named USERS on the root of your driver. It seems the tool injects the driver directly into XP and adds the drivers to the CriticalDeviceDatabase so you don't even need to use -BMSD in sysprep, just make sure you use standard IDE controller before running sysprep. So far I tested this on a HP dv6108nr and it worked perfectly. PEIMG can be used to inject just about any driver into your image. If you guy don’t feel like using a command line too you can use 'AddDrivers.exe' gui frontend. Hope you guy find this helpful.

Go to forum: Universal Imaging

4 Reply by geo411m

(28 replies, posted in Feedback and Support - DriverPacks Base)

what i do to image machine without any problems is install windows in VMWare. when windows ask you to hit f6 for textmode drivers hit f5 to choose your HAL. Choose :Advanced Computer and Power Interface. after windows is installed and you visited windows update i go to device manager and update my ide controller. Choose pick your own drivers and  install standard ide controller. then you can sysprep your machine and make sure you build mass storage drivers. then image using your fav image tool (i like imagex or ghost) and your done. you can use your update hal script and it should work fine. Since VMWare doesn't use any 3rd party driver you shouldn't have any driver problem. i've been doing this for a while now and never had any problems. Hope this helps you out.

Go to forum: Feedback and Support - DriverPacks Base