gosh

Forgotten Setup Secrets Revealed

36 posts in this topic

hi newbie here, what do you do with the Entries_BootDriv's_.ini file?

The .bat file i just double click but .ini?

Thanks

I'm using nlite

0

Share this post


Link to post
Share on other sites
Now if only I could adapt this setupldr.bin to change the hal on a syspreped machine!

You can script the HAL change using RunOnce...

edit: I posted how to do it before, but can't remember the tool I used, and the search here sucks. I'll look around though if you're interested.

edit2: You can hot swap the HAL with devcon: http://msdn2.microsoft.com/en-us/library/m...60-aaeb017e5fc7

Edited by fly
0

Share this post


Link to post
Share on other sites

Hi there

I've tried part 2 and it doesn't work at all, it just says file missing e.g. rr174xp.sys missing, when i take a look in my backup folder i find rr174xp.sy_ and when I expand the file the new file is named rr174x.sys... I've removed rr174xp.sy_ frem my I386 folder as the guide says but it cant figure out that I've already expanded the files for it :S

Kalle

0

Share this post


Link to post
Share on other sites

Whoa! Editing the TXTSETUP.SIF file looks like it can get the install go on way faster, because one can really disable the many unnecessary stuff there. I have few questions, tough. First at all - then the TXTSETUP.SIF file are excessive number of empty lines. Must they have been preserved? I dubt that, but I better ask first :)

Second, there is could of things that I want to know what they are and if I can ",noload" them. The SCSI stuff is self-explainatory (tough I have still one minor question, will the Deamon tools work then to emulate CDroms? Because it work as emulating them as being the SCSI ones...) but how about this?

[busExtenders.Load]

pcmcia = pcmcia.sys

If I did not have any PCMCIA slot on my machine and on most PCs, I should ",noload" it, right?

[files.i8042]

i8042prt.sys,4

What is this?

[files.sermouse]

sermouse.sys,4

Is that a support for serial mouse, eg. mouse connected to COM port?

[scsiClass.Load]

cdrom = cdrom.sys

disk = disk.sys

floppy = sfloppy.sys,,noload

ramdisk = ramdisk.sys

SCSI floppy is already disabled, disabling the disk if not having any SCSI card will be good too, right? And disabling the cdrom only when I never need the Deamon tools to emulate one, right? And the ramdisk is what? SCSI ramdisk? Is that really necessary to have?

[inputDevicesSupport.Load]

serial = serial.sys

serenum = serenum.sys

Is not that again the serial mouse?

[files.ohci1394]

ohci1394.sys,4

1394bus.sys,4

The 1394 bus is already disabled above (ohci1394 = ohci1394.sys,,noload) - but will it be good to disable loading this files also?

[files.sbp2port]

sbp2port.sys,4

What is this? Soundblater port or what the...?!

[files.lbrtfdc]

lbrtfdc.sys,4

I have no idea what is this either.

[files.vga]

vga.sys,4

framebuf.dll,2

vga.dll,2

vga256.dll,2

vga64k.dll,2

Do are all those VGA files really necessary? Aren't the vga.dll, vga256.dll and vga64.dll just same versions of the file for different VGa capable cards and witch one is used on normal modern hardware? Then the rest could be discarded?

Anyone can help me out?

Edited by caps_buster
0

Share this post


Link to post
Share on other sites

Well, this is not "question time". ;)

Empty lines in txtsetup.sif can be removed allright.

i8042 is the "right " name for PS/2 keyboard and mouse bus:

http://www.file.net/process/i8042prt.sys.html

More generally, try searching in Google for the driver name alone or together with TXTSETUP.SIF and you'll probably find all the info you need.

Don't assume that anything is "properly" named.

IDE and ATA/SATA devices use disk.sys or cdrom.sys as well

serial.sys/serenum.sys are about the serial PORT(s) not mouse.

1394 (read "firewire") is NOT i8042.

You must read a lot of things besides this thread in order to be able to identify properly system files, their use, the need or lack of need for them.

The SMALLEST possible TXTSETUP.SIF you will ever find (used in a MicroPE project) is here:

http://www.911cd.net/forums//index.php?showtopic=17807

your mileage may vary.

jaclaz

0

Share this post


Link to post
Share on other sites

FWIW, the fastest install that can take place will be achieved by:

installing Unknown Device Identifier

running it to get ALL of your hardware device strings

opening TXTSETUP.INF

scrolling to [HardwareIdsDatabase]

put in all of your device strings, edit the driver files accordingly

Open SYSSETUP.INF

scroll to [DeviceInfsToInstall]

remove INFs for devices you don't have. for example:

mchgr.inf (media changer -- trust me, you don't have one)

1394.inf -- Firewire

tape.inf -- tape drivers

netirsir.inf -- Infrared devices

pcmcia.inf -- laptops only

battery.inf -- laptops only

etc etc etc etc etc etc

here are the devices from win2k's TXTSETUP that the WinXP TXTSETUP does not have. in other words, support for these was removed from xp... this probably means that it would be very rare for you to encounter any of these:

cpqfws2e = cpqfws2e.sys,4 ; XP doesn't have

cpqarray = cpqarray.sys,4 ; XP doesn't have

cpqarry2 = cpqarry2.sys,4 ; XP doesn't have

ncrc710 = ncrc710.sys,4 ; XP doesn't have

buslogic = buslogic.sys,4 ; XP doesn't have

flashpnt = flashpnt.sys,4 ; XP doesn't have

lp6nds35 = lp6nds35.sys,4 ; XP doesn't have

ql2100 = ql2100.sys,4 ; XP doesn't have

cpqfcalm = cpqfcalm.sys,4 ; XP doesn't have

fireport = fireport.sys,4 ; XP doesn't have

fd16_700 = fd16_700.sys,4 ; XP doesn't have

tffsport = tffsport.sys,4 ; XP doesn't have

so you could comment them all out.

editing empty lines will not gain you any speed.

much may be learned by analyzing my files.

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.