Re: service entry naming conventions
Agreed
The DriverPacks, the DP_Base program, and Support Forum are FREE!.
You are not logged in. Please login or register.
Agreed
Yes, with this method whatever drivers get injected all get loaded. With the injection method internal to OfflineSysPrep it is only the main driver files, no secondary drivers. Full PNP after first boot is probably mandatory. Injecting with peimg is a different matter as the installation is directly via the .inf, so whatever drivers there that are references get injected and consequently loaded. With the setup routine there will be far less services running so that no memory limit is currently breached, but it seems injecting drivers into an already installed system that limit can be reached, at least under the conditions and methods I've tested here.
Turns out that it is very likely to be a memory limit rather than a buggy driver. Testing the suggestion posted here
http://forum.driverpacks.net/viewtopic. … 576#p18576
of replacing ntldr from longhorn (I tried 4053) results in a booting system and no longer the 'ntfs.sys' error. Memory limits seem to have been increased.
Regards,
Galapo.
yes each os has a higher limit than its successor - we have been aware of that for quite a while.
however if you use the 2003 in place of the XP file
Then you are in violation of the MS Licensing agreement. (unless you want to buy a 2003 license for your XP)
So we cannot recomend that people do that.
Then you are in violation of the MS Licensing agreement. (unless you want to buy a 2003 license for your XP)
So we cannot recomend that people do that.
Yes, that's right.
Is that also the case with Longhorn files?
Regards,
Galapo.
You may have some wiggle room there - I am not certain - I'm sure that someone will clarify for us...
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
[ Generated in 0.015 seconds, 10 queries executed ]