4,276

(63 replies, posted in DriverPack Mass Storage)

re jaak

The 'Intel(R) Chipset Software Installation Utility'
    must be installed prior to installing the
    Intel(R) Matrix Storage Manager.

this is installed by our chipset pack (which is run prior to t-12)

Man you guys act like this is my first day here or somthing... wink

Is anybody going to test my idea or not... big_smile wink

4,277

(63 replies, posted in DriverPack Mass Storage)

i cheated and ran setup then went to my temp folder to see what the package contains. (Bâshrat the Sneaky is not the only sneaky one)

if you look you will find this package contains .net redistributable package.
DONT WORRY about it just accept the fact that it does... and it will install the needed componenets itself (sorry i mentioned it)

Yes my method will not install any bloat in a machine that does not require said bloat -
THAT is WHY i suggested it... duh wink.

jeff

RVM Integrator simply launches Base, there is no exchange of info between the programs.
I aplogize that this is not well documented by Me, Ryan, Wim or Siginet...

One thing you can do to improve your process is to use the /settings: switch.

Set your choices in base, then from the 'overview page' export your settings to a file, say Home.ini.
then change the location and settings for your Pro and export them to Pro.ini

then in the RVMIntegrator you can use the command line
yourpathhere\DPs_BASE.exe

and put this on the 'optional parameters' line->  /settings:Home.ini
Or                                                                  /settings:Pro.ini

In this way you can be sure what settings are being called when launched from the integrator.

It is very likely that your sharing your results will help others...

thanks for shareing and feel free to call on us anytime...

thanks for being here!

4,280

(41 replies, posted in Other)

no XP sp3 is not yet available...

Windows XP SP3 will be available to non-subscribers on 4/29 via Windows Update and Microsoft Download Center.
http://technet.microsoft.com/en-us/wind … 3a761.aspx

but it won't be long now... wink

ALWAYS include in your post
-DPs_BASE.ini (from the same directory as DPs_BASE.exe)
-DPs_BASE.log (from the same directory as DPs_BASE.exe)

IF RELEVANT, include in your post
-%SystemRoot%\DPsFnshr.log

Don't forget to MENTION the relevant DriverPack (or DriverPacks BASE) and its VERSION in the TITLE.

We will be glad to help you with any DriverPacks related issues...
However i am not conviced this is even remotely related to the DriverPacks

If i were to wager a guess I'd say clean the dust off your cooling fans / heat sinks.
Sounds like thermal failure...

4,282

(41 replies, posted in Other)

Issues should really, really be resolved

Bâshrat the Sneaky has implemented a new / alternate solution for our file downloads.

and it was really fast when i tried it... almost 800Kb

improvements were added ahead of schedual we should be working 100% (holds breath)

You should find everything in excellent working order now!

I keep thinking Jake will toss you a bone here

4,286

(63 replies, posted in DriverPack Mass Storage)

Ill make some assumtions: your doing an unattended install and you have selected RunOnceEX for starting the Finisher

This would mean that you already have an \$OEM$\cmdlines.txt file 

and that your winnt.sif contains at least these lines

[Unattended]
OemPreinstall=Yes
DriverSigningPolicy=Ignore
NonDriverSigningPolicy=Ignore

now your instructions (jeff modded)

6. Download Intel Matrix Storage Manager Driver from the Web site
     and Put it in \$OEM$\ - so you now have $OEM$\iata78_cd.exe

7. script the Install of the Intel Matrix Storage Manager Driver. To do this,
     add this line to \$OEM$\cmdlines.txt
     (all lines in this file must be in quotes except for the first line [commands] )

"iata78_cd.exe /s"

and your done.

This will install the Intel Matrix Storage Manager Driver at about T12 during PE and before the reboot.

I think it is worth noteing here that this package includes .net and therefore depends on it.
so this file should not be extracted and run with its internal Iss setup file unless .net is otherwise addressed.

Test and Report please...

no reply to the report? just silently release an update... jeesh

Just searched their site and Knowledge Base no mention of the error - base, driverpacks or autoit
and nothing comes up at all for false positives in the KB Period.

They do tout thier low false positive rate in thier advertising -
and now I can only assume that low figure it is because they don't keep track
When they find False Pos. nor when they are reported.

I am sticking to SARC...

i must be getting old wink

your right 888111 applies to 2000 sp4
921401 is for xp and 2k3 only... 

so that is not the issue ...

4,289

(63 replies, posted in DriverPack Mass Storage)

i guess you didn't read my post...

Hivesys has nothing to do with it - so it won't help - no point in reading your code...

