Search options (Page 6 of 11)

sorry i was in a rush to go out and had just installed, sysprepped, ghosted it and on final test then realised path mistake and posted in haste

whoever made the latest monitor pack (070818) has screwed the root path up, can it be removed from FTP so no one else just wastes an hour on a rebuild with it like i just did, grrr

PC hung (about 10.30) - can see time change below , apparently installing monitor but presume was somehting to do with graphics drivers?
Was restarted at 11.40 and can see if then installed monitor fine
Was a new Dell lattitude D610

[2007/08/21 10:32:39 480.574]
#-198 Command line processed: C:\WINDOWS\system32\services.exe -setup
#I060 Set selected driver.
#-019 Searching for hardware ID(s): pci\ven_8086&dev_2592&subsys_01821028&rev_03,pci\ven_8086&dev_2592&subsys_01821028,pci\ven_8086&dev_2592&cc_030000,pci\ven_8086&dev_2592&cc_0300
#-018 Searching for compatible ID(s): pci\ven_8086&dev_2592&rev_03,pci\ven_8086&dev_2592,pci\ven_8086&cc_030000,pci\ven_8086&cc_0300,pci\ven_8086,pci\cc_030000,pci\cc_0300
#I022 Found "PCI\VEN_8086&DEV_2592" in c:\windows\system32\drvstore\igxp32_eba99244b5c9ce2772ee2b9804f9cb72848cd30f\igxp32.inf; Device: "Mobile Intel(R) 915GM/GMS,910GML Express Chipset Family"; Driver: "Mobile Intel(R) 915GM/GMS,910GML Express Chipset Family"; Provider: "Intel Corporation"; Mfg: "Intel Corporation"; Section name: "i915GM0".
#I023 Actual install section: [i915GM0]. Rank: 0x00002001. Effective driver date: 10/06/2006.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [i915GM0] in "c:\windows\system32\drvstore\igxp32_eba99244b5c9ce2772ee2b9804f9cb72848cd30f\igxp32.inf".
#I320 Class GUID of device remains: {4D36E968-E325-11CE-BFC1-08002BE10318}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-124 Doing copy-only install of "PCI\VEN_8086&DEV_2592&SUBSYS_01821028&REV_03\2&EBB567F&0&10".
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [i915GM0.Interfaces] from "c:\windows\system32\drvstore\igxp32_eba99244b5c9ce2772ee2b9804f9cb72848cd30f\igxp32.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of "PCI\VEN_8086&DEV_2592&SUBSYS_01821028&REV_03\2&EBB567F&0&10".
#I121 Device install of "PCI\VEN_8086&DEV_2592&SUBSYS_01821028&REV_03\2&EBB567F&0&10" finished successfully.
[2007/08/21 10:32:46 480.578]
#-198 Command line processed: C:\WINDOWS\system32\services.exe -setup
#I060 Set selected driver.
#-019 Searching for hardware ID(s): monitor\sec3450
#-018 Searching for compatible ID(s): *pnp09ff
#I393 Modified INF cache "C:\WINDOWS\Inf\INFCACHE.1".
#I022 Found "*PNP09FF" in C:\WINDOWS\Inf\monitor.inf; Device: "Plug and Play Monitor"; Driver: "Plug and Play Monitor"; Provider: "Microsoft"; Mfg: "(Standard monitor types)"; Section name: "VESADDC.Install".
#I023 Actual install section: [VESADDC.Install]. Rank: 0x00002000. Effective driver date: 06/06/2001.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [VESADDC.Install] in "c:\windows\inf\monitor.inf".
#I320 Class GUID of device remains: {4D36E96E-E325-11CE-BFC1-08002BE10318}.
#I060 Set selected driver.
#I058 Selected best compatible driver.

>>rebooted as froze here, was no gap in log what above and below were on adjacent lines <<

[2007/08/21 11:46:21 468.3 Driver Install]
#-019 Searching for hardware ID(s): monitor\sec3450
#-018 Searching for compatible ID(s): *pnp09ff
#-198 Command line processed: C:\WINDOWS\system32\services.exe -setup
#I022 Found "*PNP09FF" in C:\WINDOWS\Inf\monitor.inf; Device: "Plug and Play Monitor"; Driver: "Plug and Play Monitor"; Provider: "Microsoft"; Mfg: "(Standard monitor types)"; Section name: "VESADDC.Install".
#I023 Actual install section: [VESADDC.Install]. Rank: 0x00002000. Effective driver date: 06/06/2001.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [VESADDC.Install] in "c:\windows\inf\monitor.inf".
#I320 Class GUID of device remains: {4D36E96E-E325-11CE-BFC1-08002BE10318}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-166 Device install function: DIF_INSTALLDEVICEFILES.
#I124 Doing copy-only install of "DISPLAY\SEC3450\3&A26EB72&0&80861400&00&02".
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [VESADDC.Install.Interfaces] from "c:\windows\inf\monitor.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of "DISPLAY\SEC3450\3&A26EB72&0&80861400&00&02".
#I121 Device install of "DISPLAY\SEC3450\3&A26EB72&0&80861400&00&02" finished successfully.
[2007/08/21 11:46:46 468.8 Driver Install]

