@hilander999

I don't really have much more than what I've already posted for details at this time. I'm building again with just the basic install with rc11 of C driver graphics pack that was made to see if running HWPNP a bunch of times there will get it to play nicely.

When using the xnview to view multiple pictures for instance it does the slowdown lag(choppiness line by line movement that slows down not only displaying the pictures but cursor movement as well). This happens while using the folder browse feature. The image at a time, it's slow-er, but not super-noticable such as the other extreme case.

Doesn't [play nicely] with my own driver still. The default monitor which SHOULD be listing as "Generic PnP Monitor"(monitor\LPL0000) but instead gets a scrambled name in the unknown devices section with my driver. The go GS 7900 gets assigned properly and lists right in device manager under PE, but of course barfs somewhere along the way.


Nope, that was no help:
Here's the HwPnP log file

OverFlow wrote:

Wayne,

Please remember that PE is NOT an OS, It's not windows.
It's an installation tool (and thanks to Bart also a repair tool) not an OS substitiute.

You are not going to be able to play DOOM / Crysis from PE any more so than you could from safe mode. wink In fact you may have better luck from safemode big_smile You will be able to run a virus scan wink

That much I get. When I talk "lag in graphics" I'm not refering to 3d. I'm referring to 2d. Menus, pictures, etc..All of which without hardware backing have delays and tend to barf quite a bit.