use code tags or have your post deleted...
I am not going to follow you around and hold your hand - last warning.

yes it is possable - and it can be done in half the time you've already spent fighting with sysprep.
and i didnt suggest CD i was actually thinking RIS (check out Autoimage by RogueSpear)
WPI Windows Post Installer will automate your software installs includeing befroe and after registry entries and launching any scripts to migrate settings, in this way every machine is a master.
and who cares how long an UNATTENDED install takes? you don't have to be there...
if you need to do many machines ghost multicasting is the ticket - no question.
but why wouldn't you want the master to be as clean and up to date as possable?
sysprep leaves behind a huge mess in your files and registry.
I had a guy say well i use a registry optimizer.
I had to think to myself why start out with a huge mess to clean up on a "clean" load? [scratches head]

read this thread... http://forum.driverpacks.net/viewtopic.php?id=2436

PS i am a huge fan of ghost been useing it for more than ten years...
when i worked for the phone company we had over 3000 desktops to support...
trust me, in my 40 years of experience I have done whatever it is you are now attempting to do.
(yes 40 years - i made my first dialup connection from a dumb terminal to a mainframe in 1968)

4,291

(63 replies, posted in DriverPack Mass Storage)

please use code tags  grrrrr....

you have been given the answer
the device management has to be installed first.

"If you select AHCI for Serial ATA (SATA) in the BIOS Setup
        Utility before installing Intel Matrix Storage Manager Driver,
        your computer will not respond; it will only display a blue
        screen."

you will have to preinstall the storage manager

