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

with ICH7 chipset and a Nvidia 7900 it should be pretty perky in 2d mode (explorer, IE, device manager, etc...)

OH, and I HAVE played DOOM in a PE before. No PE is complete untill it has at least "Some" games included for those frustration moments and long waits for scans while your bored.

@Wayne
Details, Details, Details... are the key to everything.
Even with a VESA driver I have no lag like what you describe, even when viewing full screen DVD movies on my PE.

I've built plugins for custom video drivers before, but without having the hardware here to work with, it's not even an option.
My older rigs have ATI Graphic boards and I like to keep a PE around with nothing but games on it for "Play Time" when I have nothing to do but wait anyways.

I am trying to port some of my custom built to the masses via the SystemCore I wrote for the UBCD4WIN project, and it's no small task.
Most plugins contain somewhere between 16 & 200 lines of code, the core has 24,000+ which does not even count the underlying plugins that support it.
Run a text search for "hilander999" on the OEM1 & PLUGINS folder, and you will see an interesting pattern.

If your not interested in furthering the development or testing fixes, let me know so I'm not waisting my time replying here.
If you are interested, and are willing to test some beta software, I need as much detail in your responces to me that you can describe.

~The Devil is in the details.

If you want something in PE, either he can do it, or it can't be done.

He wasn't kidding about fixing it - if you provided GOOD details...

restating the layers of drivers thing.
Think of an OSs drivers like a pyramid and graphics drivers like the capstone.
- Your BASE is the chipset drivers (which are not installed in PE)
- On top of the base goes every thing else. we are starting at a disadvantage. basic chipset acceleration is gimped
Mass Storage, USB, RAM, Console and other medium level functions depend on chipset. (gimped by dependency)
Mass takes a beating here, since everything is loaded into RAM not a huge deal, unless we need something from HDD or ODD.
- Sound and Video are at or near the top of our pyramid and likewise depend on the blocks below them to be solid. IE a screen refresh might be slow due to increased lag on IO / Mass Storage or even RAM itself. many sound drivers require the HDA driver installed first, As john pointed out this will require one extra loop through HWPNP.EXE so HDA can be present before the sound Hardware is visible, and eligable for the driver. - i don't even want to think too much about video... Wheeew

Try and give Hilander as much detail as you can!

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. In fact you may have better luck from safemode You will be able to run a virus scan

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.

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.

Describe the "LAG" in some detail, when, where and what your running that seems "Slow".

I am working on some cool sh1t that envolves PNP and noticed that one major provlem is driver stacking or layers of devices that support other devices.

Sometimes it takes 3 runs of HWPNP.EXE to enumerate all the connected drivers.
You may notice a whole slew of non-detected devices in device manager with yellow ! marks through them and after running HWPNP a few extra times, these devices will connect with each other.

Short version, installing one device reveals 3 other devices that may also reveal yet another connected device, and so on...

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.

IF you want full blown windows performance you need to install windows.
for example mass storage drivers are the Text Mode drivers ONLY... (16 bit)
not the good PnP performance drivers, etc... PE will not reach the performance levels of the full OS, it can't.

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

@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.

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.

@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.

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.

RULE #1 I have down pat...
- "Forget everything you know about regualar windows"

@Erik
Took me 3 months to explain the PE driver thingy to Jeff, so don't feel bad. (His inf entries look ok and is in pebuilder format, not either of the 2 completely different windows formats. lol )

Whew!  Thanks.  I thought I was going nuts there.  Good luck and get well soon!

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.

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.

@Erik
Took me 3 months to explain the PE driver thingy to Jeff, so don't feel bad. (His inf entries look ok and is in pebuilder format, not either of the 2 completely different windows formats. lol )

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

Awesome.  Thank you.  At least we know the driver itself works fine on your system.

OK no problem.  Thanks for the info Jeff, I had assumed the PE files would be different, but I didn't know HOW different!

cdob pops in here often... but i may cross post...

@ Erik - the layout of the inf is specific to PEBuilder (the main exe for Bartpe disc creation)