3,301 Reply by OverFlow

(37 replies, posted in Universal Imaging)

I am not the sysprep guru... i think that post has good details (hint try search)

i am certain that you can make no changes or reboots
(shut down useing "turn off") once you have changed the IDE setting and made any final runonceex reg settings.
Image...

i will guess that means NO to minisetup wink

i am guessing that you do your entire setup ready to image make that change (or changes)
and then No more changes after this point. Image

(IDK if a reseal or wahtever is needed - its in that pesky post i am vaguely remembering)

PS Galapo's Offline SysPrep is probably the best way to get where you are going wink

http://home.exetel.com.au/galapo/Offlin … .9.0.4.zip

Go to forum: Universal Imaging

3,302 Reply by OverFlow

(8 replies, posted in Feedback and Support - DriverPacks Base)

Thank you...
It is always nice to be appreciated
it is equally nice to get such good detail in a first post
and then there are your excellent follow up questions.

Our latest and greatest stuff is always posted on the home page wink tongue
8.10.RCx is a Release Candidate...
Until this morning it was the first Post now it is the second wink

When you ran base you had two choices for Method.
Method two REQUIRES setup.exe and you dont use that, so it won't work... wink
(As you already know, but now you know why.)
Method One should work however, you must relocate the $OEM$ folder to the I386 folder...
(this is documented around here in a couple of places, so i won't elaborate here.)
if you didn't adjust the location of the folder it would not have been found... wink
- your right winnt32 did not copy them, because they were lost ... lol

if you have staged your image correctly for m1 (if you use  QSC = Yes  then it wont take 90 min on subsequent runs)
you will have a systemdrive\D\ folder with the drivers in it...

Hint,
choose "custom" for the finisher when you do your install
- DON'T run the finisher (it deletes the driverpacks)
- when you sysprep add the runonce or guirunonce command for the finisher
    (that way the drivers will be available for use at the destination machine at deployment
     and then the finisher will delete them after they are used on the target)

the down side to an m1 solution it's a little bigger at 550MB, and the 4096 path limit.
the up side is speed since the drivers are ready to go (no extraction neccessary)

SAD on the other hand is only a 330mb footprint on your image (Useing M2 - which will work for you with SAD)
Extracting itself to the target machine, updateing local devices, and then removeing itself)
note: SAD doesn't need to be part of your image... you cna just call it at the time of deployment from a location of your chooseing

Go to forum: Feedback and Support - DriverPacks Base

3,303 Reply by OverFlow

(37 replies, posted in Universal Imaging)

set standard IDE in device manager before sealing... wink

ther is a reference to that in SkinLayers sticky i am pretty sure... (I know its here somewhere)

Go to forum: Universal Imaging

3,304 Topic by OverFlow

(55 replies, posted in News)

Written and provided by mr_smartepants. i just cut and pasted this for him. wink


Wow, it's been 6 months since we've released new Graphics DriverPacks. 
Has it really been that long?  Yes, it has! 
And you, our adoring public, have been itching for updated drivers.  Believe me, I feel your pain!

