Welcome aboard,  Glad to be able to help big_smile

the source (in this case your dvd) is passed to setup, mru, possably the registry.

the only way to test accurately is to run the install from the network. or to copy a preimage then remove the dvd and reboot.

4,353

(15 replies, posted in Other)

there are a couple of users who drop-in here that do RIS off a Linux server. that would be difficult.
I do silly stuff like that sometimes... for fun... my friends often ask why? just to hear the answer: the one they know is coming

Because I can... wink ...

I think you should not let your first attempt at 2003 intimidate you.
Think of it as XP with PMS you just have to proceed carefully

i have loaded 2003 server countless times.
Yet i find it still takes me a few runs at a new setup before i am happy with it.

i will usually get it all up and running with drivers and updates and then ghost it right before i promote it to a domain controller.
that saves a couple of hours if you choose poorly when setting it up. jsut restore the image from right before you promoted it.
and you get a clean slate in no time. the server side setup of ris is not difficult. the biggest issue with ris is making sure the lan drivers get installed (unless you copy everything to the local drive first)

give 2003 a second chance - besides now you have found out there are support comunities out there. wink

If you have a driver that does not install useing the dpinst method then get the HWID's (tool in my sig) and
Start a post in the correct subforum start teh title with [REQ] 
post the HWIDS and the DriverPack version(s) for that device.
if you know where the working driver can be found (OEM) then a link is considered polite.

We can't stand missing drivers...

jeff

we cross posted check my last please

PSS i have seen some good scripts for sysprep and hal on this forum somewhere... i forgot who and where.

i think i now how you can win this useing existing tools

DPinst.exe is a MS tool that will compare your local device managers device drivers (or lack there of)
to a folder that may contain subfolders of drivers and atuomaticaly update them if newer drivers exist in those folders.
This works in much the same manner as if you selected search removable media, (with a recursive folder search)
it is not very difficult to edit the XML file that then runs dpinst.exe in unnattended mode (i have a link to a working sample below)
this would be great if you plugged in a card to a machine and had no clue what is was.
Run dpinst with driverpacks and device manager will tell you. wink

We have a new freind here at DriverPacks, WarmSnow he has a front end / GUI for MS's DPinst.exe
It works well useing the driverpacks as a source for those driver folders wink 
the Idea is to update blackboxes with the drivers from our packs.
Unattended and not just at the time of install... any time. 
http://forum.driverpacks.net/viewtopic. … 148#p19148
be sure to read the First post and get the file from the Last post.

I have also created a simple script that does the same thing (no gui) inspired by WSnow
http://forum.driverpacks.net/viewtopic.php?id=2264

first post is how to create a source and second is how to autoinstall drivers on a machine.

Perhaps you should mention it on the other forums.
you can (if you want to) run DPsFnshr.exe at any time after the install.

IE don't put it in in your scripts anywhere at all.
Once everything is all done just double click on it in windows explorer. big_smile

in this way one could prove that their script was the issue and not the finisher itself...

lets see your base.ini and log these will show if 888111 is installed.
if I386\svcpack\KB888111.cat exists in your source it might be added, but not properly added
if it does not exist then it is definitely not added.


if your hda is failing then 888111 is not slipstreamed / installed.
I suspect this is a sysprep issue it's definately not a base / DriverPacks issue.
(ps SysPrep is not supported by DriverPacks - but someone may post a solution.)
(pss this should be in the installation platforms forum)

xp SP3 may also eliminate your problem.

on the machine that has this problem what happens if you manually install 888111 and then manually reinstall the sound drivers?

IMHO sysprep is the worst possible way to deploy windows.

It sounds like you need to start clean. Perhaps you will consider an easier and more flexible method.

local installs
RVM
Nlite
DriverPacks
WPI

remote installs
above list plus RogueSpears AutoImage. (RIS)

in this way every install is a master and it takes a fraction of the time to create and maintain and
any issues or problems are not copied to new systems and no HAL problems.

IE your image had adobe 6 installed then you upgraded to 7 then 8 then 8.1
all of the garbage for 6, 7 and 8 still exists in the syspreped registry and the mess grows with each new pass.
after a few upgrades your registry is in the same condition as a two year old machine. (in need of repair or reinstall)

by using an UWXP install each machine is a Clean install (a new master) and has no left over / extraneous garbage in the registry.
a bloated registry is a very bad thing and it is guaranteed with sysprep. not to mention hal issues which don't exist with a UWXP install.

If you are simultaneously deploying to multiple identical machines use ghost,
it automatically handles the SID and sysprep is not even needed
and in multi-cast mode the image is sent simultaneously to all machines
(instead of a 1 to 1 copy it is a 1 to many copy drasticly reducing time and network load)
i have used this technique to copy as many as 100 machines at the same time.
And 100 takes no longer than one since it is a true multi-cast.


