You are not logged in. Please login or register.
DriverPacks.net Forum » Posts by mr_smartepants
Here's an experimental DP using the latest nvidia drivers. FOR TESTING ONLY, DO NOT USE ON PRODUCTION MACHINES.
DP_Graphics_A_wnt5_x86-32_80227_nightly
MD5: 4022123512F0094929740ABB14C37477
Size: 73.6 MB
Changed:
N1\
Changed path from N\1\ to N1
Updated to version 174.16, 02/19/2008
A1\
Changed path from A\1\ to A1
Updated to Catalyst 8.2, DriverVer 01/22/2008, 8.453.0.0000
Fixed uninstall fault in mobility.inf (not reported)DP_Graphics_A_wnt5_x86-32_8012 & DP_Graphics_A_wnt5_x86-32_80218_nightly all different is "Updated to Catalyst 8.2"! But "Changed path" in old version!
Yes, the nightly versions are testing versions and they are meant for our testing team to use. The new paths are to reduce the Method-1 path limit.
Thank you for confirming the new drivers work. What card did you test them on?
Last Nvidia version is 169.32 whql - not 169.21 in Graphics A!
http://us.download.nvidia.com/Windows/1 … l_whql.exeLast ATI version is 8.2 whql - not 8.1 in Graphics A!
http://game.amd.com/us-en/drivers_catal … radeonx-xp
Welcome to DriverPacks.
Yes, I had released a newer DP with the 8.2 Catalyst in the nightlies and I forgot to post it here. First post updated.
You are incorrect about the nvidia drivers however. The latest release for GeForce FX, 6, 7, and 8 series GPUs is 169.21.
It's possible you got ahold of leaked or beta drivers. But the www.nvidia.com website still lists the 169.21 drivers as current.
As a general rule, we use only WHQL-certified drivers directly from the vendor. Never beta.
Don't worry, I'm sure they'll release updated drivers soon that incorporates the newer cards. But for now, there's nothing wrong with the current G_A nightly in the first post and it's being made ready for release.
Yes, those Zalmans are the best when it comes to active cooling. But I'm going towards silence (well, quiet anyway). Since I already have two 120mm fans (one will be disconnected) in that quadrant of the case, I'm going to build a duct to link the fan openings to the CPU heatsink so all the exhausted air has to go through the heatsink first. Kinda like what Dell does in their GX series.
You're welcome. We're always glad to help.
But DriverPacks were never meant to work under virtual machines (VMware, VirtualPC, or VirtualBox). They won't cause problems, but they won't do anything either.
Test on a real PC.
Is your wireless adapter turned on?
Sometimes there's a mechanical switch to enable/disable the wireless card (for airports). I ran into a problem once where the wireless driver refused to load unless the wireless was turned on.
Since it's on the PCI bus, and you've got a PCI bridge, it might be hiding behind the PCI bridge. Try installing the Intel drivers for your chipset here and see if it shows up.
Yes, and DON'T select the i386 folder itself, select the folder that CONTAINS the i386 folder.
It might help to remove any funky characters in the folder name.
PLEASE help me by supplying the info on the model of the WIRELESS adapter/card and the compatible DRIVER for this particular notebook...
Hi and welcome to DriverPacks. Actually, YOU need to provide the details of your hardware to us. We're not clairvoyant.
You can use the HWID utility in my signature. You'll also need to provide the name of the device (what Vista says it is, or what's listed on the sticker.)
Translated:
Well this post did I have a doubt that integrates the SATA drivers with the genre and I Splitream a folder OEM but I have another folder $ OEM $ interferes with something or I do not have to put everything in the folder without signs OEM
The two OEM folders are perfectly normal. The $OEM$ folder contains the cmdlines.txt file which enables the RunOnceEx option. Anything contained within the $OEM$ folder will get copied to the C: drive during XP install.
The OEM folder is where all of the DriverPacks are stored.
As long as you integrate by using the DPBase, everything will be fine.
Did you test your disc? Did it work OK or were there problems?
That is one nice rig, glad you choose GigaByte, nice motherboards.
My only question is: why Vista !!!
My choice was between gigabyte and MSI, I like the idea of the dual-bios on the gigabyte (nuked too many boards during bios-flash).
As to the XP/Vista debate...
I've read that XP pro doesn't utilize multiple cores all that well. It's just a kludge-job at multi-threading at best. Vista was designed to take advantage of multiple cores at the OS level, sending OS-threads to different cores.
Games for the most part are single threaded, hence the XP partition. I do a lot of video transcoding (home server/NAS in the works) which use every available core, hence the Vista partition.
We'll see.
Besides, I'm going through a mid-life crisis, and this was cheaper than a Ferrari...or a blonde. 
Do the old games not work on Vst or do you want to keep the OS clean (for instance of nasty copy protection that gets installed along with the games...).
No, it's just a known fact that's been proved over and over again that XP is about 10-20% faster in gaming than Vista. Besides, I can have an XP build that's stripped down and lean for gaming, then later boot into Vista that's cluttered and functional for everything else.
I hear they released SP1 integrated DVD OEM iso's on TechNet. I ordered an OEM system builder DVD from newegg...OEM disc...OEM license...:)
Although there's nothing like having the properer slipstreamed original press DVD, seeing as you and me both probably customize a lot on the discs (hence including the need to burn it again anyway), getting an ISO is more than a fair trade-off.
At least they do hand them out (if only to subscribers).
I'm actually quite upset about that. I was part of the testing for both the beta and RC of Vista and I never did receive my promised Ultimate DVD for contributing. I'm tempted to return my OEM DVD back to newegg unopened and use my RTM copy until the SP1 integrated discs show up. I figure M$ owes me one friggin' ISO!
The original fans in that case aren't going to last long. I already have a boxload of Yate Loons (same as Nexus) waiting in my attic. I'm really going to enjoy this build!
I was going to dual-boot XP for gaming, Vista for everything else. Not that I have much time for gaming, but hey.
I'll still run XP on my notebook. Vista beta 2 choked it into nothingness!
The word is that SP1 for x64 Vista is already on MU as of yesterday. Just my luck, if I had held out for another few weeks, I'd get the integrated SP1 DVD. 
Oh well, vLite to the rescue!
I don't have the sp1 link on my connect.ms login though. It's only a matter of time til they release a standalone installer.
I hear they released SP1 integrated DVD OEM iso's on TechNet. I ordered an OEM system builder DVD from newegg...OEM disc...OEM license...:)
I have a nagging suspicion that 8800GTS fan is going to be the loudest component in the rig. Nothing a water cooling setup can't handle.
Well, I finally blew some $$$ and bought a new system from Newegg.
The parts should be here in a week or two.
For those interested, I ordered:
Case: Antec P180
Mobo: GIGABYTE GA-EX38-DS4
CPU: Intel Core 2 Quad Q6600 Kentsfield 2.4GHz (I really wanted the Q9450 Penryn but nobody has stock)
CPU cooler: Scythe SCINF-1000 120mm CPU Cooler (ducted to rear exhaust fan for silence)
RAM: 8 GB GeIL 4GB(2 x 2GB) plus OCZ 4GB (2 x 2GB) 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400) Dual Channel
Video: EVGA 512-P3-N841-AR GeForce 8800GTS (G92) 512MB (Finally get to test out my G_A nvidia DP!)
PSU: SeaSonic M12II SS-500GM ATX12V 2.2 /EPS12V 2.91 500W Power Supply
DVD: SAMSUNG 20X DVD±R DVD Burner Black SATA Model SH-S203B (I'll still keep my trusty Plextor Edit: it died )
HDD: Seagate Barracuda 7200.11 ST3750330AS 750GB 7200 RPM SATA 3.0Gb/s Hard Drive (new one with 32mb cache)
Also grabbed a copy of Vista Ultimate 64-bit (Go legit or go home!)
$1500 shipped.
I'll post some pics once I get the beast up and running. I may buy a water cooling kit this summer, we'll see how the Scythe holds up first.
Of course, I bought all of this with YOU GUYS in mind. I mean, I owe it to you to have a decent "testing" rig...right? 
Pictures (1024x768 png-24 1.5Mb each):
Parts
Heatsink
mounted 1
mounted 2
More to follow.
*Edit
Installed OCZ 4GB DDR2 kit (2x 2GB DDR2 800, 5-4-4-12)
Got ASUS Xonar sound card
Accidentally killed my trusty Plextor PX-760A DVD-DL burner.
It reads discs OK, but gives "Power calibration error" whenever you try to burn anything.
Are you running Vista?
I've got almost the same DriverPacks you have but mine are relabeled:
ATICCP.ins
bin
DP_Modem.7z
DP_Modem.txt
DPC801c.7z
DPCP7122.7z
DPCP7122.txt
DPGA8021.7z
DPGA8021.txt
DPGB8012.7z
DPL8021.7z
DPM8021.7z
DPSA8021.7z
DPSB8021.7z
DPSB8021.txt
DPW802_N.7z
DPW802_N.txt
The corresponding txt files just say:
This file had to be renamed to be compatible with 8.3 filenames.
Original filename: DPW802_Nightly.7z
speaking of which...what is the most current nightly of Base?
I've been using RC2 for a while now since RC3a had issues for me.
You mention the G_A DP (which I have a copy of on my desktop) and in the entire DP there is only a single file that's not 8.3 compliant in the A1/B_58538 directory.
amdpcom32.dll
There are no non-8.3 compliant files in N1.
Are you renaming the DriverPacks in any way(before/after integration)?
During integration, DPBase automatically renames the DriverPacks for 8.3 compliance and even places a .txt file in the OEM folder telling you which DriverPacks were renamed and to what.
Besides, 8.3 filenames are only a concern during textmode setup. Once setup is complete and the finisher runs at either GUIrunonce or ROE, long-filename support is enabled anyway.
Anyway, you could have a DP with the filename DP_Graphics_A_wnt5_x86-32_802_nightly_big_hairy_long_file_name_wowthisisreallylong.7z and it'll still get truncated down to DPGA802n.7z during integration by the Base.
I agree with Helmi. In each and every integration I've done, the DP Base has always renamed the DriverPacks into the OEM folder in the 8.3 format.
I never use method 1 though, but I doubt that would be any different.
and yours tutorial's quote;
http://forum.driverpacks.net/viewtopic.php?id=1449mr_smartepants wrote:"If all went well, then build your Windows source into an ISO file (nLite or RyanVM Integrator),"
this sentence..I think I can't understood..after read this, I supposed, first we must use DPs_BASE and then nlite or RVM..
Sorry for the misinformation. I've corrected that line in the tutorial. I apologize for the text not translating well.
As the others posted, the order I use to integrate is:
1) RVM Integrator using RVM update pack
2) nLite for removals/tweaks and to integrate IE7 & WMP11
3) RVM Integrator for addons
4) DriverPacks
5) Build ISO with nLite (I think it's better).
Interesting.
I look forward to trying this on a running system.
Was it written using AutoIt?
Try installing the Dell-supported drivers first from here.
If that doesn't work, try the newer drivers from Intel here.
Try using a clean XP source and reslipstream SP2 and retest.
thanks.
We learn something new every day.
Yes, Google is a wonderful resource.
I tried Virtual PC 2007 first (because it was free), but half of my WinXP builds would get an error in a file in a sub-folder of \I386\ASMS\ that would stop the install. It wasn't always the same file, but GDIPLUS.MAN was one of them. I tried VMware with the same ISO's and it NEVER had that error.
It's really too bad... I liked the video driver support better on Virtual PC.
Ed
Are you using VPC to test your .ISO files or the actual burned CD/DVD?
If this is happening with .ISO files, it might be a corrupted gdiplus.dll file. Grab a replacement from here:
http://dll-files.com/dllindex/dll-files.shtml?gdiplus
This error is almost always caused by a botched SP2 slipstream, a dirty disc, or a failing optical drive.
http://www.annoyances.org/exec/forum/winxp/t1017113594
http://www.hardwareanalysis.com/content/topic/15875/
IIRC, the PHP code uses a referer line to activate the download. Some AV programs with firewalls (Symantec does this!) will block the referer and you'll receive the 'anti-leech' warning.
The solution is simple, just disable your firewall for the duration of the download (don't worry, there's no spyware involved).
I was hit by this several times until I upgraded to the new Symantec Endpoint Protection which fixed the blind referer issue.
There are times when the nightly versioning system is used for the final DriverPacks however.
When a bug is discovered in a final DP, a .V update is posted to fix the issue.
DriverPacks.net Forum » Posts by mr_smartepants
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
[ Generated in 0.101 seconds, 6 queries executed ]
