Hi All

Using Server 2003 Standard SP1 windows files, latest pe builder.

I seem to have an issue with my keyboard. I have tried PS/2 and USB on multiple machines physical and virtual. I have mouse connectivity, but never anything from the keyboard. No keys are responsive. The keyboard does work in bios. If I go to the keyboard layout selection app, and type something, I get a blue screen, stop code of 8E win32.sys. Any thoughts on where I should begin on this?

Thanks!

John

Hi Everyone

I am probably not giving enough information to you guys. What else should I be providing?

Thanks!

John

What you had is NOT:




It's most probably a 0x0000008E error, something that looks like this:


It is usually associated with bad ram (which is not your case) or with a "bad" WIN32K.SYS:
http://support.microsoft.com/default.aspx?...kb;en-us;834450
or in some cases with a conflicting driver (video?). Nvidia drivers caused that in the past.

There is also this:
http://msdn.microsoft.com/en-us/library/ms794023.aspx

I would vote for a "bad" driver:
http://aumha.org/a/stop.htm

IRQ conflicts may also be the cause.

It's one of those STOP errors that may be caused by almost anything.

However a "FULL" STOP code might help, i.e. EXACTLY what you see on the screen when it happens.

jaclaz

Here is the full stop error codes:

*** STOP: 0x0000008E (0xC0000005, 0xBF90697E, 0xF9EA6CB0, 0x00000000)

*** win32k.sys - Address BF90697E base at BF800000, DateStamp 42435de9


Being a bad driver would kind of make sense, as I don't get any keyboard response. What would the above messages indicate to you?

John

Broken hardware: bad CD media, RAM, PSU, cable, capacitors


Or half broken source files. Use other source files or slipstream SP2.

It would be first time I see a Virtual Machine with broken (Virtual) Hardware.

And I don't think as well that a VM uses a Nvidia driver, so it must be some other driver conflicting.

Which VM did you use?

Can you try another one?

Are you making a "Vanilla" BartPE or throwing in it every and each plugin you can find on the internet?

If the latter, try a simple build without adding ANY plugin.

jaclaz

Sorry for the lengthy delay in replying.

I managed to get this resolved. Strangely enough, I fixed it by burning it on a 32bit XP machine, instead of a 64 bit Vista. Did I miss something in the program reqs, or is this a strange new bug. Fwiw, this has happened on a lot of programs.


John

Strangely enough, you cannot find here:
http://www.nu2.nu/pebuilder/
any reference to "Vista".

Even more strangely , this sentence:


should hint that it was:

• tested and found NOT working on NT4/ME/9x
• tested and found FULLY working on 2000/XP/2003/BartPE

I guess we can also assume that it was:

• NOT tested on Vista, 2008, WIndows 7, DOS, Linux BSD and MAC OS, or on ANY other not mentioned Operating Systems.

Happy anyway that the problem was solved.

jaclaz

I believe paraglider runs PEBuilder on Vista so it can be done. I'm not aware of what considerations need to in place to do that though. I think there are a couple of plugins that can cause problems and need to be tweaked if the system is build on Vista.

John you saved my life. During repeated attempts of re-installing Windows XP SP3 on my laptop, I had the exact same problem as yours. I was going to smash my head against a wall. A google search on the error code was leading to fixes that had nothing to do with my pb.
Then I found your post, and I generated BartPE from windows XP 32 bits instead of Vista. And it worked!!! My tears of joy almost ruined my laptop again. Many thanks John!!!
I am going to post on http://www.ezbsystems.com/cgi-bin/ikonboard.cgi?act=ST;f=2;t=2440 that one should run peBuilder on Windows XP 32!