hi
mass storage textmode will not be slipped in from 3rd party.

Indeed.

Hence, when you are seeking for a quick and dirty method to add missing TM drivers, I would suggest using nLite for the task.
Just be sure you select them as TM and it should work.

An alternative is of course to request these drivers to be added to the official pack -that way we all will profit from them

if you look around in mass storage forum, you can find a test release that should adress intel conflics.

edit; I just read that remark by Mr Smartepants. This is one more VERY GOOD reason to not remove manual install and upgrade.

another undesirable side effect of OEMPREINSTALL=YES is you cant use hit F6 to supply a driver on a floppy

just put the floppy in without hit F6 , it wil load the driver automaticly.

textmode not doing what it was supposed to do, that I could reproduce long ago, and I probably can again.

another undesirable side effect of OEMPREINSTALL=YES is you cant use hit F6 to supply a driver on a floppy

Which is not really needed anymore thanks to the DriverPacks

But yes, that is pretty annoying, still.
I'm not sure whether MS did that on purpose or just thought that if you are going unattended, you wouldn't supply a driver floppy anyway.

Thankfully, they finally realized floppies are so last millenium and offer the option to provide drivers on a CD/DVD/USB stick/HDD with Vista.
You cannot assume how much that pissed me off before I discovered the DriverPacks! >8(

jtdoom wrote:

Hi

in NLite, there are two settings wich will kill the process.

UNattended setting > OEM Preinstall >> defaults to enabled, and should be DISABLED
Therefore, check WINNT.SIF
the line has to say this, OemPreinstall=No.
If it says "YES", method 2 textmode is not going to work.

another option in Nlite, will cause DPs_Base to throw error, SETUP.EX_ not found
This is caused by this one
Operating system options > Manual Install and Upgrade
If you remove this, building a method 2 cannot work.

Are yopu sure about both of this?
For #1, I would assume the BASE re-sets the parametre properly (hence, you should always nLite before BASEing).

For #2, I was ripping that part out for a very long time to save valuable space on my CD (have moved to DVD now, if you remember), and seeing as I always used M2, I'm unsure about whether it would really break it.

Things may have changed in the past so I may not be up to date here
Anyway, it certainly does not hurt follwing your advice, I'm just uncertain whether it is absolutely vital...

I'm with Helmi on this one.  I have always used nlite to remove the "manual install and upgrade" option to save space and I always use DP_base method 2 and I've never had a problem.  I can understand why some people might have problems since that nlite option removes the capability for the "recovery console" as well as other options that might be needed prior to installing windows.

Actually, DP_base sets that parameter if it's not already set.  If the parameter is set already, DP_base will change it depending on your settings.
If I'm wrong, please correct me.
That's one of the reasons it's important to run DP_base last.

I just checked, with only manual upgrade and install removal, and setup.ex_ missing was apparently triggered by another Nlite option. I cannot recall anyone ever reporting this error (save me.. I did mention it in a report on a  nightly.) so I reckon it is very uncommon.
Nevertheless, I will try find back that option that dood it to it.
(like in, "The butler dood it." hehehe)

yes, Base did not alter OEMpreinstall=YES line.

I am going to make install disks with it enabled and disabled and see if it makes a difference.

Hi

in NLite, there are two settings wich will kill the process.

UNattended setting > OEM Preinstall >> defaults to enabled, and should be DISABLED
Therefore, check WINNT.SIF
the line has to say this, OemPreinstall=No.
If it says "YES", method 2 textmode is not going to work.

another option in Nlite, will cause DPs_Base to throw error, SETUP.EX_ not found
This is caused by this one
Operating system options > Manual Install and Upgrade
If you remove this, building a method 2 cannot work.

Are yopu sure about both of this?
For #1, I would assume the BASE re-sets the parametre properly (hence, you should always nLite before BASEing).

For #2, I was ripping that part out for a very long time to save valuable space on my CD (have moved to DVD now, if you remember), and seeing as I always used M2, I'm unsure about whether it would really break it.

Things may have changed in the past so I may not be up to date here
Anyway, it certainly does not hurt follwing your advice, I'm just uncertain whether it is absolutely vital...

in NLite, there are two settings wich will kill the process.

UNattended setting > OEM Preinstall >> defaults to enabled, and should be DISABLED
Therefore, check WINNT.SIF
the line has to say this, OemPreinstall=No.
If it says "YES", method 2 textmode is not going to work.

another option in Nlite, will cause DPs_Base to throw error, SETUP.EX_ not found
This is caused by this one
Operating system options > Manual Install and Upgrade
If you remove this, building a method 2 cannot work.