that is an excellent question for RogueSpear our good freind and author of autoimage 

He may not respond to this thread right away... IDK if he checks here daily
- you may get a quicker response at his forum...

- you could try it ;p

or does AutoImage insist on having a windows server?

As you already know RIS is a server feature...
you will have to choose an alternate host to do RIS without one...
Imageing software such as ghost is affordable and effective. this may be a better solution for you?

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)).

I created a workaround useing a command line switch, but in the process of createing the workaround i fixed the problem and the command line switch was not neccessary, however it is still available.

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

new command line switch by request  /proxy

Usage /proxy:"LocalProxy:Port"[,"Username","Password"]
examples
DPs_BASE.exe /proxy:"192.168.1.1:8080"
DPs_BASE.exe /proxy:"LocalProxy:8080","administrator","password"

Another problem, the update checker doesn't work for me.  It just hangs the whole thing.  Through Google, I found some other people here were having the same problem and it seemed something was added to the .INI, but I can't find what.  I'm using an ISA proxy if that matters, and that proxy is set in my IE settings.

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

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."

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.

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.

however my question is, when a new release (driverpacks comes out)
i assume running a new slipstream will break the above again,

what is the process of updating the above folder (source files)

could i just drag the driverpack file (the updated one's in question) over to the source file and delete the other one (old driverpack file),

or is it a little more complex then that,

because as much as i apreciate the above help, doing these steps everytime could open a window for errors to sneak in,

one last question,

on my windows, i use

RyanVM
NLite
then driverpack slip method 2 gui run once,

now you mentioned "add gui run once section from winnt.sif to your \\server\winxp\i386\$oem$\$1\unattend.txt (or whereever you keep your unattend file) and delete winnt.sif"

problem is i don't have a unattend.txt file, as i created non attend using nlite, and nlite doesn't create this file as i think it adds it directly into winnt.sif, i did a complete search unattend.txt files and none was found at all,

what i did was used setmgr and created a unttend.txt file, and copied the info from winnt.sif over to unateend.txt, then i continued with your instructions....is that right????

tried to right out as clear as possible, but you know how it is, the more detail one thinks they add will help, but in fact actually makes things worst,

Summary:
2 questions were asked,
1 method needs verifying (copying new driver pack manually over will this work) ?

thanks,

if i haven't explained as clear as i should then just say and i will explain as best as i can, and go 1 step at a time instead of putting all this in 1 post.