Search options

I've got the driver from the bloated install if any of you guys want it.

And yes, it works [as far as to say that it installs - i've added it to a 3rd party driverpack i make at work and it shows as installed within windows]

Cheers
Nath.

Nope the name of it can be anything so long as it ends in .sif and resides in the templates folder inside i386 of the image. Its not quite like a CD install, which is why people need to use caution with RIS installs.

If it made it and put it in the usual location of a CD install, it would serve no purpose as RIS doesnt take it's templates from there [as mentioned above] plus there are differences in a RIS template and a normal CD-based one.

Havent the time unfortunately to go into the details of RIS for you, but i appreciate your feedback etc.

I agree with you there, however, you are missing my point.

Unless you use RIS, you wont fully understand what I mean, not the layout as i believe DP fully supports RIS installs, being that a XP RIS install [using RVM/NLITE/B.T.S.] works perfectly. I use AutoImage for this and i dont have a problem here.

The XP build looks like this:

RISIMAGENAME\   >   i386\
                >   $OEM$\   >   $1\

and inside the $1 directory are the B.T.S. files and bin directory.

This may be down to how AutoImage uses DP_Base via API to add the drivers but I can't be 100%. All I know is it works for XP like this, but doesnt for the specific version of the OS I've mentioned. And even if i dont use Bâshrat the Sneaky at all, i still get the BSOD issue unless i work out a way to not use the $OEM$ directory you see.

The issue is fundementally confusing but i'll find a way somehow

Any RIS users about please post... would help me out to know if i'm alone in this specific problem or not lol

Regards
Nath.

As you may have noticed, i have trouble explaining myself sometimes... mainly down to time constraints and not wishing to spend every waking moment on a forum

Nope, as its not really the issue, as how would I start the process off?

It works fine with other images, just seems to be this particular OS - not 2003, but 2003 Ent SP2 [R2].

WINNT.sif isn't used on RIS installations as RIS installations use multiple templates that you can "pick & choose" during the F12 process.

Thanks for the info. Interesting stuff, but not sure how it will apply to a RIS install.

Nath.

lol yes... that what i've been saying

like the log from the first poster:

its a popup... which u click "ok" and it carries on. Isn't a problem to the build, but means when called by another program for automation, its not automated of course if you have to click a "ok" button lol

Nath

Hi there Tiger

That wasn't actually my log lol I was just adding my two pence to the thread

I've no doubt that it isn't needed, but what I was meaning is that if its not needed, there should be something within DP that prevents it trying to add it

When calling DP from a different program and its meant to be silent, having the pop-up although informative, it defeats the object of the api running automated.

Cheers
Nath

I've taken a screenshot of it this time around if you want it Bâshrat the Sneaky...

and also, if I choose GUIRunOnce as the finishing method, I dont get any errors [except that if I look at the C drive afterwards, I see that the driverpacks and finisher hasn't been cleared up after a reboot].

Cheers
Nath

Ahhh... thought someone might have beaten me to that one

Nath.

It will slipstream them into text mode regardless I believe - RogueSpear has started a BugTracker on here.... just so you know, although I am unaware whether this is just with the API mode [i.e. using AutoImage with Bâshrat the Sneaky DP] or not.

Regards
Nath.

nope [hehe I'm dumb sometimes but not that dumb ]

I didn't, at least, as it is greyed out - i.e. as i dont have the mass storage driverpack in the driverpacks folder it won't let you choose it.

Any ideas?

I can anything else that it can be  :S

Cheers
Nath