To me it's more of a swiss army knife OS. It's contained, unalterable, no footprint, and can do 98% of what I turn the machine on to do for most days. I have the specific tools(OS's) for the specialized instances. Many times they are in flux as I'm testing something, or otherwise hosed it. Sometimes I just really don't feel like re-installing or imaging. Which is why I love my UBCD4win disk, and it also serves the other purposes you mention for relatives and friends. smile

hilander999 wrote:

@Wayne

READING ASSIGNMENT:
http://www.911cd.net/forums//index.php?showtopic=19325

This may be a viable solution for you since nvidia ALWAYS fits the "Problematic" catagory.

Definitely a good intermediate solution, still won't give hardware acceleration, which won't solve the lag issue I currently have, but at least I could get the proper resolution going for this thing. smile

hilander999 wrote:

@Wayne

Blame me, everyone else does.

I have been sick lately and happen to be one of the only people who actually understands how this stuff works in bartpe, which explains the 57 views on you question at ubcd4win.com with no responce. When the right person reads your thread, you get answers... unless of course he gets woken up at night to respond here instead. smile

if the files are not getting copied to the output folder, it may be something in the Bâshrat the Sneaky BASE or a flag in the driverpacks ini file stopping the copy in pebuilder.
.cat files are not used in PE

With the limited Windows API set included in a PE, I'm not sure you are going to get that driver working.
Graphics drivers are a bit harder to get working and sometimes require several thousand registry entries before build (in the plugin.inf file)

I may be able to sort this out, but I'm not really well enough to spend a lot of time in front of a keyboard right now.
I also have some experimental stuff that may sort this out also, so if I get to a beta state, I'll hook you up with some goodies to try out.

Yeah, I did a bit of sifting, I think it's only selectively using drivers from DriverPacks for this and for that matter many other included driverpack types, I assume because of the reasons you mention. Event viewer throws the failed to load error, but if there's any way to show a deeper view of what's going on inside bartPE, that'd be loads of help. So far, to me best I can get is "there was an error". *facepalm*

Appreciate it guys! Not a big rush now that I at least know some reason as to WHY it's not working. I'll just deal for a bit with lower resolution and no hardware accel for my PE live cd. smile

Doing a basic integration works fine. In fact the only driver that was missing was the wireless for some reason. *shrug*

DPSmode 2 was necessary as there were 5k+ entries. smile

Here are the logs for verification.

Forgive my ignorance, going through the xp integration process now. I was just now going  through the tutorial stickies on 3rd party driver integration, I'm still more than a bit ignorant about aspects of this. smile

On the winntdirectories entry, it does create the folder and put the tvg files into there, when I check the BartPE build folder, as to the others I'll have to look into it further later, after testing the method you wish. I just have to swap out my hard drive, I keep 3, xp32bit, win7-64, and Debian test release. smile Back in a flash!

Use KTD? I'm using nLite to create the bootable ISO from this, I assume that's ok?

mr_smartepants wrote:

OK, I understand your frustration.  But I have zero experience with ubcd4win so I really cannot help you there.
What I was hoping was that you would do a standard integration (no ubcd4win) so we could determine if it was a DriverPacks fail or ubcd4win fail.
I'll have to remove those beta .inf files while I process the graphics DriverPacks for final status.  We'll work on this problem in the nightlies where all the cutting-edge stuff happens. wink

Our mantra is "Stability before currency".  And the graphics DriverPacks are more stable now than they've ever been!

I tried to just extract the N3 directory, rename the N3 folder name to files, put that into the 3rd party section and rebuild with the below entries in the 3rd party inf file:

[WinntDirectories]
a=nview,1

[SourceDisksFiles]
files\nvdm.inf=20,,1
files\advanced.tvp=a,,1
files\default.tvp=a,,1
files\nvsvc32.exe=2,,1
files\keystone.exe=2,,1
files\nvappbar.exe=2,,1
files\nvapps.xml=2,,1
files\nvdspsch.exe=2,,1
files\nview.dll=2,,1
files\nvshell.dll=2,,1
files\nvtuicpl.cpl=2,,1
files\nvcpl.dll=2,,1
files\nvcpl.cpl=2,,1
files\nvwimg.dll=2,,1
files\nwiz.exe=2,,1
files\nvhotkey.dll=2,,1
files\nvmctray.dll=2,,1
files\nvshell.dll=2,,1
; begin Locale
files\nvmccs.dll=2,,4
files\nvmccssr.dll=2,,4
files\nvdispsr.dll=2,,4
files\nvgamesr.dll=2,,4
files\nvmoblsr.dll=2,,4
files\nvvitvsr.dll=2,,4
files\nvwssr.dll=2,,4
; end Locale
files\nv4_disp.dll=2,,1
files\nvcuda.dll=2,,1
files\nvdisps.dll=2,,1
files\nvmccss.dll=2,,1
files\nvmobls.dll=2,,1
files\nvvitvs.dll=2,,1
files\nvwddi.dll=2,,1
files\nvwss.dll=2,,1
files\nvcod.dll=2,,1
files\nv4_mini.sys=4,,1
files\nvoglnt.dll=2,,1
files\nvwdmcpl.dll=2,,1
files\nvmctray.dll=2,,1
files\nvwddi.dll=2,,1
files\nvcpluir.dll=2,,1
files\nvgames.dll=2,,1
files\nvexpbar.dll=2,,1
files\nvcpl.hlp=21,,1
files\nvwcplen.hlp=21,,1

But it does the same thing as my own saying nv4_disp.dll failed to load. It has the correct name entry, so it does see it, like my own. I assume it fails for the reason you specified previously. Be nice if there was some log file to view which gave a bit more specifics then the little event viewer entry in winpe. Which of course is about 0 help to you I know. I'm guessing the building of the driver base for UBCD4win skips many of the included driverpack entries for stablity reasons since this is a PE build. But again only guessing. Thanks for trying anyhow. Hope something comes about, otherwise I'll just keep hackin' away at it til I finally pop a blood vessel or something. smile

Maybe because I'm not including the security catalag (.cat) file? Hmm...have to try again. Frisbee time again!

DPs_BASE.log
DPsFnshr.log (from %windir%)
setup***.log (from %windir%)

All I did with the test pack above was add the .infs from the beta you linked to DriverPack Graphics C\N3 (175.16).  It should work, but I need to see the logs to see why it doesn't.
Thanks for testing.

Yeah, I'm unsure as to what the deal is. It still doesn't work. I wiped the install, and started from scratch, but I still see nothing referencing nvidia being incorporated, searched the log for any mention in that section. I just don't know what your flags or ubcd4wins for that matter mean, so I'm shooting in the dark.

There are no Finisher or setup logs that I'm aware of for this. The only other relevant log file I think is the ubc4win.log. Here are the log files, one is with all of the driverpacks, other just with the graphics C you provided, and the ubcd log file.

I'd pose a parallel query over there, but it's a bit dead on that board at present. Are there specific files and/or flags in the DriverPacks config files to look for to see if the nvidia drivers are even making it to the image?

Thanks for the hard work man. Seriously appreciated.

Yeah, afraid not. Probably work if I had a 8000M or better, but not working for my go 7900gs.

mr_smartepants wrote:

I'm uploading a new DriverPack Graphics C for you to test.
http://driverpacks.sytes.net/driverpack … 911rc11.7z

Just let me know if it works on your hardware when integrated using DriverPacks BASE.

Nope. I slipstreamed it, seemed to integrate fine, but it's still stuck in the unknown devices section. =)

I uploaded the DriverPacks log file to rapidcrapola just in case.

Do I need to wax the released C? Maybe that's the issue.. I'll try again.

mr_smartepants wrote:

Welcome to DriverPacks! smile

yasha wrote:

Latest generic release from Nvidia

I understand requests for new drivers to be incorporated are a no-no,

What makes you think you can't request drivers? wink
If you don't ask, you don't get! big_smile

The link you provided is for older beta drivers.  The latest WHQL (our favorite) nvidia notebook drivers are 186.81 and are listed here.
But you're absolutely correct.  over 99% of the HWIDs listed in those notebook drivers are not included in our DriverPacks.  I take responsibility for that.  I'm sorry to have left those out.
But in order to add these, I will have to break driver-signing for these notebook drivers.  This is because Nvidia intentionally introduced a fault to prevent driver integration (you saw this firsthand.)
Without modifying the .inf, you'll get a filecopy error around T-34 for NvCplSetup***.exe.

I can add these and they won't interfere with the current drivers.
I'll be providing a link for you to test.  You feel up to the challenge?

See, that wasn't so bad was it?  We don't bite (very often). smile

Most certainly up for it! I got mine to install and read, but yeah, it fails to load, scrambles the monitor ID on the laptop, and other funkiness. smile

Well, I just saw the sticky and such about requesting "new" nvidia driverssets, just wanted to make sure I wasn't posting off-base and it was just my lack of research that was causing the lack of my laptop driver pwnage. smile

I put that older link up as the one you list doesn't incorporate the "go 7900" series, think the "8000M" series is as far down as it goes. I'm unsure how relevant that is though, as I'm sure the entries could probably be added and these drivers work fine. smile

Latest generic release from Nvidia


I'm using a Dell XPS M1710 with a Nvidia go 7900GS card in it. This is actually good for a fairly large number of laptops out there (higher end) as many mobile/notebook video card/chipsets are incorporated in this driver. I've tried to 3rd party this unsuccessfully so far for use in the UBCD4win, but it would be great if these were actually incorporated into the actual released driverpack.

I understand requests for new drivers to be incorporated are a no-no, but the less than 8000 series mobility drivers I don't believe are as yet incorporated. Most of the hardware is unrecognized by the driverpacks, but the other important ones are at least wired/wireless network, it's just the graphics driver missing that's foremost on my mind at present. smile

Just in case I am wrong, and it's just my specific laptop (XPS M1710) being a pain, here's the HWID info:

=========== 
PCI Devices 
=========== 
PCI\VEN_1180&DEV_0832&SUBSYS_01CE1028&REV_00\4&35BAB052&0&08F0: Ricoh 1394 OHCI Compliant Host Controller
PCI\VEN_8086&DEV_27C4&SUBSYS_01CE1028&REV_01\3&18D45AA6&0&FA: Intel(R) 82801GBM/GHM (ICH7-M Family) Serial ATA Storage Controller - 27C4
PCI\VEN_8086&DEV_27D4&SUBSYS_01CE1028&REV_01\3&18D45AA6&0&E2: Intel(R) 82801G (ICH7 Family) PCI Express Root Port - 27D4
PCI\VEN_1180&DEV_0843&SUBSYS_01CE1028&REV_01\4&35BAB052&0&0AF0: Ricoh SD/MMC Host Controller
PCI\VEN_8086&DEV_27C8&SUBSYS_01CE1028&REV_01\3&18D45AA6&0&E8: Intel(R) 82801G (ICH7 Family) USB Universal Host Controller - 27C8
PCI\VEN_8086&DEV_27D6&SUBSYS_01CE1028&REV_01\3&18D45AA6&0&E3: Intel(R) 82801G (ICH7 Family) PCI Express Root Port - 27D6
PCI\VEN_1180&DEV_0852&SUBSYS_01CE1028&REV_05\4&35BAB052&0&0CF0: Ricoh xD-Picture Card Controller
PCI\VEN_8086&DEV_27C9&SUBSYS_01CE1028&REV_01\3&18D45AA6&0&E9: Intel(R) 82801G (ICH7 Family) USB Universal Host Controller - 27C9
PCI\VEN_8086&DEV_27D8&SUBSYS_01CE1028&REV_01\3&18D45AA6&0&D8: High Definition Audio Controller
PCI\VEN_14E4&DEV_1600&SUBSYS_01CE1028&REV_02\4&EB643FB&0&00E2: Broadcom NetXtreme 57xx Gigabit Controller
PCI\VEN_8086&DEV_27CA&SUBSYS_01CE1028&REV_01\3&18D45AA6&0&EA: Intel(R) 82801G (ICH7 Family) USB Universal Host Controller - 27CA
PCI\VEN_8086&DEV_27DA&SUBSYS_01CE1028&REV_01\3&18D45AA6&0&FB: Intel(R) 82801G (ICH7 Family) SMBus Controller - 27DA
PCI\VEN_8086&DEV_2448&SUBSYS_01CE1028&REV_E1\3&18D45AA6&0&F0: Intel(R) 82801 PCI Bridge - 2448
PCI\VEN_8086&DEV_27CB&SUBSYS_01CE1028&REV_01\3&18D45AA6&0&EB: Intel(R) 82801G (ICH7 Family) USB Universal Host Controller - 27CB
PCI\VEN_8086&DEV_4229&SUBSYS_11018086&REV_61\4&E11C65&0&00E1: Intel(R) Wireless WiFi Link 4965AGN
PCI\VEN_10DE&DEV_0298&SUBSYS_019B1028&REV_A1\4&21D6A3AB&0&0008: NVIDIA GeForce Go 7900 GS
PCI\VEN_8086&DEV_27A0&SUBSYS_01CE1028&REV_03\3&18D45AA6&0&00: Mobile Intel(R) 945GM/GU/PM/GMS/940GML/943GML and Intel(R) 945GT Express Processor to DRAM Controller - 27A0
PCI\VEN_8086&DEV_27CC&SUBSYS_01CE1028&REV_01\3&18D45AA6&0&EF: Intel(R) 82801G (ICH7 Family) USB2 Enhanced Host Controller - 27CC
PCI\VEN_1180&DEV_0592&SUBSYS_01CE1028&REV_0A\4&35BAB052&0&0BF0: Ricoh Memory Stick Controller
PCI\VEN_8086&DEV_27A1&SUBSYS_01CE1028&REV_03\3&18D45AA6&0&08: Mobile Intel(R) 945GM/GU/PM/GMS/940GML/943GML and Intel(R) 945GT Express PCI Express Root Port - 27A1
PCI\VEN_8086&DEV_27D0&SUBSYS_01CE1028&REV_01\3&18D45AA6&0&E0: Intel(R) 82801G (ICH7 Family) PCI Express Root Port - 27D0
PCI\VEN_1180&DEV_0822&SUBSYS_01CE1028&REV_19\4&35BAB052&0&09F0: SDA Standard Compliant SD Host Controller
PCI\VEN_8086&DEV_27B9&SUBSYS_01CE1028&REV_01\3&18D45AA6&0&F8: Intel(R) 82801GBM (ICH7-M/U) LPC Interface Controller - 27B9
PCI\VEN_8086&DEV_27D2&SUBSYS_01CE1028&REV_01\3&18D45AA6&0&E1: Intel(R) 82801G (ICH7 Family) PCI Express Root Port - 27D2
24 matching device(s) found.
 
=========== 
USB Devices 
=========== 
USB\ROOT_HUB\4&A427C5E&0                                    : USB Root Hub
USB\ROOT_HUB20\4&180AD589&0                                 : USB Root Hub
USB\VID_0B97&PID_7761\6&2B90F3C&0&2                         : Generic USB Hub
USB\VID_0B97&PID_7762\7&15477028&0&2                        : O2Micro OZ776 USB CCID Smartcard Reader
USB\VID_413C&PID_8103\6&2B90F3C&0&4                         : Dell Wireless 350 Bluetooth Module
USB\VID_413C&PID_A005\5&1C8BA3EB&0&1                        : Generic USB Hub
USB\ROOT_HUB\4&2D7DDD1A&0                                   : USB Root Hub
USB\ROOT_HUB\4&30E7D614&0                                   : USB Root Hub
USB\ROOT_HUB\4&6D88364&0                                    : USB Root Hub
9 matching device(s) found.
 
============= 
Input Devices 
============= 
No matching devices found.
 
============ 
ACPI Devices 
============ 
ACPI\PNP0A03\2&DABA3FF&1                                    : PCI bus
ACPI\PNP0B00\4&17AA870D&0                                   : System CMOS/real time clock
ACPI\PNP0C01\1                                              : System board
ACPI\PNP0C01\2                                              : System board
ACPI\PNP0C01\3                                              : System board
ACPI\PNP0C01\4                                              : System board
ACPI\ACPI0003\2&DABA3FF&1                                   : Microsoft AC Adapter
ACPI\PNP0C04\4&17AA870D&0                                   : Numeric data processor
ACPI\GENUINEINTEL_-_INTEL64_FAMILY_6_MODEL_15_-_INTEL(R)_CORE(TM)2_CPU_________T7200__@_2.00GHZ\_0: Intel(R) Core(TM)2 CPU         T7200  @ 2.00GHz
ACPI\PNP0C0A\1                                              : Microsoft ACPI-Compliant Control Method Battery
ACPI\PNP0C0C\2&DABA3FF&1                                    : ACPI Power Button
ACPI\PNP0C0D\2&DABA3FF&1                                    : ACPI Lid
ACPI\PNP0C0E\2&DABA3FF&1                                    : ACPI Sleep Button
ACPI\GENUINEINTEL_-_INTEL64_FAMILY_6_MODEL_15_-_INTEL(R)_CORE(TM)2_CPU_________T7200__@_2.00GHZ\_1: Intel(R) Core(TM)2 CPU         T7200  @ 2.00GHz
ACPI\PNP0C14\0                                              : Microsoft Windows Management Interface for ACPI
ACPI\PNP0C32\0                                              : Direct Application Launch Button
ACPI\PNP0F13\4&17AA870D&0                                   : PS/2 Compatible Mouse
ACPI\THERMALZONE\THM_                                       : ACPI Thermal Zone
ACPI\PNP0000\4&17AA870D&0                                   : Programmable interrupt controller
ACPI_HAL\PNP0C08\0                                          : Microsoft ACPI-Compliant System
ACPI\PNP0100\4&17AA870D&0                                   : System timer
ACPI\PNP0103\4&17AA870D&0                                   : High precision event timer
ACPI\PNP0200\4&17AA870D&0                                   : Direct memory access controller
ACPI\PNP0303\4&17AA870D&0                                   : Standard PS/2 Keyboard
ROOT\ACPI_HAL\0000                                          : ACPI x64-based PC
ACPI\PNP0800\4&17AA870D&0                                   : System speaker
26 matching device(s) found.
 
============ 
 HDA Audio 
============ 
HDAUDIO\FUNC_01&VEN_8384&DEV_7690&SUBSYS_102801CE&REV_1022\4&3B2AD384&0&0001: High Definition Audio Device
1 matching device(s) found.
 
============ 
RAID Devices 
============ 
PCI\VEN_8086&DEV_27C4&SUBSYS_01CE1028&REV_01\3&18D45AA6&0&FA
    Name: Intel(R) 82801GBM/GHM (ICH7-M Family) Serial ATA Storage Controller - 27C4
    Hardware ID's:
        PCI\VEN_8086&DEV_27C4&SUBSYS_01CE1028&REV_01
        PCI\VEN_8086&DEV_27C4&SUBSYS_01CE1028
        PCI\VEN_8086&DEV_27C4&CC_010180
        PCI\VEN_8086&DEV_27C4&CC_0101
    Compatible ID's:
        PCI\VEN_8086&DEV_27C4&REV_01
        PCI\VEN_8086&DEV_27C4
        PCI\VEN_8086&CC_010180
        PCI\VEN_8086&CC_0101
        PCI\VEN_8086
        PCI\CC_010180
        PCI\CC_0101
1 matching device(s) found.

Respectfully,
Wayne (aka Yasha)