You are not logged in. Please login or register.
Active topics Unanswered topics
Search options (Page 141 of 159)
DriverPacks.net Forum » Posts by mr_smartepants
dado023 wrote:I don't have that line in my winnt.sif.
Should i add it?
NO! It's only for Method 1 and will screw up Method 2.
You modified your winnt.sif file AFTER DPbase was run.
Proof:
Yours:
[Unattended]
UnattendMode=FullUnattended
Repartition=No
OemSkipEula=Yes
UnattendSwitch="yes"
TargetPath=\WINDOWS
DriverSigningPolicy=Ignore
OemPreinstall=Yes
Mine:
[Unattended]
UnattendMode=FullUnattended
UnattendSwitch="Yes"
OemPreinstall="Yes"
OemSkipEula="Yes"
FileSystem=*
WaitForReboot="No"
NoWaitAfterTextMode=1
NoWaitAfterGUIMode=1
Hibernation="No"
DriverSigningPolicy=Ignore
NonDriverSigningPolicy=Ignore
You removed the NonDriverSigningPolicy entry after DPbase put it there.
This modem DP is broken for my Gateway laptop now. A Motorola driver with generic HWIDs got added back in to \D\3\M\M\2\
Line 127:
%SM56_MODEM_INSTALL% = SM56_MODEM_INSTALL, PCI\VEN_8086&DEV_24C6 ; ICH4
Which matches my Agere modem exactly.
I now get an error during T-13 "Incompatible driver found for modem" or something like that.
Commenting out the above entry fixes my problem, but breaks driver signing.
Jaak wrote:Well, RVM once had an advanced option to convert to ansi, and I did that.
I then saw betas which set convert to ansi as default.
It could be that RVM in its current release does not do that by default, and I believe the advanced selection screen for this is gone.
The latest RVMI 1.5.1 had that advanced option removed.
Siginet wrote:Improvement: The Advanced Option "Convert Unicode to ANSI" feature should be obsolete now so it has been removed.
I'm not sure if the RVMI converts them automatically or not.
You could ask here: http://siginetsoftware.com/forum/showthread.php?t=299
Glad to know it worked...sort of. 
It bugs me you still get the exclamation point. I'm still willing to bet it's something else interfering with the normal setup.
Edit.
You didn't by chance declare this in your winnt.sif did you?
[Unattended]
OemPnPDriversPath="path\to\drivers"
Welcome to DriverPacks!
Yes, it's well known the Unattended wiki (uawiki.org) site has become derelict for a long time.
Your best option is to use MSFN's site.
http://unattended.msfn.org/unattended.xp/
It's current and full of info.
It's not normally required, but in your case your system is trying to use unsigned drivers. XP will kick up a stink if you don't use that text in the winnt.sif.
Sorry we can't be any more help. It's difficult when I'm not sitting in front of your notebook. 
I have a feeling that the Chipset and SMbus drivers need a restart BEFORE the graphics drivers can be loaded. It seems the PnP enumerator isn't detecting your hardware in the right order.
I have no proof, just a nagging suspicion.
Do you have Driver Signing disabled in the winnt.sif file? If not, it should be.
Have you tried KTD? I would recommend extracting the DPGA80...7z file from the OEM folder on your DVD to your desktop.
Go to your Device Manager, select the VGA adapter properties, click the "Update Driver" button.
Point to the D\G\A1 folder and let it detect. If it gives any errors at all from that point, our DP won't work for you (and I'm sorry).
If it works, then there's something else wrong and I'm at a loss.
I dual-boot between Vista64 and XP 32, but by the bios selection, not boot.ini.
I've found that better for me so if I choose to nuke a partition it doesn't screw up the bootloader for the other partition.
You are meant to install XP first, then Vista, but you can do it backwards only if you run the Vista boot repair utility last.
gvgb wrote:Can this be implemented somehow?
Open G\N1\nv4_go.inf and let me know what you read on line#2 
I've heard of your error before but can't find it for the life of me.
You can try the experimental DP here: http://dev.driverpacks.thesneaky.com/dr … nightly.7z
Did you use nLite to inject any drivers into your source? I can't think of another reason unless you have other drivers on your XP install disk somewhere.
Before you uninstall the drivers and point to D\G\A1, go to device manager, click on the device properties, click the "Driver" tab, then look at the "Driver Provider".
Does it say ATI or Microsoft?
The only other thing I can think of is the HD2400 has an HDMI port and needs the sound drivers loaded for that card. But since you say everything works after pointing to the G\A1 folder.....hmmm.
I don't know what to tell you.
Can you post your DPsFnshr.log?
Welcome to Driverpacks!
First, you're in the wrong place. We don't supply tools to modify how XP looks.
Everyone has their own preferences for looks. Personally, I use V'ISO written by Ricktendo64.
http://www.wincert.net/forum/index.php? … 47&hl=
Let us know if you need assistance with DRIVERS, it's what we're here for.
OverFlow wrote:so i was considering adding a method three 'M3' where the drivers were extracted to the OEM folder (instead of 7zipped)
(perhaps even name the folder $WinPEDriver$ instead of OEM)
They could be used without copying them to the local HDD at all (unless KTD was selected)
DPInst could be easily used with the disk and a default xml file could be generated as well.
That's actually a VERY good idea!
The DPBase could be coded in such a way to detect the OS type (which it does), then use the $WinPEDriver$ path in the correct manner for each OS type (XP, Vista, Server, etc.)
I never use M1, but I'm beginning to like the idea of your M3. That would save a lot of file-copy time. For XP, can the pathway be declared for driver detection, then re-declared back to default (if KTD isn't used) to keep from pointing to the install disk? Registry entries after-the-fact?
That sounds brilliant!
Damn fine idea Alex! Welcome to the team BTW! 
So this method should work for all our DriverPacks except MassStorage.
Good thing M$ standardized the method for us eh?
Awesome!
midiboy wrote:the link does not lead anywhere. The time has come for what ? Vista driverpacks ? :-)
That's because the link leads to the "Testing Team" area where most do not have access.
Thanks Jaak.
Yes, This is definitely a long thread to read from end to end.
It's main intent was to get the test DriverPacks out into the open for 'non-testers' to test for us, since we have a limited number of 'official' test-team members.
Because of the experimental nature of future DriverPacks, it might be better to remove the links and close this thread.
Oh, and the 174.53 drivers only officially support the 9800 series cards. We've been tinkering with them for mainstream cards and testing continues. But typically we will ONLY release DriverPacks containing WHQL drivers that have FULL support from the vendor. We never use beta drivers and only use 'cross-pollinated' drivers as an experiment.
It's unfortunate that nVidia chose to release newer drivers for ONLY the 9800 series cards. That means we won't see 'Unified' drivers for another month.
Stability is our ultimate goal.
You can try this one. I added the GART driver back in (with other tweaks). Please report back with your findings (good/bad).
DP_Graphics_A_wnt5_x86-32_80309_nightly
http://dev.driverpacks.thesneaky.com/dr … nightly.7z
MD5: B243B5659F7611649650BD31DD389A69
Size: 72.4 MB
Changed:
N1\
Changed path from N\1\ to N1
Updated to version 174.16, 02/19/2008 (experimental)
A1\
Changed path from A\1\ to A1
Updated to Catalyst 8.3, DriverVer 02/25/2008, 8.471.0.0000
Fixed uninstall fault in mobility.inf (not reported)
-- new from 80308 nightly--
- Removed WDM directory, supported by G_B\A5\WDM
- Added GART driver to AVS directory
- Added Hotfix documented here: http://support.ati.com/ics/support/default.asp?deptID=894&task=knowledge&questionID=31542
- Changed DPFinisher .ini to include exception for GART installer
dado023 wrote:where can i find a tutorial how to integrate .net frameowrk 2 and 3????
I use RogueSpear's .NET2 installer from here.
I install it during T-13 svcpack. Just drag the .exe installer to the i386\svcpack folder, then make an entry in i386\svcpack.inf (may be compressed into svcpack.in_) in the [SetupHotfixesToRun] section.
Instructions can be found on msfn here.
http://unattended.msfn.org/unattended.xp/view/web/24/
No Jaak, what he saw was the 'silent' installer for the GART driver that wasn't so 'silent' after all.
<sigh> More work for me...yay.
The good news is it worked! 
I'll try a new nightly in the next day or so.
@dado023, thanks for confirming for me. Are you prepared to test another DP for us in a day or so?
Jaak wrote:If you was not aware or it, I will say it.
kernel 2008 is pure X64. It sits on the metal, or won't. Period.
(yep, period. ??? My understanding is that 2008 will not even TRY to install if the basic IO in hardware is not compliant.)
That's good (and bad).
No legacy code means a tighter kernel and more stability (and performance).
It also means slower adoption rates since businesses will need to wait for the next hardware upgrade cycle before deployment.
OverFlow wrote:any progress on a cheat sheet "learning pains" for graphics... he asks with baited breath...
I feel pretty comfortable with doing it, or assisting with it, but... you are the "master"
I'll work on it over the weekend. The XP side is pretty straight-forward. I'm playing with the vista tool Muiz posted to see where everything goes. It's main limitation is no 'finisher' for executing exceptions.
Count me in for XP-32 bit, and Vista 32/64 bit testing.
Of course I'll be 'out of pocket' for a while.
dado023 wrote:any progress? as soon as you build new pack ill test it......
You can try this one. I added the GART driver back in (with other tweaks). Please report back with your findings (good/bad).
DP_Graphics_A_wnt5_x86-32_80309_nightly
http://dev.driverpacks.thesneaky.com/dr … nightly.7z
MD5: B243B5659F7611649650BD31DD389A69
Size: 72.4 MB
Changed:
N1\
Changed path from N\1\ to N1
Updated to version 174.16, 02/19/2008 (experimental)
A1\
Changed path from A\1\ to A1
Updated to Catalyst 8.3, DriverVer 02/25/2008, 8.471.0.0000
Fixed uninstall fault in mobility.inf (not reported)
-- new from 80308 nightly--
- Removed WDM directory, supported by G_B\A5\WDM
- Added GART driver to AVS directory
- Added Hotfix documented here: http://support.ati.com/ics/support/default.asp?deptID=894&task=knowledge&questionID=31542
- Changed DPFinisher .ini to include exception for GART installer
You could change the countdown timer from -t 60 to -t 240, that would give you 4 minutes til shutdown.
Please stick to a single thread. No multiple posts please.
There's just too many variables that can cause that.
Do your integrations in stages and test in VM after each one to find the culprit.
Posts found [ 3,501 to 3,525 of 3,963 ]
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.107 seconds, 6 queries executed ]