Various problems with latest wnt5_x86-32

They have not been integrated.

One of the first things I did upon fresh Windows XP installation was to download driverpacks, verified so the checksums matched, and installed them with the tool I've mentionned.

P.S.: I've ran tool again (with CPU driverpacks) and have been able to reproduce the two first mentionned popups:

EDIT: I didn't expect was this wouldn't be silent, but during the install:
- a screen appeared, about CPU install, and I had to press finish because the install was stalled;
- immediately after that, a second screen (identical to the first one) appeared and I had to click finish;

- to reproduce the third popup, I'd likely have to reinstall Windows (I could). If I remember correctly, the third popup, which happened in the minutes following the two others, was about sound installation.

EDIT2: the only yellow exclamation marks to be found in the device manager seem not to be about sound or video, but rather "system devices," and are illustrated in the picture inside the rar archive posted in the first post.

EDIT3: here is a third picture, showing the driver contents of the add/remove programs page.

Last edited by twipley (2008-10-27 09:55:04)

I don't know. That's just plain weird, because I'd have sworn to successfully have installed drivers for the same hardware using the same tool and almost same official, i.e. non third party, driverpacks.

And now that doesn't work, and just to be sure I've tried by recreating my system partition anew, installed Windows, and re-downloaded driverpacks and driver updater (just to be sure), but it the was same as in first try.

But just for the fun of it I've took another computer (my laptop), reinstalled Windows, given it the same driverpacks and tool, and everything went fine, neither is there anything weird in the device manager.

Maybe I have hallucinated having used that driver updater tool in the past!

I'll try to see if jaws has anything to say on the subject...

1) the best thing for you to do is to use DriverPacks "disc" method to integrate your drivers into your source.
(drivers first install)

2) the next best thing for you to do is to use the Stand Alone Drivers (SAD) feature of base.
(software first install)

While I try Warm Snow, you think you can dig me out the two other links? e.g. I've fell on the SAD topic earlier, but this all was a bag of nonsense to me (I'm no techie), I mean, there was way to much written!

I just want a simple program which I can bring to my friends' homes via CD with driverpacks and help them... and I really don't understand why this hasn't worked on me, maybe someone with the same CPU as me can try to install CPU driverpacks with jaws' tool to further investigate the source of the problem?

Furthermore, some things I don't understand:
- is it normal, that in device manager I have these chipset exclamation marks (see picture); I wonder because I know the SM Bus controller written by NVIDIA doesn't really offer extra performance over native drivers
- is it normal, that the only drivers listed in Add/Remove programs are the ones shown in the picture?

I've started this topic today because of the need I feel to "investigate the source of the problem," because I'm pretty sure having installed the same drivers, under the same conditions, for the same hardware, with the same tool, and in a successful manner, in the past.

My feeling is that it's only a small factor at the cause of the problem!

And if the topic for jaws' tool has been stickied for that time, if it was so screwed by that time someone would already have replied, wouldn't it?

Peace out,
I'm tired.

EDIT: lol, at least that's not the fault of jaws' problem! because Warm snow's did exact same thing.
what can the source of the problem be?! it must be coming from me...

http://img443.imageshack.us/my.php?image=eega8.jpg

weird thing is that it isn't coming from my Windows CD or from driverpacks (as the exact same, even under the same circumstances worked on my laptop), and now it's not coming from jaws' tool either! weird stuff...

lol @overflow: "as i said i think you're the first one that has ever used it"
that's what I thought, but let me tell you this is one nice piece of a program!

Last edited by twipley (2008-10-27 12:00:06)

Okay, I've just reinstalled Windows with another Windows CD, but the problem really seems to be my PC because every other PC I try that on, and to my mind in the same circumstances, succeeds with drivers and everything! And every Windows installation I do on my PC (that were working a few months ago) now fails on automatic driver installation.

Otherwise my PC works great, it's just the drivers that doesn't get installed correctly...

I've compiled all the five pictures, the HWIDs and the log file.
In case you wanna check that out: http://tinyurl.com/bugreport

When I get the time I'll do a memtest but I doubt that's the problem.

no, and that's the other thing!

EDIT: it really seems to be none other fault than my PC!
strange thing is the exact same installation worked months ago.

- same hardware
- same Windows
- same driverpacks
- same tool used

- jaws/snow tool produces the same effect.

Last edited by twipley (2008-10-28 11:47:24)

if you mean by that resetting the BIOS, it's already done.

I don't know if I've got the knowledge to do that -- except reseating the hardware, of course!

In the meanwhile, I've tested installing with different Windows XP versions -- all worked fine, except driverpacks (snow/jaws).

I've also tested on VMWare! as you may already know, VMWare installs with the same CPU as the host, so I've just ran the CPU driverpack inside the guest using snow/jaws, but the same error happened! wow.

When I get some extra time, I'll try to reformat and see if drivers install well (this time, without driverpacks). Well, if that's the case I'll just have to stop using driverpacks for some time, but h*ll I can always recommend them to friends! :)

I've subscribed to this topic so if somebody write something here in the future I should be informed. Also, if I ever open my PC case and add/remove some piece of hardware that makes it working, I'll be sure to report it back here

thanks for the help people, it almost did it!

nope.