new modem pack
00D92392A710DDF02674C275AEBDE7A0
DP_Modem_wnt5_x86-32_70821.7z
adds support for wireless modem cards in Dell laptops, in \NW (novatel wireless merlin USB modem module)

great, please let me know so I can populate the universal imaging thread

tbh, if the full YYYY-MM-DD was used with hyphens, it would probably be clearer it related to a date at least.

...and although bit is compleltey offtopic, Imperial measures advantage is their scaling in relation to real life, that metric doesn't have (I use both btw.) this is the best way to explain.
car tyre 30psi = 2.07bar
mountbike is 50 psi = 3.45bar
racing bike 120psi = 8.27 bar
the point being its easy to compare numbers on a scale of say 1 to 100 when the units fit the task. Metric units for things like trye pressures are useless, either in bar or N/m^2.
If I went to measure my car tyre pressure and found it was 1.93 bar , I really wouldn't know if that was about right or too flat becuase the difference in the two numbers is minimal. However if it was 25 psi I could easily see it was 5 out and what fraction that was of what it should be.
I grew up using entirely metric measures yet now always use feet and inches for measuring 90% things because they fit the day to day sizes of things more sensibly. Unless you have used both systems you perhaps cannot understand this though [ I tried explaining it to my gf once who only ever used metric and she couldn't 'get it'.]

lol, yeah I didn't either Helmi explained it and its also been now updated ion the sticky thread about releasing them.
The last number is the date in a modified version of the international date format, (which is YYYY-MM-DD) - which makes it evenly confusing for everyone as I have never seen it used anywhere ever except here
so today being 18th of ausgust 2007 = 2007-08-18 in IDF and in driverpack format is 070818 so pack would be DP_Monitor_wnt5_x86-32_070818.7z

frag: do you want to formerly update DP_Misc yourself? - you might want to put the O2 smartcardreader bit into my pack?
I have updated the modem one myself with the newer modem too for the D830's
I think the graphics one got udpated in main pack.
The sound one I think got updated too in main pack but doesnt seem to work.

yeah it would be great to fix this, appart from the radeon mobility graphics driver not working on the D620 this is only other main issue.

Fragbert made a fix pack for the Sound about this, I believe it got incorporated into the main sound pack but doesnt appear to work?
http://forum.driverpacks.net/viewtopic.php?id=1521

Helmi:

Sorry I didn't know that was the date, seems hard to read to me, being back to front - the tutorial just says to name them;
DP_myDriverPacksNameWithoutSpaces_wnt5_x86-32_myVersionSystem.7z

I had just incremeted with next logical looking number, maybe why people just end up putting 'mod' after things they changed as they don't know?

I just put all the other info into a post but once again this board stopped working yet again for a few mins so it was all lost when I hit submit (happens about 30% of the time)
Iv'e renamed the Touchscreen to end with an 8, MD5 stays same - folder is \TS\

Helmi

I have now tried with original XP SP2 sfc_os.dll and with a modified one+reg change [reg change now again working with the modded dll, as it did with SP1] - and it makes no difference to that count or how any of the drivers install. >> n.b. I use the finisher on runonce after sysprep <<

I do remember, perhaps in March?, not having this behavior with a previous dp_base - i remember it beeping away as all the unsigned drivers got processed and annoying everyone at work.

Also, I use the finisher for an entirely different reason, adding my SmartCardReader pack to machines in current use. When I use the finisher in this situation (really just to populate devpath) I DO get all the resets. On some machines the driver signing disabler thing DOESN'T work on one particular one and I get popup as in screenshot. Older machines possibily with SP1 and no updates seem to get popup but newer ones do not.

Here you can see I am using it just for adding the pack and it resettin, but the driver signing thing not working when it hits a non whql signed driver.

This is all now ok simply by not running makePNF.exe prior to sysprep (as had been suggested by Bashrat!)