this is probably why nLite works... it force installs the manager.
(whether it's needed or not - bloating the install)
DriverPacks uses the finisher to install managers and control panels and the like.
So they are only installed for hardware that EXISTS in the system
(we don't install garbage you don't need) DP_Finisher runs after the PE setup reboot from the gui.

So since the driver will fail to boot if the manager is not preinstalled
and driverpacks doesn't preinstall software for devices (the Finisher runs after PE reboots the machine)
It can not succeed.

either the machine must be installed as described by adam_w
or the  Intel Matrix Storage Manager Driver must be preinstalled by whatever mechanism.
IE run from cmdlines.txt or detached program or...

The driver is broken... complain to Intel...
the device should work without its cute little control panel or the control panel should be installed by the primary device driver's inf.

I normally discourage the team from hacking INF's
(I need to see a darned good reason to break driver signing)
but sometimes an exception to this rule can / must be made.
The best solution would be to put the ball in Intels court and demand a fix.
no other controllers have this issue,  so it seems to be them?

the single link is for our mirrors...
Our host has been having issues, and assured us yesterday they were fixed...

http://forum.driverpacks.net/viewtopic.php?id=521

http://forum.driverpacks.net/viewtopic.php?id=2577

Please reply to the existing topics
try to use the search feature.... and check other recent posts before starting a new topic.
Most of the time someone else has already reported it.

I can get through intermittently - i think one of the mirrors is still up...


(welcome aboard sorry about the trouble)

Did we ever get any feedback from 'Alas'

4,294

(13 replies, posted in Hardware)

I agree that we can't see how he is calling the finisher... perhaps he has a script for that...

your log is calling you a liar...

2008-04-18 15:39:37 : <PREP> Deleted old DriverPacks.
2008-04-18 15:39:37 : <PREP> Deleting old method 2 related files.
2008-04-18 15:39:37 : <PREP> Deleted \OEM\bin\DevPath.exe.
2008-04-18 15:39:37 : <PREP> Deleted \OEM\*.ins.
2008-04-18 15:39:37 : <PREP> Deleted \OEM\bin\7-zip32.dll.
2008-04-18 15:39:37 : <PREP> Deleted \OEM\bin\DPsFnshr.7z.
2008-04-18 15:39:37 : <PREP> Deleted \OEM\bin\DPsFnshr.ini.
2008-04-18 15:39:37 : <PREP> Deleted \OEM\bin\un7zip.exe.
2008-04-18 15:39:37 : <PREP> Deleted \OEM\bin
2008-04-18 15:39:37 : <PREP> Deleted \OEM
2008-04-18 15:39:37 : <PREP> Restored \I386\winnt.sif.
2008-04-18 15:39:37 : <PREP> Restored \I386\txtsetup.sif.
2008-04-18 15:39:37 : <PREP> Restored \I386\dosnet.inf.
2008-04-18 15:40:07 : <PREP> Extracted DriverPack MassStorage to a temporary working directory.
2008-04-18 15:40:07 : <PREP> G:\DriverPacks\tmp\DPMtmp\DriverPack_MassStorage_wnt5_x86-32.ini
2008-04-18 15:40:09 : <PREP> Restored \I386\DPTI2O.SY_.
2008-04-18 15:40:09 : <PREP> Restored \I386\adpu160m.SY_.
2008-04-18 15:40:09 : <PREP> Restored \I386\aliide.SY_.
2008-04-18 15:40:09 : <PREP> Restored \I386\symmpi.SY_.
2008-04-18 15:40:09 : <PREP> Restored \I386\mraid35x.SY_.
2008-04-18 15:40:09 : <PREP> Restored \I386\dac2w2k.SY_.
2008-04-18 15:40:09 : <PREP> Restored \I386\dac960nt.SY_.
2008-04-18 15:40:09 : <PREP> Restored \I386\ultra.SY_.
2008-04-18 15:40:09 : <PREP> Restored \I386\ql12160.SY_.
2008-04-18 15:40:09 : <PREP> Deleted \I386\3wareDrv.SY_.
2008-04-18 15:40:09 : <PREP> Deleted \I386\3waregsm.SY_.
2008-04-18 15:40:09 : <PREP> Deleted \I386\aec6210.SY_.
2008-04-18 15:40:09 : <PREP> Deleted \I386\aec6260.SY_.
2008-04-18 15:40:09 : <PREP> Deleted \I386\aec6280.SY_.
2008-04-18 15:40:09 : <PREP> Deleted \I386\aec68x5.SY_.
2008-04-18 15:40:09 : <PREP> Deleted \I386\aec6880.SY_.
2008-04-18 15:40:10 : <PREP> Deleted \I386\aec6897.SY_.
2008-04-18 15:40:10 : <PREP> Deleted \I386\aec67160.SY_.
2008-04-18 15:40:10 : <PREP> Deleted \I386\aec671x.SY_.
2008-04-18 15:40:10 : <PREP> Deleted \I386\ahpt3xx.SY_.
2008-04-18 15:40:10 : <PREP> Deleted \I386\aar81xx.SY_.
2008-04-18 15:40:10 : <PREP> Deleted \I386\AACAD2.SY_.
2008-04-18 15:40:10 : <PREP> Deleted \I386\aar1210.SY_.
2008-04-18 15:40:10 : <PREP> Deleted \I386\adpu320.SY_.
2008-04-18 15:40:10 : <PREP> Deleted \I386\a320raid.SY_.
2008-04-18 15:40:10 : <PREP> Deleted \I386\cda1000.SY_.
2008-04-18 15:40:10 : <PREP> Deleted \I386\ADP3132.SY_.
2008-04-18 15:40:10 : <PREP> Deleted \I386\AACSAS02.SY_.
2008-04-18 15:40:10 : <PREP> Deleted \I386\AAC.SY_.
2008-04-18 15:40:10 : <PREP> Deleted \I386\amdbusdr.SY_.
2008-04-18 15:40:10 : <PREP> Deleted \I386\arcm_x86.SY_.
2008-04-18 15:40:10 : <PREP> Deleted \I386\atiide.SY_.
2008-04-18 15:40:10 : <PREP> Deleted \I386\ahcix86.SY_.
2008-04-18 15:40:10 : <PREP> Deleted \I386\m5228.SY_.
2008-04-18 15:40:10 : <PREP> Deleted \I386\m5281.SY_.
2008-04-18 15:40:10 : <PREP> Deleted \I386\m5287.SY_.
2008-04-18 15:40:10 : <PREP> Deleted \I386\m5288.SY_.
2008-04-18 15:40:10 : <PREP> Deleted \I386\m5289.SY_.
2008-04-18 15:40:10 : <PREP> Deleted \I386\CPQ32FS2.SY_.
2008-04-18 15:40:10 : <PREP> Deleted \I386\cpqcissm.SY_.
2008-04-18 15:40:10 : <PREP> Deleted \I386\hpcissm2.SY_.
2008-04-18 15:40:10 : <PREP> Deleted \I386\cpqarry2.SY_.
2008-04-18 15:40:10 : <PREP> Deleted \I386\cercsr6.SY_.
2008-04-18 15:40:10 : <PREP> Deleted \I386\megasas.SY_.
2008-04-18 15:40:10 : <PREP> Deleted \I386\hpt3xx.SY_.
2008-04-18 15:40:10 : <PREP> Deleted \I386\rr174xp.SY_.
2008-04-18 15:40:10 : <PREP> Deleted \I386\hpt374.SY_.
2008-04-18 15:40:10 : <PREP> Deleted \I386\hptmv.SY_.
2008-04-18 15:40:10 : <PREP> Deleted \I386\hpt366.SY_.
2008-04-18 15:40:10 : <PREP> Deleted \I386\hptmv6.SY_.
2008-04-18 15:40:11 : <PREP> Deleted \I386\rr232x.SY_.
2008-04-18 15:40:11 : <PREP> Deleted \I386\2310_00.SY_.
2008-04-18 15:40:11 : <PREP> Deleted \I386\iastor55.SY_.
2008-04-18 15:40:11 : <PREP> Deleted \I386\iastor70.SY_.
2008-04-18 15:40:11 : <PREP> Deleted \I386\iastor.SY_.
2008-04-18 15:40:11 : <PREP> Deleted \I386\raidsrc.SY_.
2008-04-18 15:40:11 : <PREP> Deleted \I386\ipsraidn.SY_.
2008-04-18 15:40:11 : <PREP> Deleted \I386\nfrdx960.SY_.
2008-04-18 15:40:11 : <PREP> Deleted \I386\aacsas.SY_.
2008-04-18 15:40:11 : <PREP> Deleted \I386\adp94xx.SY_.
2008-04-18 15:40:11 : <PREP> Deleted \I386\iteraid.SY_.
2008-04-18 15:40:11 : <PREP> Deleted \I386\jraid.SY_.
2008-04-18 15:40:11 : <PREP> Deleted \I386\MegaIDE.SY_.
2008-04-18 15:40:11 : <PREP> Deleted \I386\MegaINTL.SY_.
2008-04-18 15:40:11 : <PREP> Deleted \I386\L4symmpi.SY_.
2008-04-18 15:40:11 : <PREP> Deleted \I386\Mraid2k.SY_.
2008-04-18 15:40:11 : <PREP> Deleted \I386\mv61xx.SY_.
2008-04-18 15:40:11 : <PREP> Deleted \I386\mv614x.SY_.
2008-04-18 15:40:11 : <PREP> Deleted \I386\mvsata.SY_.
2008-04-18 15:40:11 : <PREP> Deleted \I386\nvgts5.SY_.
2008-04-18 15:40:11 : <PREP> Deleted \I386\nvrd325.SY_.
2008-04-18 15:40:11 : <PREP> Deleted \I386\nvgts6.SY_.
2008-04-18 15:40:11 : <PREP> Deleted \I386\NVRD326.SY_.
2008-04-18 15:40:11 : <PREP> Deleted \I386\nvatabus.SY_.
2008-04-18 15:40:11 : <PREP> Deleted \I386\nvraid.SY_.
2008-04-18 15:40:11 : <PREP> Deleted \I386\fst376xp.SY_.
2008-04-18 15:40:11 : <PREP> Deleted \I386\ide376xp.SY_.
2008-04-18 15:40:11 : <PREP> Deleted \I386\fasttrak.SY_.
2008-04-18 15:40:11 : <PREP> Deleted \I386\fast2xxp.SY_.
2008-04-18 15:40:11 : <PREP> Deleted \I386\s150sx8.SY_.
2008-04-18 15:40:11 : <PREP> Deleted \I386\fastsx.SY_.
2008-04-18 15:40:12 : <PREP> Deleted \I386\sptrak.SY_.
2008-04-18 15:40:12 : <PREP> Deleted \I386\ulsata.SY_.
2008-04-18 15:40:12 : <PREP> Deleted \I386\ulsata2.SY_.
2008-04-18 15:40:12 : <PREP> Deleted \I386\fttxr52P.SY_.
2008-04-18 15:40:12 : <PREP> Deleted \I386\prfsx4xp.SY_.
2008-04-18 15:40:12 : <PREP> Deleted \I386\sata4302.SY_.
2008-04-18 15:40:12 : <PREP> Deleted \I386\FTTXR5_O.SY_.
2008-04-18 15:40:12 : <PREP> Deleted \I386\ql2100.SY_.
2008-04-18 15:40:12 : <PREP> Deleted \I386\ql2200.SY_.
2008-04-18 15:40:12 : <PREP> Deleted \I386\ql2300.SY_.
2008-04-18 15:40:12 : <PREP> Deleted \I386\si3114r5.SY_.
2008-04-18 15:40:12 : <PREP> Deleted \I386\3124r5A.SY_.
2008-04-18 15:40:12 : <PREP> Deleted \I386\3124R5A2.SY_.
2008-04-18 15:40:12 : <PREP> Deleted \I386\3132R5C.SY_.
2008-04-18 15:40:12 : <PREP> Deleted \I386\3132R5C2.SY_.
2008-04-18 15:40:12 : <PREP> Deleted \I386\3132R5C3.SY_.
2008-04-18 15:40:12 : <PREP> Deleted \I386\3132R5C4.SY_.
2008-04-18 15:40:12 : <PREP> Deleted \I386\3132R5C5.SY_.
2008-04-18 15:40:12 : <PREP> Deleted \I386\pnp649r.SY_.
2008-04-18 15:40:12 : <PREP> Deleted \I386\pnp680r.SY_.
2008-04-18 15:40:12 : <PREP> Deleted \I386\3112Rx47.SY_.
2008-04-18 15:40:12 : <PREP> Deleted \I386\si3114r.SY_.
2008-04-18 15:40:12 : <PREP> Deleted \I386\si3124r.SY_.
2008-04-18 15:40:12 : <PREP> Deleted \I386\ASH1205.SY_.
2008-04-18 15:40:12 : <PREP> Deleted \I386\pnp680.SY_.
2008-04-18 15:40:12 : <PREP> Deleted \I386\si3531.SY_.
2008-04-18 15:40:12 : <PREP> Deleted \I386\SI3112.SY_.
2008-04-18 15:40:12 : <PREP> Deleted \I386\si3114.SY_.
2008-04-18 15:40:12 : <PREP> Deleted \I386\si3124.SY_.
2008-04-18 15:40:13 : <PREP> Deleted \I386\SI3132B.SY_.
2008-04-18 15:40:13 : <PREP> Deleted \I386\SI3132B2.SY_.
2008-04-18 15:40:13 : <PREP> Deleted \I386\SI3132B3.SY_.
2008-04-18 15:40:13 : <PREP> Deleted \I386\SI3132B4.SY_.
2008-04-18 15:40:13 : <PREP> Deleted \I386\SI3132B5.SY_.
2008-04-18 15:40:13 : <PREP> Deleted \I386\SISRAID.SY_.
2008-04-18 15:40:13 : <PREP> Deleted \I386\SISRAID1.SY_.
2008-04-18 15:40:13 : <PREP> Deleted \I386\SISRAID2.SY_.
2008-04-18 15:40:13 : <PREP> Deleted \I386\SISRAIDX.SY_.
2008-04-18 15:40:13 : <PREP> Deleted \I386\SISRAID4.SY_.
2008-04-18 15:40:13 : <PREP> Deleted \I386\VIAMRAID.SY_.
2008-04-18 15:40:13 : <PREP> Deleted \I386\VIAPDSK.SY_.
2008-04-18 15:40:13 : <PREP> Deleted \I386\VIDEX32.SY_.
2008-04-18 15:40:13 : <PREP> Deleted \I386\VIBUS.SY_.
2008-04-18 15:40:13 : <PREP> Deleted \I386\VMSCSI.SY_.
2008-04-18 15:40:13 : <PREP> Deleted old DriverPack MassStorage text mode drivers.
2008-04-18 15:40:13 : <PREP> Deleted \I386\presetup.cmd.
2008-04-18 15:40:14 : <PREP> Replaced original setup: method 2 was used previously.

method two was used preveiously

your log is quite clear about this....

If you want help then get your facts straight...

I can't make this more clear either... I AM LOOKING AT YOUR LOG.
there is no mistake on my part... i see the deleted mass storage files listed and a record that m2 was removed AND txtsetup and dosnet were restored...

Either this is not your log - or you can't follow directions.

Thanks for reconizing the team - they work hard!

you could easily include it in the change log / overview...

lets do that from now on...

that is why i never use bottom feeder virus scanners

use Norton or CA/McAffee and you don't have 3rd rate results

DriverPacks is written in AutoIt. Avast and AVG frequently tag any file written in autoit as a virus.

This is about as intelligent as tagging any file written in C as a virus. or any file written in VB as a virus.
Just because a program CAN be used to write malicious code doesn't mean any program written with it IS malicious code.

They fail to take the time to write thier virus scanners to READ the file to see if it contains bad code they simply mark it as bad because of the compiler it is written in. I assume they do this to save money on programmers and to make the scans complete more quickly. I would rather have thorough and accurate, than cheap and fast.

this is LAME and is why i would never use either of the above programs...
I mange thousands of desktops for dozens of comanies.
I dont have time to fool with running down false positives
and my clients don't wish to pay for services they don't need.

sometimes when you pay more for something you actually are getting a better value...

4,299

(13 replies, posted in Hardware)

you are useing CCC for ATI so .net needs to be installed before the finisher runs.

Boom... it's probably that simple 
install .net before the finisher or switch to CCP.

should be fixed now http://forum.driverpacks.net/viewtopic.php?id=521