Well, it's been a long and dusty road to get from there to here today!  We've had problems (our testers know exactly what I'm talking about) with all the nightly builds between version 8.04 and this new and improved 8.10. 
First we had the ATI Catalyst drivers nailed down and bug-free during June and July, but Nvidia couldn't put together a decent set of drivers to save their lives.
Then ATI released the ultra-buggy 8.8 Catalyst, and Nvidia went WHQL with their beta!  (What were they thinking?)
Finally, ATI & Nvidia pulled their collective thumbs out of their...uh...receptacles, and released relatively bug-free drivers!

So, what's new with this DriverPack?  Well for starters, it's EN-US language ONLY (by popular demand) to keep the download size small.  Whoa, calm down!  I didn't forget about our international clients! 
Oh I certainly did NOT. smile
Full Language support for the ATI/Nvidia drivers...and...wait for it...ATI Catalyst Control Center localization (credits to Debugger for the idea)!  This super language support is added with a 3rd Party Driverpack for those people who want to add that functionality.
Also, as a bonus, Nvidia PhysX is added via another separate 3rd Party DriverPack.
This set of DriverPacks is fully prepared for the new and improved DriverPacks BASE 8.10 due to be released very soon (once final testing and languages are added).  But is also backwards compatible with the older version of DriverPacks BASE.

Instructions for this new triple-pack:
Place DP_Graphics_A_wnt5_x86-32_8103.7z in the \DPs_BASE\DriverPacks\ folder as normal.
Place both DP_Graphics_A_Languages_wnt5_x86-32_810.7z and/or DP_Graphics_A_PhysX_wnt5_x86-32_810.7z in the \DPs_BASE\3rd party DriverPacks\ folder with your other 3rd Party DriverPacks.
Integrate as normal.
Enjoy! smile
Big thanks go out to the entire testing team (in alphabetical order): Big Brit, Debugger, Fragbert, Helmi, hilander999, Jaak, maxximum, Overflow, RogueSpear, SamLab, Sm0k3r, and many many others.  You guys rock!

In order to utilize Catalyst Control Center, the system must have Microsoft .NET Framework version 2.0 installed in the system.
Please note that error messages will occur on your system if .NET is NOT installed BEFORE Catalyst Control Center.  If you decide not to install .NET, DO NOT install Catalyst Control Center.


DP_Graphics_A_wnt5_x86-32_8103
Download through the tracker
MD5: A099A8C9BACA740B5A9D54ADF3989F1B
Size: 56.3 MB

Changed:
  Added BartPE code to .ini per Overflow request (fixed tags so unique now)
A1\
  Updated to Catalyst 8.9, DriverVer 08/20/2008, 8.530.0.0000
  Removed old WDM directory, supported by DriverPack Graphics C \A5\WDM
  Added AVIVO codecs installer (currently enforced when ATI card present)
  Heavily-pruned mobility.inf (commented-out dup'd older HWIDs.)
  Added mega-language options to ATICCC (when DP_Graphics_A_Languages_wnt5_x86-32_810.7z is added to 3rd Party DriverPacks)
N1\
  Updated to version 178.13 09/17/2008, 6.14.11.7813 (WHQL)
  Pruned inf files;
  Added "nvidia.ins" registry entries install method for new DPs_BASE 8.10
  Changed DriverPacks Finisher .ini to include exception to install PhysX v8.09.04 (when DP_Graphics_A_PhysX_wnt5_x86-32_810.7z is added to 3rd Party DriverPacks)

Removed:
A1\
  HDMI Audio folder (duplicated in DriverPack Sound A R3\)



3rd Party DriverPacks addons for Graphics_A


DP_Graphics_A_Languages_wnt5_x86-32_810
MD5: 5970F7FA15E545B0463E973B4339CC31
Size: 39.2 MB

Added every language and locale that ATI supports when used in conjunction with DriverPack Graphics A 8.10.1
Place DriverPacks in \DPs_BASE\3rd party DriverPacks\ directory


DP_Graphics_A_PhysX_wnt5_x86-32_810
MD5: 9C3419B49593FFCD869D136B2434455F
Size: 46.7 MB

Installs PhysX v8.09.04 on supported hardware when used in conjunction with DriverPack Graphics A 8.10.1
Place DriverPacks in \DPs_BASE\3rd party DriverPacks\ directory



New changes are in place for DriverPack Graphics B & C. 
Both have been reorganized into more logical arrangements. 

The new lineup will be:
DriverPack Graphics A : Mainstream ATI/Nvidia desktop & notebook.  (A for Active)
DriverPack Graphics B : Business-level ATI/Nvidia/Matrox for workstations; ATI FireGL, Intel, Nvidia Quadro, Matrox. (B for Business)
DriverPack Graphics C : Catch-all for the bulk of other drivers such as SIS/Via/ etc. (C for Catch-all)

DP_Graphics_B_wnt5_x86-32_810
MD5: 49BB90580DFEFFD1B1E4F4DE45728C1C
Size: 96.4 MB

Changed:
A6\
  Deleted, duplicated by AE\
  (INF files merged to new folder, may have broke driver-signing):
 
AB\
  Deleted, duplicated by AE\
  (INF files merged to new folder, may have broke driver-signing):
 
AC\
  Supports new FireMV PCI-Express 2x00 series
  Updated to DriverVer 07/22/2008, 8.521.0.0000
 
AE\
  Unified driver supports new FireGL V series (see below)
  Updated to DriverVer 09/05/2008, 8.523.1.1000 
 
I1\
  Updated to DriverVer 09/11/2008,6.14.10.4990 (14.36.3.4990)

I2\
  No change to DriverVer 02/07/2006,6.14.10.4497 (14.19.50)
   
I3\
  Deleted, duplicated by \I2
 
I4\
  No change to DriverVer 06/21/2005,6.14.10.4342 (14.10.3)

I5\
  No change to DriverVer 08/20/2004,6.14.10.3889 (14.7)

I6\
  No change to DriverVer 07/23/2002,6.13.01.3196 (6.7)
     
I7\
  Commented out duplicate HWIDs from I2\ (14.17)
  (original .inf renamed ialmnt5.inf.bak)
 
M1\
  Updated to version 2,06.02.004 SE U WHQL, Jun. 25, 2008

M2\
  Deleted, duplicated by \M1

N3\
  Updated to DriverVer 05/26/2008, 6.14.11.6996
  Commented out duplicate HWIDs with \N1
   
N4\
  Deleted, duplicated by N3\
  (INF files merged to new folder, may have broke driver-signing):
 
ND\
  Updated to DriverVer 02/22/2008, 6.14.11.7431
  Supports Dell Latitude - D630, D830; Precision - M4300 HWIDs for nVidia Quadro FX 360M, Quadro NVS 135M, Quadro NVS 140M


AE\ is a unified driver.
The Display Driver is designed to support the following ATI workstation product family:
ATI FireGLâ„¢ T2-128
ATI FireGLâ„¢ V3100
ATI FireGLâ„¢ V3200
ATI FireGLâ„¢ V3300
ATI FireGLâ„¢ V5000
ATI FireGLâ„¢ V5100
ATI FireGLâ„¢ V5200
ATI FireGLâ„¢ V5600
ATI FireGLâ„¢ V7100
ATI FireGLâ„¢ V7200
ATI FireGLâ„¢ V7300
ATI FireGLâ„¢ V7350
ATI FireGLâ„¢ V7600
ATI FireGLâ„¢ V7700
ATI FireGLâ„¢ V8600
ATI FireGLâ„¢ V8650
ATI FireGLâ„¢ X1-128
ATI FireGLâ„¢ X1-256p
ATI FireGLâ„¢ X2-256
ATI FireGLâ„¢ X3
ATI FireGLâ„¢ X3-256
ATI FireGLâ„¢ Z1-128



DP_Graphics_C_wnt5_x86-32_8101
MD5: CCA9F1DBF185B17C580DA4FB997EEFD3
Size: 50.2 MB

Changelog:

3a thru 3d\
  Marked for archive (no longer updated by vendor)
A2\
  No change to DriverVer 02/28/2002, 5.10.2600.6010
A3\
  No change to DriverVer 09/26/2001, 6.13.3279.0
A4\
  No change to DriverVer 06/16/2002, 6.13.10.5796
A5\
  No change to DriverVer 05/03/2006, 8.252.0.0
A6\
  Deleted, duplicated by AE\
A7\
  No change to DriverVer 05/11/2001,5.12.2195.1118
  Fixed missing language files (not reported).
A8\
  No change to DriverVer 04/30/2002,6.12.10.2088
  Fixed missing language files (not reported).
A9\
  Deleted, duplicated by AA\
AA\
  No change to DriverVer 02/15/2005, 6.14.10.6497
AD\
  Added OEM Dell ATI Rage Pro DriverVer = 01/14/2000, 5.0.0.86 (by OverFlow)
  - HWID support for PCI\VEN_1002&DEV_5046&SUBSYS_040xxxxx (May be replaced by A3 with .inf mods) 
AS1\
  Deleted, duplicated by AS2\ 
AS2\
  Marked for archive (no longer updated by vendor)
P\
  No change to DriverVer 10/23/2001, 1.0.9.31
S3a thru S3h\
  Marked for archive (no longer updated by vendor)
Sa\
  Updated to DriverVer 06/27/2008,6.14.10.3850 (v3.85)
Sb\
  Updated to DriverVer 03/09/2006,6.14.10.3730 (v3.73)
Sc\
  No change to DriverVer 02/19/2004,6.14.10.3570
  Dup'd HWIDs commented out.
Sd\
  Updated to DriverVer 02/22/2002,6.13.10.1150 (v1.15)
Se\
  Updated to DriverVer 12/11/2002,6.13.10.2090 (v2.09)
T\
  Deleted, duplicated by \T1 (newer)     
T1\
  Updated to DriverVer 02/14/2008,6.10.10.4101   
T2\
  Updated to DriverVer 04/24/2008,6.10.10.4103
TR\
  No change to DriverVer 08/28/2001,5.01.2527.0125
V\
  No change to DriverVer 07/06/2007, 6.14.10.0099
V1\
  No change to DriverVer 12/29/2005, 6.14.10.0276
V2\
  No change to DriverVer 04/28/2007, 6.14.10.0364
V3\
  No change to DriverVer 03/09/2005, 6.14.10.0212
V4\
  No change to DriverVer 09/24/2002, 6.13.10.3137
V5\
  No change to DriverVer 11/10/2006, 6.14.10.0342
V6\
  No change to DriverVer 06/07/2007, 6.14.10.0367
V7\
  No change to DriverVer 03/14/2007, 6.14.10.0359
V8\
  No change to DriverVer 05/15/2007, 6.14.10.0092
V9\
  No change to DriverVer 06/14/2007, 6.14.10.0368
X\
  No change to DriverVer 02/02/2005,6.14.10.1080
x2\
  No change to DriverVer 05/26/2005,6.14.01.1130


Of course, we welcome all comments and suggestions (donations are always welcome!) smile

Go to forum: News

3,305 Reply by OverFlow

(3 replies, posted in Feedback and Support - DriverPacks Base)

download DriverPacks BASE

use the DriverPacks tutorial for directions on how to setup the packs and base program...

select SAD as your platform.

select the packs you desire and hit slipstream button.

run the DriverPacks.net\DP_Install_Tool.cmd

cant make it any easier than that... wink

(stubborn is good)

Go to forum: Feedback and Support - DriverPacks Base

3,306 Reply by OverFlow

(8 replies, posted in Feedback and Support - DriverPacks Base)

make that three ways... i just thought of another... wink let me know if you have trouble with SAD
the third method is more involved and we won't go there if not needed...

Go to forum: Feedback and Support - DriverPacks Base

3,307 Reply by OverFlow

(8 replies, posted in Feedback and Support - DriverPacks Base)

This can be done two ways with the new version of base (check our home page)

You will need a copy of base 8.10.RCx and use the DP_Install_tool.cmd script in the OEM folder
call it from runonce or guirunonce that should put you over the top...
this is the SAD or Stand alone drivers feature that is now coinstalled with the DriverPacks
or you could use the DriverPacks BASE to create a SAD folder
Either use that from a network share, or include it with the image and delete after it's used..

Your method is not currently supported - at least not directly...
IE we support setup.exe for disk method not setup32.exe...
the win32 setup will always fail for method 2 (since setup.ex_ is never called wink)

but method one will work, as long as you don't need all the packs.
M1 will only make the first 4096 charachters of the drivers paths available

hope that helps

thanks for the excellent details!... and welcome aboard

Go to forum: Feedback and Support - DriverPacks Base

3,308 Reply by OverFlow

(58 replies, posted in 3rd Party DriverPacks)

no...

as stated above... text mode drivers will not be added from a 3rd party DriverPack

Go to forum: 3rd Party DriverPacks

3,309 Reply by OverFlow

(15 replies, posted in DriverPack Chipset)

best one i can think of is a driver that is included in the most recent SP only...

we dont really need it but some poor slob who is tied to an old SP for wahtever reason just might...

Go to forum: DriverPack Chipset

3,310 Reply by OverFlow

(38 replies, posted in Software)

I dont like MS code much myself
we are 180 degrees out of sync
I like smaller faster leaner meaner they like bloat for the sake of bloat.

although i saw some very promiseing behavior and even some legitimate quality checks with the release of sp3 -
i maintain hope that that ship may still find its way someday...

in a car there are two ways to make it faster add horsepower or lighten the car - this is no different wink

Go to forum: Software

3,311 Reply by OverFlow

(7 replies, posted in Other)

it's a real groaner...  wink
sorry...

but you made me think of it wink big_smile

It's easy to tell the good farmer, He is the one that is Out-Standing in his field !

ROFL

Go to forum: Other

3,312 Reply by OverFlow

(7 replies, posted in Other)

Looks like a cool project...
Please keep us in the loop

I am always excited to see people shareing ideas and contributing to the greater good of our community.

I have granted you access to the testing team area
so you can stay current with changes that may (or not) at some point affect your program.

I offer you my respect, and Welcome you to the testing team. 

PS i think jclas was correct don't get feature happy - the KISS method is always the best one.

Jeff

Riddle: Do you know how you can tell if a farmer is good one, even from a distance?

Go to forum: Other

3,313 Reply by OverFlow

(15 replies, posted in DriverPack Chipset)

mass storage would be tougher as i would have to code base to regonize the archive mass pack wink

Go to forum: DriverPack Chipset

3,314 Reply by OverFlow

(7 replies, posted in Other)

We are honored to be asked to help you...

thank you...

IIRC Pyron and / or iLE wrote the original Fake setup that we use...
So technicaly it's not really ours wink
We just enjoy the privilege of borrowing it with their permission smile

I personaly don't see any reason why not
It is a basic wrapper program that could have been written by anyone with some time on their hands.

Without checking with Bâshrat the Sneaky or the original authors...     I think it's OK

Please be sure to credit Pyron, iLE, and DriverPacks (Like it is the presetup.cmd now)
and there should be no issues that i can forsee.

Thanks So Much for Asking.

Your integrity is showing wink


EDiT>>>

I marked the [REQ] as approved since I am assumeing no one will object to such a polite request...

Go to forum: Other

3,315 Reply by OverFlow

(117 replies, posted in DriverPack Mass Storage)

it's not luck
           he's a Veteran....  wink

Go to forum: DriverPack Mass Storage

3,316 Reply by OverFlow

(15 replies, posted in Other)

Don't ever stop thinking outside the box!

It's an excellent quality, nurture it sir!

Go to forum: Other

3,317 Reply by OverFlow

(4 replies, posted in Feedback and Support - DriverPacks Base)

back atcha on the crystal ball thing - no info to go on in your post ...


RE: Ive followed the 'READ BEFORE YOU ASK!' post.

NOT EVEN CLOSE NOT ONE ITEM from read before your post exists in your post...
you failed to mention the DriverPacks BASE version (listed in read before you post as "to be included in the title")
(and this one is CRITICAL to giving any answer to any question at all PERIOD.
you failed to mention which packs... (listed too)
you failed to mention what you did ()
IE rvm nlite autoimage.

so i am supposed to be happy about guessing what you did different than a few hundred thousand others?
and the only clue is you added SP3 (since a half a millon other people have no issue i can only assume you added it wrong.)
And I see no reason you could not come up with that answer on your own... (note: ID ten T error)


So you put a really lame post up and now i am the jerk...
THE ONLY info provided was "I added sp3 to my image" which is a big no no...

Perhaps you should look at it from the other side... or you are going to have a very short stay here i think...
I have zero patience for BS when i am getting paid nothing, take heed.

you want a good answer ask a good question... wink and follow the VERY simple guidelines provided.

It was not meant to be harsh, it Was meant to be just as vague and thoughtless as your question
And i am sure i spent way more time on my initial reply than you did on your initial post... wink


Only inconsiderate people get arrogant answers.
Perhaps they will learn somthing about themselfs if/when they realize it...
Because a truely arrogant person would not respond at all.
The fact that an answer was presented at all proves the opposite is true.

lets review your performance...

IE all that stuff in read before you post - that doesn't apply to me, thats for everyone else. (and you called me arrogant...[insert mirror here])

This is totaly inconsiderate of the position that we are put in to provide support.
(you don't care if it is harder for us?) never even occured to them to make it easy to help them
or worse (hey i'm not paying for their time, who cares how long they spend on it...) realized it and didn't care.

this ain't the forum for noobs never has been, and will not be going forward.
this is our house and you are a guest... act like it.


Good details lead to good answers - the ball is in your court sir...

Try again and this time WITH the details of what you did 1 2 3... and the missing info from Read BEFORE you post.
and i will see if i can be polite wink

its not arrogance its annoyance
- don't annoy me...
this is a simple task
at least it is for considerate people with good manners

Go to forum: Feedback and Support - DriverPacks Base

3,318 Reply by OverFlow

(15 replies, posted in DriverPack Chipset)

you might make an archive pack out of them too... 3rd party DriverPack for legacy OS versions (out of date SP wise)

Go to forum: DriverPack Chipset

3,319 Reply by OverFlow

(4 replies, posted in Feedback and Support - DriverPacks Base)

because you are the only one who failed to follow the directions

you cant slipstream sp3 into your disk after DriverPacks... since DriverPacks has to be the last step in your process.

THAT is POSTED EVERYWHERE   - DriverPacks Last - if not then it wont work

so now your source is corrupted and you will need to start over... wink

sp3 first DriverPacks last !

Go to forum: Feedback and Support - DriverPacks Base

3,320 Reply by OverFlow

(38 replies, posted in Software)

agreed...

have you looked at the spotlight tool ?

Go to forum: Software

3,321 Reply by OverFlow

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

Please tell us more...

use Read before you post in my signature as a reference for providing us good details.

the more you tell the better we can help.

Where did you get this - is a Joke - it means you are useing a test pack wink or what we call a nightly, AKA a beta pack


moved to BartPE forum...

Go to forum: BartPE - UBCD4Win - WinPE

3,322 Reply by OverFlow

(353 replies, posted in Software)

I have a confirmed bug report for the finisher so give me a minute ...
i still think i can make this play useing the existing bartpe code without much hassle...

Go to forum: Software

3,323 Reply by OverFlow

(38 replies, posted in Software)

That is awsome... you are the man... !

Yes there is one that is floating around... it is cleverly disguised as a SysPrep tool though

Sorry about that!

it's here kickarse's FindHWIDS - The INF searching HWID exporter

and, well... um... it     er,    well...  it's good wink

Go to forum: Software

3,324 Reply by OverFlow

(10 replies, posted in DriverPack Chipset)

more often than not if you change something driver name or INF info whatever it will break

we have gotten away with some small tweaks with certain drivers but it is rare...

Perhaps if the INF was not tweaked (leave the reg entries) it will still be signed wink

I think you could allow this without signing since it is unlikely that we will have a conflicting driver for this... wink
please for teh sake of everyones sanity make a backup of the original INF let's say something like *.ORG

Go to forum: DriverPack Chipset

3,325 Reply by OverFlow

(10 replies, posted in DriverPack Chipset)

your SystemRoot\setupapi.log will tell you if signing got broken

(use the 'find' feature since this file will be huge wink)

Go to forum: DriverPack Chipset