3,026 Reply by mr_smartepants

(45 replies, posted in Vista-Tool)

OK, so here are the screenshots of my starting point.
I'm starting with an clean MSDN ISO of Vista x64 (I have x86 also) with SP1 already pre-integrated from M$.
Contents of ISO extracted to \_VISTADVD\
I have key for Ultimate edition, so I selected image '4' per the readme.txt.
I'm also integrating the contents of VistaSP1x64_WinUpdate_Pack_v901.7z (decompressed to \Updates\)
Contents of \Bin\DRIVERS.XML

<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
    <settings pass="offlineServicing">
        <component name="Microsoft-Windows-PnpCustomizationsNonWinPE" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <DriverPaths>
                <PathAndCredentials wcm:action="add" wcm:keyValue="1">
                    <Path>C:\VistaTest\Drivers</Path>
                </PathAndCredentials>
            </DriverPaths>
        </component>
        <component name="Microsoft-Windows-PnpCustomizationsNonWinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <DriverPaths>
                <PathAndCredentials wcm:action="add" wcm:keyValue="1">
                    <Path>C:\VistaTest\Drivers</Path>
                </PathAndCredentials>
            </DriverPaths>
        </component>
    </settings>
    <cpi:offlineImage cpi:source="wim:i:/vistaaio/distribucion/sources/install.wim#Windows Vista BUSINESS (64bit)" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>

Here's the folder layout.
http://i40.tinypic.com/35jmsft.jpg
http://i42.tinypic.com/nv16oh.jpg
http://i41.tinypic.com/wtg492.jpg
And the Vista-Tool itself.
http://i41.tinypic.com/mhc6qx.jpg
It's in progress now.
*Edit,
I forgot to mention that I'm running Vista-tool as admin (right-click, run-as Administrator).

Go to forum: Vista-Tool

3,027 Reply by mr_smartepants

(45 replies, posted in Vista-Tool)

Sorry muiz, I had a really bad day yesterday and I took it out on you.  My apologies.

I'll create a fresh source and integrate only the updatepack and a few drivers.  I had selected image '4' for Ultimate.
I'll try again, and this time I'll take screenshots.

Go to forum: Vista-Tool

3,028 Reply by mr_smartepants

(4 replies, posted in 3rd Party DriverPacks)

This is easy from your perspective.  Just download all the DriverPacks.  Extract them, then throw out the ones you don't want.
Recompress and you're done. 

Apart from MassStorage...edit at your own peril! big_smile

Go to forum: 3rd Party DriverPacks

3,029 Reply by mr_smartepants

(18 replies, posted in Other)

LOL.
I think XP support will die the day M$ switches off their activation servers. big_smile
I mean seriously, how long can they employ their trained monkeys who answer the activation phones?
Then the only versions to install properly will be OEM SLP preactivation or VLK.

Go to forum: Other

3,030 Reply by mr_smartepants

(45 replies, posted in Vista-Tool)

Well, I'll agree that the Vista-Tool needs a lot of work.  Maybe it's a limitation of WAIK since this tool is just a front-end for WAIK.  I've tried three integrations of Vista64 and all three times I've had to scrap the source and try over.  Vista-tool corrupts my install.wim.  And it takes forever!
I can't even get the tool to build an ISO!  Just telling people "works for me" doesn't help anyone.
Sorry Muiz/shahed, but I think I'll stick with vlite for the time being.  At least it works partially.
Sorry for venting my frustrations, but I've just wasted two days on this that I won't get back.

Go to forum: Vista-Tool

3,031 Reply by mr_smartepants

(9 replies, posted in DriverPack Chipset)

XP x64 and nlite?  Not a good combination.  Especially with ATI drivers (nightmare).
My suggestion is DO NOT integrate ATI drivers with nlite.  Just load them after the desktop loads.

Go to forum: DriverPack Chipset

3,032 Reply by mr_smartepants

(1 replies, posted in Hardware)

Good luck.  I always advise people to avoid Toshiba for just this reason.
Instead of a hardware problem, it sounds like the graphics drivers got corrupted.  You can try booting into safe-mode, then uninstalling the graphics drivers.  Then restart and try to install fresh drivers.
Unless of course you already reinstalled XP, then you really are screwed.

Click and read the link in my signature "read before you post" before you ask any more questions.
And welcome to DriverPacks!

Go to forum: Hardware

3,033 Reply by mr_smartepants

(9 replies, posted in Hardware)

twipley wrote:

i've tested back removing the /sa switch (using graphics 'a' only this time)

Well, that would be a problem in itself considering your HWID is not supported in DriverPack Graphics A. wink  It's only supported in DriverPack Graphics C.

Jeff, can it really be that simple? o_o

Go to forum: Hardware

3,034 Reply by mr_smartepants

(4 replies, posted in Other)

"A watched pot never boils" smile

Go to forum: Other

3,035 Reply by mr_smartepants

(15 replies, posted in News)

I plan on devoting more time to the Vista DriverPacks.  I see the need for XP to dwindle in the future (not disappear).  However, I see Vista as the XP/ME version and is just a colorful clownsuit for garbage.  Win7 on the other hand is growing on me fast.  Even in Beta status it is much more robust and stable than Vista is.  Since Win7 uses the same driver model as Vista, I may as well get my feet wet. smile

One of our priorities with the Vista DriverPacks is the need for a DriverPacks Finisher, just like we enjoy with the main DriverPacks.

Go to forum: News

3,036 Reply by mr_smartepants

(9 replies, posted in Hardware)

Well, both your IBMs have the same HWID, although it's supported by DriverPack Graphics C\D\G\A5\mobility.inf (unsigned).  Since it's unsigned, that's probably why you're seeing the yellow symbol, although the dpinst utility should have handled that better.

