You are not logged in. Please login or register.
Active topics Unanswered topics
Search options (Page 51 of 159)
DriverPacks.net Forum » Posts by mr_smartepants
Well first thing you need to understand is that Server 2003 is NOT a normal operating system! It's a SERVER.
Second, AMD/ATI do not support their gaming cards (yours) in a server environment.
Third, as far as I know DirectX can't be installed in a server environment. So even IF you managed to get the XP drivers to work, you wouldn't be able to play any modern game anyway.
Get with the times and install Win7. You'll be MUCH happier.
Worst username ever! 
Moving to "other".
Try this: http://tinyurl.com/446fh7h
So, you're at post #1 and the only thing you have to say is a complaint? Strike 1...
The fact that your rant was already explained ON THE FRONT NEWS PAGE 2 weeks ago! Strike 2...
You know, reading is a valuable skill. I suggest you try it once in a while. 
Interesting idea about the disc distribution. All the current DriverPacks will fit on a single DVD and SAD2 would be included.
Hmmmm...
TechDud wrote:Would adding ANY infrared device drivers with, say the Chipset pack, & subsequently integrating in a Win7 disc, force Win7 to install the infrared service as well?
If so, would this not have an effect upon system latency (windows searching for IR devices)?
If any of those conditions are true, would the IR (SIR, FIR, CIR, etc) drivers better belong with the 'Miscellaneous' pack (to preserve mainstream system latency)? 
That's a good question. From my understanding, integrating the drivers with DISM will add the drivers and .inf files to the local C:\Windows\System32\DriverStore\FileRepository of the install.wim, whether the system needs them or not (think KTD). The system won't scan for devices on an IR device that doesn't exist.
To be honest, I never add drivers via DISM that aren't boot-critical. I only add DriverPack Chipset, Mass Storage & maybe LAN...that's all. The rest I install via SAD2 post install which uses DPINST.
I neglected to add these to the 11.05 release. I have them in my local copy of 11.05.1 (future release).
BTW, I found the 1.2.1 drivers at Asus.
http://support.asus.com/download.aspx?S … YbLPk492dh
Nice find. I like code65536's stuff.
msturtz wrote:Any idea where I might find the drivers to suppor this adaptor?
How about Dell?
All three will be added to "Misc" Third Party DriverPack 11.05 (in work)
They're not chipset drivers, but keyboard drivers.
This will be added to DriverPack Chipset 11.05 (in work)
Both will be added to DriverPack Chipset 11.05 (in work)
This will be added to the "Misc" 11.05 Third Party DriverPack (in work)
These should be implemented in 11.05 (in work).
Off-topic, but here you go.
Spencer7 wrote:I am trying to get Internet Explorer to slipstream, but with no luck other than just running it as an external setup after instal has finished. I would like to have it directly integrated, but I have not been able to find a way.
You need to integrate the .msu file with DISM.
Vista
x86: http://go.microsoft.com/fwlink/?LinkId=210146
x64: http://go.microsoft.com/fwlink/?LinkId=210144
Win7
x86: http://go.microsoft.com/fwlink/?LinkId=210145
x64: http://go.microsoft.com/fwlink/?LinkId=210143
More info on language packs here: http://www.msfn.org/board/topic/150416- … xplorer-9/
Glad to hear the good news. You know, these things only get better when folks try them in weird & wacky ways and report the bugs. 
And because this is open source, I'm sure some enterprising soul with better code skills than me will take this, improve it, and give back to the community.
I love this place!
Thanks for reporting the problems. Now the SAD utility is better because of it. 
rafaelr wrote:Do I delete the "DP_Chipset_wnt6-x86_1105.7z" file in "NT6\x86" before copy the "\D\" folder or not?
From the readme.txt:
Method 1 will fail if the \NT6\x86\ folder contains any .7z DriverPacks.
OK, v110505 is linked in the first post. I fixed the bug where the script was trying to write the log file to the read-only disc (causing your failure). I also coded it to extract the needed dpinst* files from the \bin\ folder.
No, there are 3 versions of dpinst.exe, each goes in it's own folder. DO NOT REMOVE THEM!
You'll have to restore the files from the SAD2-110504.7z archive to the right folders. In fact, just extract the archive to a new folder, and copy your old \d\ folder to the new extracted SAD folder. That way I'll be sure you're not tampering with the contents of the \bin\ folder also.
I tested this using method 1 & 2, on all three OS (XP, Win7 32-bit and 64-bit) without ANY failures. I'm sure it's because of something you're doing to induce the failure.
*Edit
Nevermind. I know how I can code this to be failsafe! 
Added code tags and copied bug description from other post.
Hopefully this gets resolved once Intel releases their RST 10.5 drivers.
ARrgggghhhh! OK, more testing....
*Edit
Aha! Got it. dpinst.exe wasn't being copied to your "%SYSTEMDRIVE%\D\" folder.
Fixed!
v110504 in first post.
Ah, you're using method-1. OK, now I know where to look...
@Twist,
Sorry to hear the release doesn't fix your problem. We'll have to work on that. Your posts have nothing to do with the title of THIS thread, so please create a new post with the relevant details for the bug and we'll go from there.
Thread closed.
Posts found [ 1,251 to 1,275 of 3,964 ]
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.092 seconds, 5 queries executed ]