Search options (Page 1 of 2)

XP x64 thrashes Vista x64 on a lot of fronts.

In fact XP x64 thrashes all other Microsoft Windows OS's overall.

For example - the FPS in games with XP x64 is far higher than in Vista x64.

I wonder why there are no driverpacks, I can understand why there is no BASE - it would need coding etc but with just driverpacks, DPINST.EXE works, you could at least do it that way post install, that is if there were any packs in existence, there arn't, not that I know of, shame because last time I used DPINST.EXE with my own drivers, every single one installed fine - which is more than I can say for the x86 version of DPINST.EXE on x86.

Look at the purple bar, thats XP x64

http://www.imagebam.com/image/9786675364575

Look at the last test, "PassMark" where XP x64 scores 670 (higher than any other Windows OS tested) thats 6% higher than Vista x64 can muster.

Also theres quite a gulf (of +18% in XP x64's favour) on the "Disk Mark" test.

So until Microsoft DO REALLY bring out a faster OS than XP x64, as opposed to a load of propaganda about how Vista x64 "has to be better" yada yada, I won't be "upgrading" to the slower Vista x64 anytime soon - well actually never, because its slower. Why would I change to a slower operating system? Thats just silly.

Theres nothing in Vista for me, otherwise I would have "upgraded" to it ages ago.

Over a month later, http://www.radarsync.com/vista/ still says "Note: Free links have been temporarily disabled." So they are still selling free drivers from their website! Its not legal.

The code I used is the exact code muiz posted on the previous page, except I didn't have the WAIK installed so I dumped a load of files in a "TOOLS" folder and changed a few things in the very beginning of the code, put that TOOLS folder next to the compiled AutoIt3 file.

The only thing stopping me is this damn "Drivers.xml" file.

I don't know where it comes from, or why the au3 code has a reference to it.

Surely anyone else trying to do this is having this exact problem?

Theres no "Drivers.xml" file on the root of the Vista DVD, but the au3 code expects that file to be there!

I never thought this could be done!

I tried this and got an error saying "Fehler" and "Couldn't open mixer"

Not really sure which CMD file to use from the first post.

1 - I slipped all driverpacks using method 2.

2 - I didn't use KTD.

3 - I want to extract the driverpacks, install drivers and then cleanup the driverpacks.

Should I use the first file "doPNF.cmd" and just add this line to the end:

start %SystemDrive%\DPsFnshr.exe

Just because I don't want to keep anything on the drive, I just want to do:

1 - Extract drivers.
2 - Install drivers.
3 - Delete drivers.

OK I have the next question then - do you even need to rename the pack?

Well, of course yes it can't have its original long name, but I mean, say you slipstreamed DP_Graphics_A_wnt5_x86-32_706.7z a while back and now you want to test the new "Graphics A" pack here, the old pack in the OEM folder on your CD is going to be called "DPGA706.7z" so can you put the test pack in and rename it to "DPGA708.7z" and it will just work, or does it HAVE TO be called "DPGA706.7z" like it was originally?

Hmmmmmm.... sorry about asking these dumb questions here but please, just one more! Sometimes I notice the D folder stays on the systemdrive... AFAIK this just randomly happens on Windows 2000, its not always the case, I even put my own runonce in that sometimes doesn't work, is it safe to delete that D folder when Windows logs in for the first time or are there still drivers being installed at that point? As I understand the packs, all drivers install as early on as possible. The DPsFnshr.exe runs to delete the D folder from WINNT.SIF, maybe my command is conflicting, so is it safe to delete the D folder with "RD /S /Q %SystemDrive%\D\" on the first login of Windows? Not sure why the finisher is set to "command9" in WINNT.SIF but I changed this to "command1" and had my own CMD running as "command2" to install a few programs, so if that CMD that I am running deletes the D folder, is that safe to do at that point? Windows will not log in until the WINNT.SIF commands are all done and the finisher has completed and part of that is deleting the D folder.

Windows is just stupid though - you can put stuff in CMD files you have tested over and over again then when it comes to running the install, the command doesn't work. This is Windows for you I guess. I wouldn't mind if some file was locked inside the D folder but it leaves the ENTIRE 1.6Gb folder there. Again though - I am not blaming the driverpacks, I know its Windows' fault, when ever isn't it Windows fault, sigh.

mr_smartepants I tested the updated pack and this also works,
same result as the last test, on nVidia 8800GTS.

Still got that pop-up though (asking for a reboot)

Thanks all, especially Jaak - that script did the trick.

I have an 8800GTS myself, I might be able to test the new Driverpack if I get the time,
I am really busy at the moment though.

The finisher just runs from C:\

So you reckon the very last thing the driverpacks do is deletes the DPsFnshr.exe file?

It makes logical sense to me.

I think the reason the D folder was left over is because - and this was in VMware - it takes
about 30 seconds to delete, its got thousands of tiny files inside it thats why, but if the D
folder is removed before the DPsFnshr.exe cleans itself up then its all fine with how ive
done it - a command that loops every 3 seconds checking if the DPsFnshr.exe is present
on %SystemDrive%

If the DPsFnshr.exe file is there, the bat file loops, as soon as the DPsFnshr.exe file is gone
(meaning the D folder must be deleted and the driverpacks finisher is fully finished for good)
then the bat file carries on, installing a few progs, regtweaks that need a reboot etc then the
system reboots.

Many thanks to Bashrat and anyone else who managed to get the finisher to delete without
a reboot It just gets better and better every time a new BASE comes out!