please see this other thread.. http://forum.driverpacks.net/viewtopic.php?id=2436

no...

replace DPM8021.7z
with DPM8042.7z

obviously the name is not hard coded. read the script above.
%SystemDrive%\bin\un7zip.exe %SystemDrive%\DP*.7z %SystemDrive%\

"DP*.7z" is what gets copied / extracted.

mass textmode must be added with base

all packs except mass can be substituted but you must be careful to rename them to thier 8.3 names correctly.

unattend.txt is winnt.sif the content and funtionality are identical.
we simply need to rename it for a network install.
leave it to microsoft to make it harder than it needs to be.

please do a search for kb888111 thanks...

no problem we understand that many people do not speak english as their primary language.

Just provide as much detail and information as you can.

4,364

(74 replies, posted in Vista-Tool)

not much help if your testing to see if the drivers worked wink
or in my case, you wanted to play HALO...

4,365

(1 replies, posted in DriverPack Mass Storage)

multiple versions includeing DP_MassStorage_wnt5_x86-32_8021

ms_1_exc_replaceIfOS="wxp,w2k3"

needs to be   ms_1_exc_replaceIfOS="w2k,wxp,w2k3"

Because this driver Does exist natively in windows 2000 the OEM driver will get deleted if it is not tagged as "replace"
explained:

Base checks to see if it was previously run.
if it discovers that this is not the first time base was run it removes the previous install.
base checks the entire mass ini for file names.
all names that are not tagged as "replace" get deleted. PERIOD.

