DriverPacks.net Forum - service entry naming conventions

Re: service entry naming conventions

null@example.com (OverFlow) — Mon, 17 Mar 2008 11:14:59 +0000

You may have some wiggle room there - I am not certain - I'm sure that someone will clarify for us...

Re: service entry naming conventions

null@example.com (Galapo) — Mon, 17 Mar 2008 06:03:30 +0000

OverFlow wrote:

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.

Re: service entry naming conventions

null@example.com (OverFlow) — Mon, 17 Mar 2008 04:59:44 +0000

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.

Re: service entry naming conventions

null@example.com (Galapo) — Sun, 16 Mar 2008 23:11:19 +0000

Galapo wrote:

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.

Re: service entry naming conventions

null@example.com (OverFlow) — Fri, 22 Feb 2008 14:14:28 +0000

Agreed

Re: service entry naming conventions

null@example.com (Galapo) — Fri, 22 Feb 2008 02:52:34 +0000

OverFlow wrote:

it seems to me that offline sysprep is useful for moving a drive to a new system in wich case you will only need to "add" one driver and then not have a problem.

Yes, that has been my own primary aim from the beginning ... then people started suggesting adding all the drivers...

if it is your desire to create / modify an image that could be loaded onto multiple machines (the true intent of sysprep) then the better way to go would be to use a driverpacks slipstreamed source to begin with (one of the few times KTD is useful). in that way all of the mass storage drivers would always be available.

Yes, I think you are indeed correct. Other methods -- at least with xp -- will encounter the memory issue at some stage. Version 2 of OfflineSysPrep will allow for injection of user-provided driver(s) via their .inf(s) with peimg. This in addition to the option of injecting the DP driver(s). I think it will be a good way of moving a full install onto newer hardware in the case of replacing the motherboard etc. Inject the DP driver for the detected hardware, or supply driver files yourself and inject.

Regards,
Galapo.

Re: service entry naming conventions

null@example.com (OverFlow) — Fri, 22 Feb 2008 02:39:17 +0000

it seems to me that offline sysprep is useful for moving a drive to a new system in which case you will only need to "add" one driver and then not have a problem.

