i've injected the drivers (LAN - Wlan - Mass Storage) into the...

WinPE 3.1 Image & main sysprep image using MDT 2010 Update 1


is this not the right way..... have i gone down the wrong path?


MDT seems to inject the drivers fine, it even makes some adjustments to some of the INFs in the driver packs because x64 info are present (it takes that information out of the inf's)

only done a lot of reading and theory stuff so far, haven't done hardly any practical testing at this point.

MDT is a lovely tool, and fully supported by MS amazingly, but i have yet to fully understand it's power.

hi, i'm a little confused when to use this and at what stage,

i have created a system (virtualbox) win7 and ready to sysprep it (ghost the image)

on my host (WAIK & supplement sp1 installed)
and put in MDT 2010 update 1

i'm now in deployworkbench (and there is out of bos drivers)


but this is where i'm lost.

where do i run the script,

can't i just put all the drivers in the deploymentworkbench, or am i completely in the wrong place?



this is the scenario that i'm aiming for.


create a universal image

Virtual Box (windows 7 starter installed)

sysprep this image,

deploy image on Desktop PC's/laptops

upgrade anytime to relevant level (if pc/laptop has key for pro, then upgrade to pro level, then use that key to activate)

of course i wish to insert drivers into the main image itself (i don't wish to utilize network shares for problems like connection issues, or network card not found problems (laptops sometimes use weird network systems))

i want the image to be self sufficient as possible and method 1 seems the best choice


i just don't know where driverpacks fits in, i tried to use winintergrator but my host is XP sp3 so it didn't work (strange as even WAIK and MDT 2010 is compatible with XP sp3 which i was amazed that MS went through that trouble kudos to MS for that)


appreciate any feedback,

thanks.

3

(36 replies, posted in Vista-Tool)

any chance someone could send beta 3 for me,

thanks,

4

(7 replies, posted in Universal Imaging)

http://www.vernalex.com/tools/spdrvscn/#instructions

very intuitive, i did email him some time back to see if he would ever update his guide with respect to new utilities such as "Offlinesysprep" and "Mysysprep", he did say he would get round to it, but clearly nothing yet.


i have personally read his guide several times in the past, very intuitive and well written,

i agree, would be nice if the original guide was updated, or perhaps a new one made,

i'm confused a little concerning what tools should be used,

Offlinesysprep
Sysprep driver scanner,
Mysysprep,

for example, if offlinesysprep is used, does that mean we don't need the other two tools listed,

and should we at anytime use driverpacks TOOLS (driverpacks themselves always get used) if Offlinesysprep is being used?

there are quite a few guides on google about this, but more often then not, they are quite unclear, out of date, or don't include the Offlinesysprep tool (which of course is a must have tool now)

you were right, thanks, it took 5 attempts of download, strangely enough though 7Zip extracted without any errors?

anyway the file exists now, just about to create a LiveXP project, thanks bigfoot, I would have never imagined it was a corrupt download, I assumed that 7Zip would always do a full CRC32 check on extraction, any mismatch would lead to an error, clearly I was mistaken. thanks again,

Doesn't DriverPacks have a built in SHA5 or MD hash (or what ever it's called) validator, given the nature of how sensitive these driver packs are....

just checked, the 2K problem still exists though, file is considered corrupt every time,
as well as many others I have tried of the internet, my gut tells me that AHCI7xx just isn't 2K Compliant,


Winbuilder now works, thanks,

i see this issue still exists,

further more i am trying to build Winbuilder LiveXP "Offlinesysprep"

i'm getting this error,

"failed to cab compress"
............DPMtmp\D\M\AM2\ahci7xx.sys TO
............AHCI7XX.SY_.

the thing is, i can't find ahci7xx.sys in the pack,

seems strange how Windows 2k thinks ahci7xx.sys is corrupt, and now "MakeCab" which i assume Winbuilder uses is also complaining about ahci7xx.sys,

what is up with this bloody ahci7xx.sys ?

and why does every search of every-kind i do for the file/string for "ahci7xx" turns up with nothing?


the only time ahci7xx is actually mentioned, and that is in the file
"DriverPack_MassStorage_wnt5_x86-32.ini"

[AM2]
ms_count=1
ms_1_deviceName="AMD AHCI Compatible RAID 7xx"
ms_1_tag="ahci7xx"
ms_1_sysFile="ahci7xx.sys"
ms_1_hwids="PCI\VEN_1002&DEV_4380&SUBSYS_280A103C,PCI\VEN_1002&DEV_4380&SUBSYS_2814103C,PCI\VEN_1002&DEV_4392&SUBSYS_3029103C,PCI\VEN_1002&DEV_4391&SUBSYS_3029103C,PCI\VEN_1002&DEV_4391&SUBSYS_OE08105B,PCI\VEN_1002&DEV_4392&SUBSYS_OE08105B,PCI\VEN_1002&DEV_4391&SUBSYS_C2151631,PCI\VEN_1002&DEV_4392&SUBSYS_C2151631,PCI\VEN_1002&DEV_4391&SUBSYS_E2191631,PCI\VEN_1002&DEV_4392&SUBSYS_E2191631,PCI\VEN_1002&DEV_4391&SUBSYS_E2171631,PCI\VEN_1002&DEV_4392&SUBSYS_E2171631,PCI\VEN_1002&DEV_4393&SUBSYS_OE10105B,PCI\VEN_1002&DEV_4393&SUBSYS_OE11105B,PCI\VEN_1002&DEV_4393&SUBSYS_OE13105B,PCI\VEN_1002&DEV_4393&SUBSYS_OE14105B,PCI\VEN_1002&DEV_4393&SUBSYS_OE0E105B,PCI\VEN_1002&DEV_4393&SUBSYS_OE0F105B,PCI\VEN_1002&DEV_4391&SUBSYS_76401558,PCI\VEN_1002&DEV_4391&SUBSYS_76411558,PCI\VEN_1002&DEV_4391&SUBSYS_2A6E103C,PCI\VEN_1002&DEV_4392&SUBSYS_2A6E103C,PCI\VEN_1002&DEV_4391&SUBSYS_0E13105B,PCI\VEN_1002&DEV_4392&SUBSYS_0E13105B,PCI\VEN_1002&DEV_4391&SUBSYS_0E14105B,PCI\VEN_1002&DEV_4392&SUBSYS_0E14105B,PCI\VEN_1002&DEV_4391&SUBSYS_A7051478,PCI\VEN_1002&DEV_4392&SUBSYS_A7051478,PCI\VEN_1002&DEV_4391&SUBSYS_55021565,PCI\VEN_1002&DEV_4392&SUBSYS_55021565,PCI\VEN_1002&DEV_4391&SUBSYS_700116F3,PCI\VEN_1002&DEV_4392&SUBSYS_700116F3,PCI\VEN_1002&DEV_4391&SUBSYS_31331297,PCI\VEN_1002&DEV_4392&SUBSYS_31331297,PCI\VEN_1002&DEV_4391&SUBSYS_100415BD,PCI\VEN_1002&DEV_4392&SUBSYS_100415BD,PCI\VEN_1002&DEV_4391&SUBSYS_014C1025,PCI\VEN_1002&DEV_4392&SUBSYS_014C1025,PCI\VEN_1002&DEV_4391&SUBSYS_75011462,PCI\VEN_1002&DEV_4392&SUBSYS_75011462,PCI\VEN_1002&DEV_4391&SUBSYS_73021462,PCI\VEN_1002&DEV_4392&SUBSYS_73021462,PCI\VEN_1002&DEV_4391&SUBSYS_73041462,PCI\VEN_1002&DEV_4392&SUBSYS_73041462,PCI\VEN_1002&DEV_4391&SUBSYS_01551025,PCI\VEN_1002&DEV_4392&SUBSYS_01551025,PCI\VEN_1002&DEV_4391&SUBSYS_02591028,PCI\VEN_1002&DEV_4392&SUBSYS_02591028,PCI\VEN_1002&DEV_4392&SUBSYS_027E1028,PCI\VEN_1002&DEV_4391&SUBSYS_82EF1043,PCI\VEN_1002&DEV_4392&SUBSYS_82EF1043,PCI\VEN_1002&DEV_4391&SUBSYS_FF6A1179,PCI\VEN_1002&DEV_4391&SUBSYS_FF621179,PCI\VEN_1002&DEV_4391&SUBSYS_113E1734,PCI\VEN_1002&DEV_4392&SUBSYS_113E1734,PCI\VEN_1002&DEV_4391&SUBSYS_113A1734,PCI\VEN_1002&DEV_4392&SUBSYS_113A1734,PCI\VEN_1002&DEV_4391&SUBSYS_113B1734,PCI\VEN_1002&DEV_4392&SUBSYS_113B1734,PCI\VEN_1002&DEV_4391&SUBSYS_113D1734,PCI\VEN_1002&DEV_4392&SUBSYS_113D1734,PCI\VEN_1002&DEV_4391&SUBSYS_88AD1033,PCI\VEN_1002&DEV_4391&SUBSYS_01471025,PCI\VEN_1002&DEV_4392&SUBSYS_01471025,PCI\VEN_1002&DEV_4391&SUBSYS_014B1025,PCI\VEN_1002&DEV_4392&SUBSYS_014B1025,PCI\VEN_1002&DEV_4391&SUBSYS_01481025,PCI\VEN_1002&DEV_4392&SUBSYS_01481025,PCI\VEN_1002&DEV_4391&SUBSYS_01491025,PCI\VEN_1002&DEV_4392&SUBSYS_01491025,PCI\VEN_1002&DEV_4391&SUBSYS_30E3103C,PCI\VEN_1002&DEV_4391&SUBSYS_30F2103C,PCI\VEN_1002&DEV_4392&SUBSYS_30F2103C,PCI\VEN_1002&DEV_4391&SUBSYS_3600103C,PCI\VEN_1002&DEV_4392&SUBSYS_3600103C,PCI\VEN_1002&DEV_4391&SUBSYS_30F1103C,PCI\VEN_1002&DEV_4391&SUBSYS_30E4103C,PCI\VEN_1002&DEV_4392&SUBSYS_30E4103C,PCI\VEN_1002&DEV_4391&SUBSYS_30FB103C,PCI\VEN_1002&DEV_4392&SUBSYS_30FB103C,PCI\VEN_1002&DEV_4391&SUBSYS_30FE103C,PCI\VEN_1002&DEV_4392&SUBSYS_30FE103C,PCI\VEN_1002&DEV_4391&SUBSYS_30FC103C,PCI\VEN_1002&DEV_4392&SUBSYS_30FC103C,PCI\VEN_1002&DEV_4391&SUBSYS_149210CF,PCI\VEN_1002&DEV_4391&SUBSYS_43901019,PCI\VEN_1002&DEV_4392&SUBSYS_43901019,PCI\VEN_1002&DEV_4391&SUBSYS_82881043,PCI\VEN_1002&DEV_4392&SUBSYS_82881043,PCI\VEN_1002&DEV_4391&SUBSYS_025B1028,PCI\VEN_1002&DEV_4391&SUBSYS_025A1028,PCI\VEN_1002&DEV_4391&SUBSYS_02571028,PCI\VEN_1002&DEV_4392&SUBSYS_02571028,PCI\VEN_1002&DEV_4391&SUBSYS_02551028,PCI\VEN_1002&DEV_4391&SUBSYS_43911849,PCI\VEN_1002&DEV_4392&SUBSYS_43921849,PCI\VEN_1002&DEV_4393&SUBSYS_43931849,PCI\VEN_1002&DEV_4391&SUBSYS_B0021458,PCI\VEN_1002&DEV_4392&SUBSYS_B0021458,PCI\VEN_1002&DEV_4391&SUBSYS_014E1025,PCI\VEN_1002&DEV_4391&SUBSYS_11171043,PCI\VEN_1002&DEV_4392&SUBSYS_014E1025,PCI\VEN_1002&DEV_4391&SUBSYS_014F1025,PCI\VEN_1002&DEV_4392&SUBSYS_014F1025,PCI\VEN_1002&DEV_4391&SUBSYS_303617AA,PCI\VEN_1002&DEV_4392&SUBSYS_303617AA,PCI\VEN_1002&DEV_4391&SUBSYS_303F17AA,PCI\VEN_1002&DEV_4392&SUBSYS_303F17AA,PCI\VEN_1002&DEV_4391&SUBSYS_FF501179,PCI\VEN_1002&DEV_4391&SUBSYS_02641028,PCI\VEN_1002&DEV_4391&SUBSYS_02651028,PCI\VEN_1002&DEV_4391&SUBSYS_0E0E105B,PCI\VEN_1002&DEV_4392&SUBSYS_0E0E105B,PCI\VEN_1002&DEV_4391&SUBSYS_0E0F105B,PCI\VEN_1002&DEV_4392&SUBSYS_0E0F105B,PCI\VEN_1002&DEV_4391&SUBSYS_0E10105B,PCI\VEN_1002&DEV_4392&SUBSYS_0E10105B,PCI\VEN_1002&DEV_4391&SUBSYS_0E11105B,PCI\VEN_1002&DEV_4392&SUBSYS_0E11105B,PCI\VEN_1002&DEV_4391&SUBSYS_43911002,PCI\VEN_1002&DEV_4392&SUBSYS_43921002,PCI\VEN_1002&DEV_4393&SUBSYS_43931002,PCI\VEN_1002&DEV_4381&SUBSYS_43811002,PCI\VEN_1002&DEV_4380&SUBSYS_43821002,PCI\VEN_1002&DEV_4380&SUBSYS_43811002"
ms_1_isBusExtender=false



"ms_1_sysFile="ahci7xx.sys"

it mentions this file, but this not a tangible file, this reference points to something that does not exist,

i'm very confused, i'm not really on these forums, but i thought i should share with what i have observed in the past now that i have got a error with Winbuilder XPLive which is in relation to "ahci7xx.sys"

if ahci7xx.sys does exists, i can't find it in the driver pack,

"you will have to choose an alternate host to do RIS without one..."
Won't "Tftpd32" resolve that issue, as it works very well for PXE Booting,

or does AutoImage insist on having a windows server?

i'm very confused now,

network installs is now supported thanks to the new method SAD M2,

but could someone explain how, or perhaps lead me to a website that does,

i was originally planning to do it using the "Sysangel" http://ping.windowsdream.com/winner.html
Method, but of course ran into the problem of those 2 files not being found,

if i run the SAD M2 option on the disk, will that do the trick, or does using this new SAD option require me to use a specific method,

a method perhaps that does not involve the winner project over at sysangel,

i have windows xp as host,

i want a laptop to load up a PXE boot and then install windows XP over the LAN

the XP i want to install is

XP SP3 December 2008 updates slipstreamed + Auto answer file created,

but not sure how to go about it now, do i just do M2 SAD option, then carry on with the Sysangel winner option,
or do i need to use Autoimage,

could some one help me, as i'm a little confused,

does this new SAD option fix the XP so i can use it with any type of RIS install method, or do i still need to do something specific, or use a particular method,

appreciate any help, thanks, or any suggestions on a method anyone can recommend (i use Tftpd32 as a server, i do not and will not use windows server (way out of my league unfortunately, i always somehow break it too easily)).

10

(2 replies, posted in Universal Imaging)

i think you need mysysprep that will get around the problem of WHQL, which is well mentioned many times here in these forums,

not sure what you mean when you say "My questions (finally) are, can I extract the driver packs to c:\drivers INSTEAD of manually looking around for all the drivers for the dell pcs like Vernalex does?"

if you mean without sub directories, no because of the ini (inf) files will clash

my sysprep scanner documentation should tell you about it's limitations, but to my knowledge the sysprep scanner was designed to get around the registry limitations entirely,

driverpacks always looking to expand it's database, if you do a roll out and you notice a driver was not found, then find the HWIDS and let driverpacks know, and they will no doubt add it in at a future date,

note, whether they will add specific DELL hardware drivers in or not i'm not sure,

just a query, is there an actual reason why your choosing Acronis over Ghost?

does that mean if using mysysprep program get used, then SysPrep Driver Scanner is no longer needed,

http://www.vernalex.com/tools/spdrvscn/

fair enough, just thought i'll think out loud, that's all,

as i said, wasn't that sure anyway, i'll leave the real thinking to you guys,

thanks for reading anyway.

was reading up further, and found that live compression can help upto 40%,

what i mean is many files on windows xp setup cd are in fact compressed with CAB compression
I.E. explorer.exe but on CD it would be explorer.ex_
now this underscore at the end of the extension tells windows setup it needs to be de-compressed, could this be utilized, or would this invalidate what M3 is about, not sure, as of course M3 is probably been designed to fulfil more then one roll,

just an idea out loud, as compression would improve file access times as the work load would be lowered on the drive and shifted over to the CPU and HD (HD depending on buffers or cache of course)

well you got me thinking on this one, as what you said contradicted my albeit old knowledge i had with the way cdrom and dvd drives access files, and the way files are written to disk,

so i decided to update my knowledge and for the last 4 hours i've been doing some benchmarks, and a lot of reading, although the information from 10 years ago hasn't changed that much even though technology has,
i think it's because the fundamental technology in media drives hasn't really changed and is still based on the same principle's it always has been, a bit like a combustion engine i suppose,

any way, tests,
i extracted all the graphics drivers, A,B,C
900MB worth of data, i then set my self 3 tests in mind
1 burn files to disc as is
2 burn files to disc using optimize files first
3 create ISO (Optimize) and burn the ISO to disc


using nero drivespeed 4 i got to work

test 1 results

[14:20:26]  Drive: TSSTcorpDVD-ROM SH-D162D SB00
[14:20:26]  Disc: DVD+RW, 4.28 GB, RICOHJPN W11
[14:21:16]  Starting transfer rate test
[14:30:27]  Speed:4-8 X CAV (6.36 X average)
[14:30:27]  Elapsed Time:  9:11
[14:30:27]  Starting access times test
[14:30:37]  Random Access: 94 ms
[14:30:48]  1/3 Access: 108 ms
[14:31:05]  Full Access: 174 ms
[14:31:05]  Elapsed Time:  0:38
[14:31:05]  Starting burst rate test
[14:31:07]  Interface burst rate: 22 MB/sec (22436 KB/sec)
[14:31:07]  Elapsed Time:  0:02


test 2 results

[15:18:47]  Drive: TSSTcorpDVD-ROM SH-D162D SB00
[15:18:47]  Disc: DVD+RW, 4.28 GB, RICOHJPN W11
[15:19:14]  Starting transfer rate test
[15:28:25]  Speed:4-8 X CAV (6.36 X average)
[15:28:25]  Elapsed Time:  9:11
[15:28:25]  Starting access times test
[15:28:34]  Random Access: 94 ms
[15:28:45]  1/3 Access: 109 ms
[15:29:03]  Full Access: 175 ms
[15:29:03]  Elapsed Time:  0:38
[15:29:03]  Starting burst rate test
[15:29:05]  Interface burst rate: 22 MB/sec (22369 KB/sec)
[15:29:05]  Elapsed Time:  0:02


test 3 results

[16:14:55]  Drive: TSSTcorpDVD-ROM SH-D162D SB00
[16:14:55]  Disc: DVD+RW, 4.28 GB, RICOHJPN W11
[16:15:00]  Drive: QVCFG   0TI7OL2NSDQ7     1.03
[16:15:00]  Disc: Data CD, 98:20.06,
[16:16:04]  Starting transfer rate test
[16:19:34]  Speed:24-32 X P-CAV (28.26 X average)
[16:19:34]  Elapsed Time:  3:30
[16:19:34]  Starting access times test
[16:19:44]  Random Access: 106 ms
[16:19:56]  1/3 Access: 116 ms
[16:20:09]  Full Access: 132 ms
[16:20:09]  Elapsed Time:  0:36
[16:20:09]  Starting burst rate test
[16:20:11]  Interface burst rate: 19 MB/sec (19566 KB/sec)
[16:20:11]  Elapsed Time:  0:02


now i have to be honest, test 3 was hard, and not sure how reliable it is,

as i had to mount the ISO with Daemon tools, then run test 3 on Daemon tools drive
however i still feel the test is fine, as deamon tools still had to get the information of from the cdrom anyway in real-time

and the windows memory and cache was cleared after each test,

now at this point i could see results that even surprised me a little,

1/3 access and random access was a little faster reading from the actual files them selves and not from a ISO,
however Full Access was a lot faster extracting the files from the ISO.

also of note test 3 transfer rate scored a whopping 28.26 as opposed to test 1 & 2 which only scored 6.36,
and on this phase of the test cut the time from 9:11 to 3:30 which is huge,


now i wanted to rerun these tests but using the outer edge off the DVD-rom,
so i designed a track and put the information at the outer edge,
however test 1 would not run properly,

the sound coming from my drive was terrible, a lot of spinning up and spinning back down, i've seen this kind of thing before, it's where the drive does not aspect to be reading at such a slow speed, and yet the drive cannot read such small files at such high speed, so the drive is fighting with it's error correction technology, one wants to speed up, but the other is saying slow down.

so unfortunately on my drive i can't run these tests again using the (faster reading) outer track.

now what this all means i'm not going to say this is the 1st time in a very long time i have benchmark something, there are some smart people here that hopefully will confirm i done things right, and even better do further tests to see if the M3 Raw idea is veasable without some kind of container for the many many thousands of files that driverpacks have and can dvd-reader and writers handle this new method in general.

the above test's are what they, basic to say the least, and of course more tests, from smarter people then i will be needed to confirm,
but personally do fear the workload and extra fatigue added to a dvd-reader could be quite high,
in fact i've even seen on many occasions dvd reader's have trouble installing the first steps of windows XP.

i think you made the issue a little more complex then it has to be,

to my knowledge, acronis will take care of HAL, and SATA, but not other hardware, which is why the bootcd is so small (i think it supports raid as well, but don't hold me to that)

now the idea of acronis is to have a clean drive system, what i mean by that, is to only have windows drivers installed, so create a windows setup, but do not install any drivers at all, of course this is limiting considering how old windows xp driver database is.

to utilize driver packs, all you need is the system to start up enough for sysprep to do it's work, as long as the registry has been told where the drivers are located on the hard drive then sysprep will do the hardware device scan and find what it can, so in your case, you need to to a sysprep, then run below program, point to driverpacks, then create a image,

on roll out, acronis universal image will correct HAL and sort out SATA, enough to stop BLUE screen at least, then sysprep will take over, sysprep with the help from program below will run through hardware device scan utilizing all the drivers found in told location and hopefully bootup into windows desktop,

a little tip, from my experience do not install any graphics drivers, in base image, and don't include graphics driverbase, because there is a strong chance of bad install and blue screen, graphic drivers is very error proan, especially ATI and Nvidia. everything else is ok,

Accept for Nvidia Motherboard chipsets, these are a nightmare, especially NForce 1-2-3 Nforce 4 and above is not too bad.

there are other tips i could put in, but what's here covers the most part,

I'm quite sure you will need this

http://www.vernalex.com/tools/spdrvscn/

now i have not tried the above myself, due to the fact that acronis bootcd is not 100% compatible with all systems, because of the utilization of a GUI it uses, I've had some systems keyboard and mouse show very erratic behaviour which can't be resolve (some systems don't like so many resources being loaded in such a low environment) so i continue to use Ghost for this reason. ghost is simple, but it works on any system even all laptops that make it indispensable.

goodluck,

reason i ask is, from my experience DVD readers (Especially Writers) in general don't like reading extremely small files, I.E. 4Kb Files, not to mention the strain it puts on the drive aswell,

or will they be in some kind of BIN (Image) file,

hi, some of the things in the latest change log are a little unclear to me,

quick question, does the new version (8.05) now natively support network share installs, or is the above information (instructions) still needed, thanks,

overflow a question mate, about RIS, of topic, so i posted here,

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

20

(15 replies, posted in Other)

hat off, understood this topic quite well, this is what i do really, as in ghosting at present,

a little tip for imaging, if you want to utilize full UDMA functions with ghost try this

http://www.ibiblio.org/pub/micro/pc-stu … dma/devel/

2.7 version is very stable, and use the overlap switch "/O" for extra reliability, yes a small hit in performance is hit, but still Ultra DMA will be active, so a lot faster either way, speed difference to expect in ghost 30 to 60% increase in speed and because the CPU will not be getting pestered by the hard drive any longer, compression speed will increase a lot aswell, comes in handy when multicasting for sure, and the extra speed at compressing can't help, but of course there is always a downside, it doesn't always work, 2% of the time it may fail, so out of a 100 machines it may fail on 2 (and one more thing, do not try this in VMWare, version 5 supported this, but version 6 does not, DMA functions are already in VMWare by default, so this program will corrupt DMA memory)

there's other versions there on the site, like XDMA and some other, but in all honesty i have not tried them, took a while to create a cd with this version, and i had 2 cd's, one with and one without (yes i could of created 1 cd and create a bat file that showed a choice if to enable it or not....problem is i don't know how, scripting is not for me i can tell you)
and it was difficult to get it integrated with this http://www.netbootdisk.com/

but got there in the end

however XDMA unlike UDMA works with chipsets that don't utilize the south bridge, at the time of me using this driver in dos environment the systems we had were all old, so i chose to safer option and used UDMA2, however i may try out XDMA as i'm using ghost on new systems now, and motherboard companies are trying to eliminate the need for southbridge chipsets, as southbridge's actually degrade performance now because system are getting so fast

just thought you should know, (unless of course you already do)



OverFlow

you mentioned about RIS, (http://forum.driverpacks.net/viewtopic. … 82&p=3) and been reading a lot over at MSFN, i knew it existed, but never could entertain it, as it requires windows server 2003, which i've tried, and to be honest, i was messing around with security options, and i broke it, it wouldn't let me install programs,

i only tried it because it's been a long time since trying windows 2000 server (i was young then)

but the fact is, i was in way over my head, windows server 2003 was....well to much, too many options, and the manual and help files makes the bible look small you know,

and the fact that i broke it within 2 hours, well we all have our limits, and our maximum potential, well windows server edition's of any kind is way over my I.Q. level (no time for beating about the bush), and i admit it,

so without windows server RIS is out of the question (or at least not practical to use)

but you and people in MSFN i have to admit got me curious, so whilst digging around for info on "CD image ISO for PXE booting" and "UBCD4 Windows booting via PXE", i kept running into people having wars with each other which is better Imaging based, or RIS installs, this got me curious even further,

so after more digging (and listening to more people fighting with each other what method is better or not, (i say if there both good, then learn both)) i surprisingly found this very interesting website, and obviously my eye's lit up,

and i was hoping if you or anyone here could shed some light,

(i apologize, i know this is off topic, however i have every intention of utilizing Driverpacks with this program)

i found this topic so instead of posting in above i posted here, and put link above so you know what I'm talking about and where I'm connected to

anyway this is the website and program,

http://www.windowsdream.com/

i just wondered because of this

http://www.windowsdream.com/winner.html

seems really interesting, hasn't been updated for a while, but if it allows me to create a RIS, without having to learn RIS, well that would be great,

could you shed some light on this, is it good, no good, throw job, or good for windows for dummies (ME) but doesn't nor would it ever replace a full on RIS set-up.

thanks Jaak, your a star, didn't know about MSFN,

your right, universal imaging utility is talked about quite heavy over there,

did a search and found loads of info, and i've been reading over there about

http://www.symantec.com/business/produc … vid=1601_1

seems very promising, and unlike universal imaging utility, it's only a 1 of license, so i'm gonna try a demo i'm downloading now, do some research on it, and if good, then i'll just pay for that,

seems over there they were saying that the latest mysysprep 1.3 doesn't need a script or somthing,
but it did lead me to this,

http://www.myitforum.com/articles/15/view.asp?id=8997

some kind of already made script.

but from what i researched, universal imaging utility actually uses similar technology to mysysprep, which i found quite ironic,

any way, just wanted to say thankyou for letting me know about MSFN, never heard of it before,
(Y)



oh nearly forgot, how rude of me,

thanks overflow,

looks a very interesting tool, something that could deffiently come in handy, as i'm not keen in trusting the driver by symantec, been using driverpacks for a while now, and there solid through and through.

although, saying that, did a system the other day, and the audio wasn't installed,
it was a Foxcomm motherboard, Realtek HD audio.

but it's from my image not from a slipstream CD, which is why i did not report, as my image is nailed, hammered, and butchered together at the seems,

hehehe

thanks all, your stars,

we did indeed, that's why i re-editited, JINX hehehe

thanks for the info, i knew about ghost, as i set up cybercafes, done 14 now,

the image itself is tailored for cybercafes, which is why fresh setup's isn't really the way for me to go,

you see, customers want to use the machines, and what they hate the most is NAG screens,

they don't like things keep coming up what shouldn't,
i don't want to go into detail, but lets say, over a 1,000 settings have been adjusted to make the experience for the customer the best it can be,

that means, security, update settings, privacy settings, some kind anti-key logging software, and of course browser, messengers, well the list goes on,

with every program installed by default (from image) every program has been updated and settings configured for public use,

Nettime software helps a lot

and of course Goback 4.02 protects the systems from tampering,

so you see, (i should of explained this to begin with, i apologise) the image has a specific function,
and is tailored for a specific purpose, and it has tacken many many adjustments to iron out hundreds of little settings just to help out the customer more,

so getting back on topic, although reading WPI is intriguing, i can't let go of the image i have, for it has way to much time and resources from me to start again,

and the registry is quite clean, there are cleaners, and reg defraggers that can help with this process,
tuneup utilities was all i used, but CCleaner is something i now use aswell,

i was hoping that i could find a way of using UIU (which handles all sysprep functions for me, and enhance it somewhat) further and try and find a way of downloading HAL info, and make UIU just as effective as it has been all this time,

because UIU does everything for me, that is explained in this topic, and with the help from driverpacks, it is just as powerful as if it was the latest version, only i'm worried that it doesn't have the NEW HAL's drivers for modern day processors, and neither does driverpacks,

perhaps i should try and work out how UIU works, perhaps it uses something like "Mysysprep" already, and if it does, perhaps i could alter something that will make it future proof,

thanks any way, and if any one else here could shed some lite, perhaps someone has used UIU (universal imaging utility) themselves and have found a wau of making it understand future processors without having to use the latest version,

but thank you OverFlow, i did not know about "WPI", looks very interesting, could defiantly come in handy with fresh installs (coustomers repairs, not the main image needed for cybercafes only).

and thank you for your patience, like i said before, it was my mistake, i should of explained that the image is tailored for cybercafe roll out's.


and for the record, as much as i would love to do what UIU does manually (without the need of UIU), i'm just not as intelligent as you people here,

I'm 28 years of age, and things are not as easy to pick up as it once was, when i was 19, things were easy and fun, but these days, my mind has to try now, and things don't come as natural as it use to, I'm getting old,

so with respect, a lot of stuff here about using sysprep with scripts, and creating a database for HAL info with mysysprep, man i have to say, i feel a little intimidated, I'm just not that good,

to sum it up, i was hoping some one here could help me cheat, and enhance UIU further so i don't have to dive in to this deep stuff that you people here seem to know so well.

it was a long shot a best, i know not many people even know about UIU, so, still it was worth a try,

if you don't ask, then you will never know.

thanks anyway,

and sorry for any spelling mistakes, my spell checker in firefox isn't activated for some reason, will sort it out now, as I've edited this post, 5 times already,

well, onto learning WPI, sounds good.

see ya


edited, spell checker working again, corrected this post.

just for clarification, sorry,

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

so mass storage can't be touched, fine

but the other, when you say rename, does that mean i have to rename them to the same names that are in the source folder.

i.e.

D:\winxp\I386\$oem$\$1
DPM8021.7z

so if a new version came out say DPM8042.7z

i would have to rename this back to DPM8021.7z
and then put this in the folder, and delete the other one (the old version)

which of course would make sense, as if a script calls for DPM8021.7z, but that name didn't exist, then the file would not be found.

thanks again, your a star.

ok a little of topic here, but here goes,

i use a program called universal imaging utility,

story is, i use to work for a company that used this program, and they brought a volume license (which they now don't do)

the version i have is version 2, there on version 3.5 now, but i don't have a license for series 3, i only have a license for series 2, which of course they no longer support, nor am i valid any longer for updates of any kind,

now the program works fine, and under my license agreement i can continue to use it, but it's obviously it's well out of date, and so are the drivers, and i can't no longer update it because of no support,

http://binaryresearch.net/products/the_ … ng_utility

now what i do,

i have a setup which has 2 years of tayloring added to it,

so not to make things confusing i will explain what i do first then ask the question at the end,

01. i load up my master image
02. i make the changes i need to make
03. i run UIU (UIU puts all the drivers into INF\UIU\ location)

bare in mind these drivers are very old, and i have no support so i can't update them using UIU

04. UIU after putting drivers into location, then runs Sysprep in the background.
05. UIU is then finished and i exit UIU.

system is now in ready be shutdown and sysprep has already been run and finished removing all the necessary hardware, and a image should be tacken but i don't do this yet,

06.  i now decompress all driverpacks in to windows\inf\UIU directory
07.  i now use http://vernalex.com/tools/spdrvscn/index.shtml scanner
08.  i tell scanner to load windows\inf\UIU\D\ (tell sysprep to check these drivers first)
08a scanner is then told to check UIU after driverpack (in other words when loading up sysprep will use driverpack drivers first, if a driver is not found then it will resort to using the old UIU drivers if need be which is good, because UIU contains HAL information which driverpacks doesn't have) i think.

09. i shut down the system, and create a ghost image ready for deployment.


now my question and explanations,

the reason i use driverpack is obvious, UIU drivers are old so driverpacks make up the difference,
UIU version 2 (i have) is no longer supported, and there license system has changed, and i no longer work at my company where we used it, and i asked for a copy as i was made redundent (cut backs), the head technician gave me version 2 which they had, as they didn't need it any longer, as they now buy version 3 licenses.

now my question is, is the proceadure i'm doing above valid, i've read a lot of material concerning the sysprep scanner, and everything has always worked ok, but i'm getting worried because after reading all the info in this topic, people are talking about dual cores, and multi-cores HAL's, and i'm concerned that UIU version 2 will suddenly stop working because it won't have the updated HAL's needed for modern day processor's

also could any one suggest any way of improving my proceadures above, or perhaps suggest a alternative
perhaps there's a way of downloading some new HAL drivers i could put into my UIU folder so UIU will continue to work,


i know the best method would be to purchase version 3, but that is out of the question, as they now sell them on a per license basis, and beside the UIU i got is ok, i'm just worried it won't support the new HAL's needed for modern day processor's, and all i need is to download the latest HAL drivers,

as i don't need the latest UIU drivers, as i use DRIVERPACKS, all i need is the latest HAL drivers,

sorry to make this so long, i never meant to make this post to be so long,
but i appreciate any help, as the above mentioned here concerning mysysprep, and the methods making sysprep work without UIU seems way to complicated for me,

thanks, and i please don't have a go at me for making such a long post, i'm new to here.

still not a bad idea, because it could be anything, perhaps a sound driver, videro driver, or perhaps a driver but no knowing which one is causing a problem,

having a all in 1 cd is quite a good idea, ecspecially if one has a tight time limit getting a system setup,

one solution is of course using cd-rw's, but many many drives don't like installing from these, usually get massive slow downs, and if it's a old drive, then usually one gets a error at some point about a file can't be read,

i like you also need to create 2 CD's aswell, although i'm learning to create a network install version, and i've already learnt how to do PXE booting (PXE booting took a while to learn but i got there)

gets worst, because i have to create cd's for

windows xp retail w/out drivers
windows xp pro w/out drivers
windows xp OEM w/out drivers,
& windows 2000 pro w/out driverpacks (but this don't get updated that much as not needed that much, usually for old laptops with 200MB memory or less)

so 6 cd's really i need to create, would be nice to of got that down to 3, but like i said i'm learning the network option now, which will also allow me to install off a hard drive if i do need to be called out, (thanks to the help from this post http://forum.driverpacks.net/viewtopic.php?id=2502)

still, having this multi cd version could be useful (even PXE Booting is not 100% to work, because of some bad PXE firmware's around) and would cut down on cost, and of course help out global warming hehehe


i think the hard thing would be, the bootsector on the CD, as windows cd use there own coustomized boot block which then calls for the relevent script (just a theory, not to sure if this is right)