Search options (Page 125 of 213)

RUN AS could be used too

some of the drivers we are discovering do not support legacy mode...

these drivers will need PnP entries seeded into in the Hive files.

this has been noted by cdob and little bugger and verified by some others.
so far only only Nvidia and Jmicro have been positively identified as failing if this is not done...
It may be that SAS and other Server drivers also need this to be addressed and could be why we were stumped.
- how can a registry entry be required at textmode... HUH? apparently a hive entry will acomplish this.

many txtsetup.oem files contain registry info but only the few drivers that have discontinued (or never had) support for legacy mode will fail.

yup... and should lead us to a driver

Newsposter is correct pirates get to 'walk the plank' here.

you should start with a clean OEM/Retail copy and do your own work...
that way you know what you have. We don't recomend you trust warez, at all...

haveing made that clear... we will help you create your own UXP

you only need three simple tools RVM Integrator, nLite, DriverPacks. in that order.
your first time may take you a couple hours but most of us can do it in about twenty minutes after you get the hang of it.

the only way we can tell if your hardware is supported would be if you can you post your hwids? (tool in my signature)

Say no to warez... go legit  or  walk the plank

set autologon in the registry
set the logon count to 1
use an account specifically permissioned to install in your environment. (custom account)

call the DriverPacks Finisher
remove / overwrite the registry entries (for security)
call shutdown -r -t 30

i could think of more but that is simple and effective

you are running base version 8.05 you will need the newer version here... (release candidate)

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

see if that helps...

link to tutorials are in my signature... but a tutorial for SAD (to be renamed SoFI, Software First Installer) is not yet written.
the post you referenced is leading up to a tutorial...

Sure... that is good too

we need to find the conflict...

any process of elimination gets us closer to the cause and ultimately the fix.

I must point out again that your source is corrupted...

If 'Method 2' setup is found then txtsetup.org and dosnet.org MUST exist.
(since they are backed up when 'Method 2' is installed and you log indicates M2 was installed)

What are you doing to your source? If m2 is installed then txtsetup.org and dosnet.org MUST exist!

( I will have to assume the following since i still don't know what you did - you could tell us... that might be nice )

If they don't then you have DESTROYED your source and must start over...  (didn't i say this already in an earlier post)

your freeze at t-34 is then assumed to be because your source is corrupted.

Can you please tell us how you are manageing to delete the backup files every time?
this may be the key to why you are not successful...

Note to self- next version; create critical error if backups are not found and m2 setup is... kidding

That makes sense... stay tuned for our next packs... we will have this resolved soon

Thanks for getting back to us

the guys have been beating thier brains out on graphics and mass...

you have access to the testing forum... everything is posted there that is in process...

the answer is pack extraction takes three minutes and since we target UNATTENDED installs we don't care
(we arn't watching, (that would be an attended install))

It is possable it just is not neccessary... if all the drivers get extracted then we won't miss any

It is also possable that determining which drivers we need and only extracting those might take longer.

PS Windows does not always pick the driver we think it will

base and mass storage versions you are useing and on what OS...