if it is your desire to create / modify an image that could be loaded onto multiple machines (the true intent of sysprep) then the better way to go would be to use a driverpacks slipstreamed source to begin with (one of the few times KTD is useful). in that way all of the mass storage drivers would always be available. (or any other drivers that were Kept by Keep The Driver (KTD).

Re: service entry naming conventions

null@example.com (Galapo) — Fri, 22 Feb 2008 02:09:23 +0000

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.

Regards,
Galapo.

Re: service entry naming conventions

null@example.com (OverFlow) — Fri, 22 Feb 2008 01:29:54 +0000

cdob makes a good point about compressed vs non compressed drivers. uncompressed they may take a lot more ram.
furthermore i belive with your method the support files also get loaded. if this is true it is much different than textmode setup where they are not needed or loaded into ram. Support files are eventually loaded by PNP in PE and then we don't have the memory limit and only the files required for a needed controler are loaded instead of all of the drivers. so if there are support files with the same name it will not matter (to us at driverpacks for slipstreaming) since they are loaded only if needed on the current installation.

Somebody stomped on my username over at 911 i had to register with an alternate name
(and that person has a whopping 2 posts since 2005 - unfortunately they did visit as recently as last week - so it's not a dead account)

Re: service entry naming conventions

null@example.com (Galapo) — Thu, 21 Feb 2008 19:57:05 +0000

Jaak wrote:

Each little mistake would make it quite flaky and the work was "iffy" at best..

I agree. But it was good of you all to make such a test available for a while. My opinion is to stick with what worked previously, ie do not go with the temporary name changes we had in 8024 and 8025.

@OverFlow
Sorry, the 911cd forums we down for a little while it seems. Link should again we working to read cdob's post.

Regards,
Galapo.

Re: service entry naming conventions

null@example.com (Jaak) — Thu, 21 Feb 2008 16:50:42 +0000

the testfile for galapo "DP_MassStorage_wnt5_x86-32_8025PE_svctest_VIA92.7z" was pulled from FTP.
Each little mistake would make it quite flaky and the work was "iffy" at best..

SiL: I will try find the WU drivers and hope these are BIOS independant.
That would be far better than having several sets for one type of device.

Re: service entry naming conventions

null@example.com (OverFlow) — Thu, 21 Feb 2008 07:42:24 +0000

the number of drivers is not as signifigant as the size - IE one driver may be 120k but others may be 360k...
you could have three more 120 in place of one 360 if it were a size limit...

link above is dead

Re: service entry naming conventions

null@example.com (Galapo) — Thu, 21 Feb 2008 02:10:53 +0000

I've edited my post above with how many drivers were injected with each test. To me it seems there's some sort of limit generally in the mid 70's.

cdob's made a helpful post here: http://www.911cd.net/forums//index.php? … p;p=142720

Regards,
Galapo.

Re: service entry naming conventions

null@example.com (OverFlow) — Thu, 21 Feb 2008 01:20:34 +0000

if you belived it was size then you could total the size of the listed *.sys files and see what the totals are for each group.

you may have to allow some slack space (each driver may occupy slightly more ram than its actual size)

if the size theory was correct it wouldnt matter which drivers where included only thier cumulative sizes.

test and report ill see what i can tell you

Re: service entry naming conventions

null@example.com (Galapo) — Wed, 20 Feb 2008 08:31:17 +0000

Here's the tests I did. All drivers were injected with OfflineSysPrep into an XP sp2 VMWare machine.

I am not very good at seeing patterns. But it appears to me that whatever combination of drivers chosen, you just can't do TOO many else you're hit with the ntfs.sys error. The "loader error 3" error message I had two time is interesting and I've never seen it before.

1. enabled all apart from a*, m* = ntfs.sys error = added ~81 drivers
2. enabled all apart from a*, m*, si3* = success = added ~64 drivers
3. enabled all apart from a*, m*, i*, n* = success = added ~69 drivers
4. enabled all apart from a*, n* = nyfs.sys error = added ~87 drivers
5. enabled all apart from a*, n*, i* = ntfs.sys error = added ~81 drivers
6. enabled all apart from a*, m*, n* = ntfs.sys error = added ~75 drivers
7. enabled all apart from 3*, a*, m*, n* = success = added ~66 drivers
8. enabled all apart from 3*, m*, n* = ntfs.sys error = added ~90 drivers
9. enabled all apart from 3*, a*, n* = ntfs.sys error = added ~78 drivers
10. enabled all apart from 3*, a*, m* = success = added ~72 drivers
11. enabled all apart from a*, m*, h* = ntfs.sys error = added ~90 drivers
12. enabled all apart from 3*, a* = ntfs.sys error = added ~84 drivers
13. enabled all apart from 3*, a*, h* = ntfs.sys error = added ~78 drivers
14. enabled all apart from 3*, a*, c*, h* = success = added ~73 drivers
15. enabled all apart from 3*,a*, c* = ntfs.sys error = added ~79 drivers
16. enabled all apart from a*, c*, h* = ntfs.sys error = added ~82 drivers
17. enabled all apart from 3*, c*, h* = ntfs.sys error = added ~97 drivers
18. enabled all apart from3*, c*, h*, i* = ntfs.sys error = added ~91 drivers
19. enabled all apart from 3*, c*, h* i*, p* = ntfs.sys error = added ~87 drivers
20. enabled all apart from 3*, c*, h*, i*, p*, q* = "loader error 3" error = added ~83 drivers
21. enabled all apart from 3*, c*, h*, i*, p*, q*, r* = success = added ~80 drivers
22. enabled all apart from 3*, c*, h*, p*, q*, r* = ntfs.sys error = added ~86 drivers
23. enabled all apart from 3*, c*, f*, h*, p*, q*, r* = ntfs.sys error = added ~81 drivers
24. enabled all apart from 3*, c*, d*, f*, h*, p*, q*, r* = ntfs.sys error = added ~78 drivers
25. enabled all apart from 3*, c*, d*, f*, h*, p*, q*, r*, u* = ntfs.sys error = added ~75 drivers
26. enabled all apart from 3*, c*, d*, f*, h*, p*, q*, r*, u*, v* = success = added ~84 drivers
27. enabled all apart from c*, d*, f*, h*, p*, q*, r*, u*, v* = ntfs.sys error = added ~81 drivers
28. enabled all apart from c*, d*, f*, h*, i*, p*, q*, r*, u*, v* = success = added ~75 drivers
29. enabled all apart from c*, d*, f*, h*, i*, p*, q*, r* = "loader error 3" error = added ~81 drivers
30. enabled all apart from c*, d*, f*, h*, i*, p*, q*, r*, u* = success = added ~78 drivers

Regards,
Galapo.