OPEN: keep F6 to load textmode drivers available as an option (Page 1 of 2)

I was pretty sure this was already implemented into the GUI version.

Hmm...
I was actually refering to using BOTH, instead of one or the other...
As-is, using the '0' option, i can not use F6... but can have an unattended install.
using '1', i can use F6, but not unattended.

I know some ppl had a workaround on MSFN, but I would love to see the workaround be added to the GUI so the F6 can be used in conjunction with the '0', without all the hassle of having to custom modify the files.

To load both the drivers of DriverPack MassStorage and an additional driver. Or to make a work-around possible.

Though I must admit that I don't know which text mode mass storage driver is missing?

I had the same problem with Intel sata raid. However, my workaround involves the long, arduous, tedious, time consuming and back breaking task of REMing out JAHCI in SCSI.LOAD     Seems that some drivers are incompatible with others.

<shrug>

Maybe you should try ridding JAHCI? or some other driver.   Go down the line.

Last edited by razormoon (2006-05-30 04:56:55)

These are the lines added to txtsetup.sif in the [SCSI.LOAD] section:

3ware9k=3ware9k.sys,4
3ware78k=3ware78k.sys,4
3waregsm=3waregsm.sys,4
aec6210=aec6210.sys,4
aec6260=aec6260.sys,4
aec6280=aec6280.sys,4
aec68x5=aec68x5.sys,4
aec6880=aec6880.sys,4
aec6897=aec6897.sys,4
aec67160=aec67160.sys,4
aec671x=aec671x.sys,4
ahpt3xx=ahpt3xx.sys,4
aac=aac.sys,4
aar1210=aar1210.sys,4
dpti2o=dpti2o.sys,4
adpu160m=adpu160m.sys,4
adpu320=adpu320.sys,4
aadpu320=aadpu320.sys,4
a320raid=a320raid.sys,4
cda1000=cda1000.sys,4
aarich=aarich.sys,4
amdbusdr=amdbusdr.sys,4
arcm_x86=arcm_x86.sys,4
m5228=m5228.sys,4
m5281=m5281.sys,4
m5287=m5287.sys,4
m5288=m5288.sys,4
m5289=m5289.sys,4
cercsr6=cercsr6.sys,4
hpt3xx=hpt3xx.sys,4
rhpt3xx=rhpt3xx.sys,4
hpt374=hpt374.sys,4
hptmv=hptmv.sys,4
hpt366=hpt366.sys,4
hptmv6=hptmv6.sys,4
rr2320=rr2320.sys,4
rr404=rr404.sys,4
rr2310=rr2310.sys,4
ipsraidn=ipsraidn.sys,4
nfrd960=nfrd960.sys,4
iastor=iastor.sys,4
raidsrc=raidsrc.sys,4
iteraid=iteraid.sys,4
;jahci=jahci.sys,4
megaide=megaide.sys,4
mraid35x=mraid35x.sys,4
dac2w2k=dac2w2k.sys,4
dac960nt=dac960nt.sys,4
symmpi=symmpi.sys,4
nvatabus=nvatabus.sys,4
nvraid=nvraid.sys,4
fasttrak=fasttrak.sys,4
fasttx2k=fasttx2k.sys,4
aftx2k=aftx2k.sys,4
s150sx8=s150sx8.sys,4
fastsx=fastsx.sys,4
sptrak=sptrak.sys,4
ulsata=ulsata.sys,4
ulsata2=ulsata2.sys,4
ultra=ultra.sys,4
ql2100=ql2100.sys,4
ql2200=ql2200.sys,4
ql2300=ql2300.sys,4
ql12160=ql12160.sys,4
pnp949r=pnp949r.sys,4
pnp680=pnp680.sys,4
pnp680r=pnp680r.sys,4
si3112=si3112.sys,4
si3112r=si3112r.sys,4
ati3112r=ati3112r.sys,4
si3114=si3114.sys,4
si3114r=si3114r.sys,4
si3114r5=si3114r5.sys,4
si3124=si3124.sys,4
si3124r=si3124r.sys,4
si3124r5=si3124r5.sys,4
si3132=si3132.sys,4
si3132r5=si3132r5.sys,4
sisraid1=sisraid1.sys,4
sisraid=sisraid.sys,4
sisraid2=sisraid2.sys,4
viamraid=viamraid.sys,4
viapdsk=viapdsk.sys,4
vmscsi=vmscsi.sys,4

If you notice, I keep JMicron from loading by putting a semi colon in front per Bashrat.

;jahci=jahci.sys,4

You can try putting semi colons down the list and try to find out which ones are conflicting. You can start with jahci 

I think using textmode 'as is' causes a BSOD. So he needs to use F6 instead. I had the same problem. However, after REMing all drivers, one by one, I found that JMicron (JAHCI) was causing an issue with intel sata raid. I posted the driver entries so that someone with this issue could try experimenting with suppressing the loading of drivers.

Last edited by razormoon (2006-05-30 06:25:44)

F6 isnt needed just put in the floppy with your driver during the setup and it will load it automaticly.

DONATE!
HWID's Tool     Read BEFORE you post

Just as it says

DONATE!
HWID's Tool     Read BEFORE you post

When you use XP unattended,and this is in your first part of winnt.sif :

[Data]
	UnattendedInstall = "Yes"
	MsDosInitiated=No

[Unattended]
	UnattendMode = FullUnattended
	UnattendSwitch = Yes
	OemSkipEula = Yes
	FileSystem = *
	WaitForReboot = No
	TargetPath = "\Windows"
	Hibernation = No
      Repartition= No
	OemPreinstall=Yes

Any floppy with sata drivers will load automaticly without pressing F6 during setup.

Wich part dont you understand?

Last edited by muiz (2007-06-04 18:18:21)

DONATE!
HWID's Tool     Read BEFORE you post

Yep , floppys dont work if they are not in the computer.LOL

DONATE!
HWID's Tool     Read BEFORE you post

I can't speak from personal experience because I do not use floppies anymore for years already, however, my (oldish) testing rig still features a 5.25" floppy drive (where floppies were still floppy!) and a 3.5" one and I can clearly hear and see them being accessed during the "F6" message in setup, so, appararently, there must be some access check going on even though I do not press F6 (for the lack of floppies and the need for additional drivers).

I hence expect this to work just as muiz says:
Put the floppy in before setup commences and it should find them (why else the access?).

Also, this is not the access during POST, which I have disabled in the BIOS anyway...

Coming up next - useful links:
• If you like this project, please support it with your donation!      • Grab your HW info (HWIDs) here!     
• If you are a newbie, be sure to check out the DriverPacks tutorial!     • Here's how to create your own DP!

Sorry for such a delay, but I've been busy.

I'm confused. Method described by muiz never worked for me (e.g. I sometimes forgot to press F6 - in my previous job I installed Windows very often on many computers). Neither it works now. I've tried again with txtsetup.oem in main floppy directory and drivers in subdirectory (the way this driver is delivered) or with drivers in main directory. None of these variants works.

My winnt.sif is very similar:

[Data]
    MSDosInitiated="No"
    UnattendedInstall="Yes"
    AutomaticUpdates=1

[Unattended]
    UnattendMode=ReadOnly
    UnattendSwitch="No"
    WaitForReboot="No"
    OemSkipEula=Yes
    OemPreinstall="Yes"

I used to have UnattendSwitch="Yes", but I've changed it to No because I want setup to parse OOBEINFO.INI. With Yes it didn't work either without pressing F6.
Right now I'm using via drivers for testing, because that's the chipset i have. Maybe it depend's on the driver?...

Regards,
Chris

PS. What's the tag for code here?