Can you edit the $source$\OEM\DP_Install_Tool.cmd file and change this line:
Start "MicroSoft Driver Pack Installer Tool Running" /wait /separate /realtime /min CMD /C DPInst.exe /c /s /sh /lm /el /sa
to
Start "MicroSoft Driver Pack Installer Tool Running" /wait /separate /realtime /min CMD /C DPInst.exe /c /s /sh /lm /el
and test again.

It shouldn't have any affect, but I've had success by using only those switches.  I'm also having intermittent issues with the current commands.

@Overflow, we went over this in the testing area. http://forum.driverpacks.net/viewtopic. … 902#p25902

Go to forum: Hardware

3,037 Reply by mr_smartepants

(7 replies, posted in Software)

big_smile LOL
Boy, am I glad we don't get those kind of support requests (very often).

Go to forum: Software

3,038 Reply by mr_smartepants

(7 replies, posted in Software)

Are you executing the DP_Install_Tool.cmd file or just the DPinst.exe?
I honestly don't understand what the problem is.  You're not explaining what it is you are doing very well.

Go to forum: Software

3,039 Reply by mr_smartepants

(9 replies, posted in DriverPack Sound)

I've got the drivers.
Let me see if I can throw something together for you.

*Edit
OK, this is a quick and dirty test dp built using the drivers linked in the first post.  All I did is convert the archive into a DriverPacks BASE compatible format.
http://driverpacks.sytes.net/driverpack … l-e6400.7z
Please test and report back.

Go to forum: DriverPack Sound

3,040 Reply by mr_smartepants

(210 replies, posted in Software)

You don't have to host this yourself.  You can use our 3rd Party DriverPacks FTP.

Go to forum: Software

3,041 Reply by mr_smartepants

(54 replies, posted in DriverPack Graphics)

On it...
*Edit,
I don't know about this one.  They dropped HWIDs for the 946 and 965 series.  So unless there's significant improvements for the remaining HWIDs, I'm inclined to leave \I1\ intact with 12/12/2008    6.14.10.5016
Otherwise, I'm just asking for more HWID overlap headaches.

*Edit 2
I just had a look through the other folders and we should be OK.  I'll just have to revert some HWIDs from \I1\ to \I3\ that were previously commented out.  I'll just uncomment them, job done! smile

Go to forum: DriverPack Graphics

3,042 Reply by mr_smartepants

(6 replies, posted in DriverPack Graphics)

Your HWID is the only one still active in DriverPack Graphics B\I6\.  All the other HWIDs are commented out so it won't conflict with other drivers. 
The Intel driver newsposter mentioned doesn't include yours...sorry.
In fact, your HWID is the only reason I keep \I6\ around in the DriverPacks.  It's not supported in any other Intel download.
If WU/MU shows a driver newer than 2005, please let me know.  I have a tool you can use to extract the newer drivers (if found).

BTW, the reason you get the "Yellow Triangle of Doom" is because I hacked up the .inf and driver signing is broken.  You wouldn't see that if you integrated these DriverPacks into your source, only when you run DPinst from the desktop.

Go to forum: DriverPack Graphics

3,043 Reply by mr_smartepants

(45 replies, posted in BartPE - UBCD4Win - WinPE)

Wow, I laughed so hard I almost coughed up my left lung.  My wife had to drag me away from the screen so I could regain my composure.
I can't wait for round #2. big_smile

Go to forum: BartPE - UBCD4Win - WinPE

3,044 Reply by mr_smartepants

(36 replies, posted in Other)

OverFlow wrote:

Troll Patrol

LOL. big_smile

Go to forum: Other

3,045 Reply by mr_smartepants

(4 replies, posted in 3rd Party Vista / 7 DriverPacks)

You're right.
Care to start one?

Go to forum: 3rd Party Vista / 7 DriverPacks

3,046 Reply by mr_smartepants

(45 replies, posted in BartPE - UBCD4Win - WinPE)

FalconFour is bitter about something, that's for sure.  And he decided to take his frustration out on us.  Fine.
Someone who thinks they know how to fix/operate/repair computers is infinitely more dangerous to those systems than someone who knows nothing.  The worst security risk to any network is from within (users).

Ignorance is the absence of knowledge
The true solution to ignorance is education, not discipline.
Although, if a student steadfastly refuses to listen to the teacher, he will not learn; regardless of how great the teacher is or how many times he is hit on the wrist with a ruler.
That is beyond our control.
Pity...

Go to forum: BartPE - UBCD4Win - WinPE

3,047 Reply by mr_smartepants

(36 replies, posted in Other)

Maybe something along the lines of the banner/logos here: http://forum.driverpacks.net/viewtopic.php?id=3129
Or this:
http://forum.driverpacks.net/viewtopic. … 425#p28425
http://i41.tinypic.com/b8012c.png

Go to forum: Other

3,048 Reply by mr_smartepants

(36 replies, posted in Other)

I love these things!  I'm using them everywhere.
@Helmi, can we host these?

Go to forum: Other

3,049 Reply by mr_smartepants

(36 replies, posted in Other)

Sweet!
Get yer bars here!  Get your red hot DriverPacks user bars here! big_smile

Go to forum: Other

3,050 Reply by mr_smartepants

(45 replies, posted in BartPE - UBCD4Win - WinPE)

That must be because of the BartPE plug-in you're using. 
On your BartPE installs, does the DriverPacks Finisher run during GUIRunOnce or RunOnceEx?  If so, then you can easily trigger the control panel install for ATI by adding an empty text file to your source OEM folder and rename it ATICCC.ins or ATICCP.ins.

Go to forum: BartPE - UBCD4Win - WinPE