IE if an OEM driver.sy_ was marked as Replace and Skip
skip = then it will not get backed up to .org and it will not be replaced / updated.
replace = it will not get deleted if base is rerun on a source (it's a native windows file)
and if there is no "driver.org" file then it also won't get restored


So if a driver.sy? name exists natively in windows\I386 it is by definition a "replacement"
it may also be marked as skip
Don't use the windows 2000 disable exception on a replacement driver. (use skip) 

[L2]
ms_count=1
ms_1_deviceName="LSI Logic MegaRAID Enterprise 1200 RAID Controller"
ms_1_tag="mraid35x"
ms_1_sysFile="Mraid35x.sys"
ms_1_hwids="PCI\VEN_101E&DEV_9010,PCI\VEN_101E&DEV_9060,PCI\VEN_8086&DEV_1960&SUBSYS_0438101E,PCI\VEN_8086&DEV_1960&SUBSYS_0466101E,PCI\VEN_8086&DEV_1960&SUBSYS_0467101E,PCI\VEN_8086&DEV_1960&SUBSYS_0471101E,PCI\VEN_101E&DEV_1960&SUBSYS_0471101E,PCI\VEN_8086&DEV_1960&SUBSYS_0490101E,PCI\VEN_8086&DEV_1960&SUBSYS_0493101E,PCI\VEN_101E&DEV_1960&SUBSYS_0493101E,PCI\VEN_1000&DEV_0407&SUBSYS_05301000,PCI\VEN_1000&DEV_0408&SUBSYS_00011000,PCI\VEN_1000&DEV_0408&SUBSYS_00021000,PCI\VEN_8086&DEV_1960&SUBSYS_0762101E,PCI\VEN_8086&DEV_1960&SUBSYS_0475101E,PCI\VEN_101E&DEV_1960&SUBSYS_0475101E,PCI\VEN_1011&DEV_0046&SUBSYS_0489101E,PCI\VEN_8086&DEV_B555&SUBSYS_0489101E,PCI\VEN_101E&DEV_1960&SUBSYS_0494101E,PCI\VEN_8086&DEV_1960&SUBSYS_0494101E,PCI\VEN_101E&DEV_1960&SUBSYS_0503101E,PCI\VEN_8086&DEV_1960&SUBSYS_0503101E,PCI\VEN_101E&DEV_1960&SUBSYS_0511101E,PCI\VEN_1000&DEV_1960&SUBSYS_A5201000,PCI\VEN_1000&DEV_1960&SUBSYS_05181000,PCI\VEN_1000&DEV_1960&SUBSYS_05201000,PCI\VEN_1000&DEV_0407&SUBSYS_05311000,PCI\VEN_1000&DEV_0407&SUBSYS_05321000,PCI\VEN_101E&DEV_1960&SUBSYS_0522101E,PCI\VEN_1000&DEV_1960&SUBSYS_05221000,PCI\VEN_1000&DEV_1960&SUBSYS_05231000,PCI\VEN_1000&DEV_1960&SUBSYS_45231000,PCI\VEN_8086&DEV_1960&SUBSYS_10C6103C,PCI\VEN_8086&DEV_1960&SUBSYS_10C7103C,PCI\VEN_8086&DEV_1960&SUBSYS_10CC103C,PCI\VEN_8086&DEV_1960&SUBSYS_10CD103C,PCI\VEN_101E&DEV_1960&SUBSYS_60E7103C,PCI\VEN_101E&DEV_1960&SUBSYS_60E8103C,PCI\VEN_8086&DEV_1960&SUBSYS_0431101E"
ms_1_isBusExtender=false
ms_1_exc_replaceIfOS="w2k,wxp,w2k3"
ms_1_exc_skipIfOS="w2k"

Setting MS count to 0 will disable adding a driver
and prevent the removal the drivers .sys file during the prep stage if it was previously streamed by base.

I hope this helps with the mass mystery

It may help someone. thanks

This will probably not make it into the tutorial. the DriverPacks are aimed at the technically savvy user.
It is assumed our users are already aware of the signifigance of the basic settings.
I frequently refer noobs to read up and come back... (you provided good details and were polite so...)
It is our position that you should at least understand the contents of this guide as a prerequisite for getting the best support from us.

Glad your here and that we could help...

jeff

I think that it is important to note that KTD; All, paths, and patterns will be unaffected
it only effects KTD if useing custom "pack" selection and when not all packs are selected
for the most part only sound and graphics will have issues (the split packs)
or other packs if KTD is NOT set to ALL and if folders are shortned to \D\*.*

again the workaround is to specify your KTD manually useing the "paths" method

4,368

(41 replies, posted in Other)

yes i am updating the KTD folders as i go in RC3.
as we continue to streamline the folder structures there may be some anomalies
If using KTD when using the "packs" selection method. (unless you select all packs)
if you use KTD "all", "patterns" or "paths" then you should not be affected.   

I am waiting for the release of XP sp3 because that is the primary feature of RC3...
if you must use KTD in the interim just use the paths method for the packs you select.

jeff

4,369

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

if the process stops it should create an event in the log (it might not be flagged as an error) take a look based on teh time stamps for events that coincide time wise.

4,370

(3 replies, posted in Feature Requests)

as you point out driverguide already provides that service.

and yes if you look into the artical i pointed to it uses a redistributable MS tool (DPINST.exe) and a default config file.

so there is no source it's just useing an existing tool and combineing it with with a good driver store

if you are asking about warmsnow's GUI you will have to ask him... although, it is just a wrapper for MS's dpinst

4,371

(3 replies, posted in Feature Requests)

we have an upgrade for that...

one is a script
http://forum.driverpacks.net/viewtopic. … 806#p17806

and one is a nice GUI
http://forum.driverpacks.net/viewtopic. … 805#p17805

It doesn't bother telling you what it is it just installs the driver...
Of course you could look in device manger... if it still mattered. wink

4,372

(10 replies, posted in Other)

he did... it is in the code tags above...

4,373

(74 replies, posted in Vista-Tool)

vista did away with the whole boot.ini / loader thing - and it made me sad...
In the end I saw no useful purpose for the new boot-loader system...
What was gained by switching from a known good system? IDK...

Dual Booting is cake   UNLESS    you do what I did...

I put a 40GB IDE HDD in my "drawer" Drive Bay and opened my bios and Specified my boot sequence so that the Drawer was Primary and the SATA drives and IDE RAID were tertiary. This has Always worked flawlessly on my GigaByte MB. 

However enter hasta la Vista... I run setup and I feed it the driver and wait for setup to load the files and reboot, and I wait gleefully for the second part of setup but instead I am sad. the boot tracks are on the SATA drive, and my system won't boot  at all  and I have to repair my sata's boot tracks.

I finally had to disconnect all the other drives in the system to load Vista on the IDE drive.
You may be thinking "well, it's kinda silly to put vista on the IDE drive when you have SATA available..."
but I don't have a spare sata removable drive that I can format ATM nor do i wish to molest my primary setup ATM. but I digress,

The point is, it doesn't work as well as it's predecessor.
   IE had I been in this situation with XP;
      I could have used notepad for the boot.ini, and fdisk /mbr for the boot-track
      and I would have been off to the races in no time at all.

In retrospect i should have just ghosted my primary sata to the drawer and repartitioned,
but hind-sight is always 20/20... ain't it?

4,374

(74 replies, posted in Vista-Tool)

the existing base code is autoit so were starting with that... i almost got RC3 nailed down.

they finaly decided to include the hotfixes they said they wern't going to... figures...

I have totaly cleaned house on the core of Base and it is ready for final testing and ready for some new features and Vista.
I now have 2.5 gig of ram so i can use my machine (and a removable HDD) for test installing on a live machine. 

i got to get back to coding now...

to make that viable with the finisher i will have to edit the base to point to the D\Wxx folders
the finisher and KTD will expect the old subfolders until i add the new folders to the list
this will be most evident for the split packs like sound and video