Oleg_II

As I said some time leaving the file in the source causing a lot of entries in the regestry that are not needed. But finding which file and regestry entry are only needed for your program to run is difficult and time consumming.

The application WebCraft (used to write HTML code for websites) needs HTML rendering from IE. I found that it needs MSHTML.DLL and only one line in regestry and it will work. It appears that this DLL is also needed for openning CHM files. But if I just add MSHTML.DLL into i386 folder on installation disk it writes quite a few lines in regestry and these entries are obsolete. Something is calling for this DLL during installation. I combined 4 files and 4 entries for regestry into one package so that it installs as a separate application. My application works, I can open CHM files (some bugs are still happen with it) and obsolete entries are not added into the regestry. Here is the installing INF file for this package with names of all needed files: Later I also found that MSN Messanger needs WINHTTP.DLL just placed in its folder without registering in order to work. One more application Xenu Link Sleath (checks website links) also needs something from IE core. I have not investigated it yet but it probably needs some regestry entries.

TAiN Thank you for notice. There is some information in STORAGE.INI concerning VMWare drivers: So I think it's covered and should work with current HFSLIP beta.I don't have VMWare so can't test. If somebody can check it it would be great.

Unfortunately only passwords are not stored. Anyway I use rasdial command in a batch file where I have stored username and password:rasdial "myconnection" "username" "password" Does this work? Somebody tried it to set username and password? I found that freeware utility NIRCMD can do similar things (and much more).

worldy You are right: if NTLDR is missing you won't have booting choice. If you don't want to depend on NTLDR you will need to learn about boot managers and use them. I don't like them so in this situation I'll load from recovery CD or a DOS floppy and either fix or just restore the partition. That's the limitation. But using boot managers that write into MBR also won't guarantee against corruption (and may cause other difficulties in future too). That is probably the reason why laptop manufactorers not only install recovery partition but provide a set of recovery CD. Minimum set of files you need to use this method: - pqvf.vfd - a floppy disk image with DeployCenter (could be 1.4 or 2.8MB image), created when installing DeployCenter on Windows (it's basically a DOS disk with DeployCenter executable and a couple of helpers); - VFINSTNT.EXE - VBE Installer for Windows NT/2000 (inside installation folder). - VFLOPPY.SYS - VBE First phase loader (inside installation folder). - VFLPPYLD.SYS - VBE Second phase loader and disk I/O redirector (inside installation folder). All four files go in one folder anywhere on your computer (I place it in %PROGRAMFILES%). That's for running from Windows. You also need a special MBR copy and edit BOOT.INI as I described before if you want to use the menu during startup. Use pqvf.vfd as a boot image also to create your recovery CD. Download DeployToolkit_manual.pdf for instructions and samples of scripts if you want to automate restoration progress ("press one button and completely restore" solution). For copying MBR I use the same tools as jaclaz posted: MBRFIX and MBRWizard (there is a Windows GUI working for booth tools at the same time, don't remember where I got it but I see a lot of links with jaclaz's name about some GUI Loading from boot floppy or CD with DeployCenter you can make bootable other primary partition. That is why I like this program - it can help in different situations PS There is one way not to depend on NTLDR but your computer will boot twice before you enter the system. The solution is not too elegant but anyway: place a CMD file into "All Users\Start Menu\Programs\Startup" that will instruct VFINSTNT.EXE to run without immediate reboot (run recovery process next boot). This file will be executed each time you enter the system and each time you boot you will boot into recovery process image first, cancell it and reboot into system.

There are different ways to do it. I prefer HFSLIP.

Kiki Burgh Thanx! Just like to know if the hotfix is extracted and integrated as separate files or ran as an EXE file

Tomcat76 Maybe a bit off topic. I can't run HFSLIP right now (I'm far from my computer now). Just wonder if it supports KB888111.EXE integration? And in which manner: slipping files into sourse or running through SVCPACK.INF?

Innocent Devil Well, yes. At least you need some place to save your images. But if you use the method I described with Virtual Floppy Evironment you don't need a primary partion, you can save your images on any partition within extended one. And if you use it on your own computer like I do you don't even need to make this partion hidden. Just create a folder say "Restore" for images and use the rest of the place as you wish

Yeah... It took me about 3 hours to make it. I tried correcting the old STORAGE.INI but found that's easier to take info from INF files (as you suggested). And I'm not done with NVIDIA drivers yet.And I make it in sections for different manufactorers - hope it would be easier to update that way. That would be nice but it take too much time. I'll check it when I have time. If somebody could help New database file is ready. Please test it with the latest beta of HFSLIP. If your hardware is not listed please let me know and I add it into the database. If somebody is willing to continue updating and support the database please also let me know. I'm done with this untill I have some more time to check BTS driver packs and a computer with such hardware. Hope it will be before this year Christmas PS Want to know your opinion: is it better to have one big file STORAGE.INI or make it as a few smaller ones like STORAGE_INTEL.INI, STORAGE_SIS.INI, STORAGE_VIA.INI, etc.?

worldy 1. I'd recommend DeployCenter over Ghost (I like it pursonally and the instructions for running from Windows is for DeployCenter, it will be different for Ghost). But in DOS booting functionality is nearly the same. You choose. 2. For the purposes you specified it's better to use something like WinPE, BartPE, WinBuilder - there is a separate Forum for that. And there are instructions how to automate all operations you asked for: partitioning and installing Windows from these boot CD (that includes installing recovery partion too). As for using DeployCenter for this purpose (partitioning and formatting) I can give you these two tips: Tip 1: You can make simple customized script that partitions a new hard drive into one primary partiton and one extended with a few logical on it. It's complitelly automatic. Remember I said that DeployCenter has some functionality of PartitionMagic? But I'm not sure Ghost can do this. Tip 2: - first make three partitions of needed size with needed formatting and file systems on a hard disk; - make ONE! image of ALL THREE just made partitions to CD with imaging software like DeployCenter or Ghost with high compression; - when you buy a new disk (doesn't metter how big it is) just restore your empty partitions image on it - it will take seconds and then you'll get three partitions already formatted and ready to go and probably some undefined space on hard disk that you will aquire later from installed Windows. 3. I can run recovery process not only ckicking the shortcut in Start menu but choosing in booting menu. If Windows doesn't boot it will probably at least show booting menu and you can run recovering operations from it choosing "Recover my System" item (remember my instructions about editing BOOT.INI and saving MBR in a file on system disk?). Or you will have to boot from a rescue floppy disk or CD that is better to prepare in advance with your imaging software on it.

Tomcat76 Go ahead!

glentium Perfect! Marvelous! So some work with STORAGE.INI is needed... OK! I'll correct these mistakes.

In general it's nearly the same. I've just tried WinBuilder (something like BartPE) and it can include support for SATA/RAID drivers including only SYS files and editing TXTSETUP.SIF.

glentium That would be nice. By the way what did you do with other files (not SYS) when slipstreamming the drivers manually?

Not argueing, just my opinion. I have a few partitions: one primary with my system and three logical on extended partition. My system and my data are on different partions. And I don't care about losing system as soon as I can restore it with nearly all programs and settings from a prepared image in 5 minutes or install it again with Unattended in only 30 minutes In fact I often restore the system partition from "ideal" image on purpose just to be sure there is no viruses and broken things on my system. As I said it takes only 5 minutes with DeployCenter from clicking on the shortcut in Start menu to reloading in restored Windows. It doesn't hurt because all personal data and even most program settings are on the other partition. Nothing changes, only the system is renewed/revived again. (I don't even install antivirus software because of this but it's my personal opinion too.) And of course I make regular backups of my sensitive data to CD or CD-RW using DeployCenter too: I make the image of the entire second partition with all my documents and photoes directly to CD. It takes a bit longer with high compression and image verification options enabled but not more then 15 minutes for 2Gb of data (documents, photoes, archieves). I don't use Windows versions of DeployCenter and PartitionMagic (and I rarelly use PM at all). Both create boot floppy disks that can be used in VFE or from multiboot CD. So there is no MBR changes I'm not aware of. I admit that VFE change my MBR but only when I run it and this is a temporary change because it backups MBR before running and restores from backup after running (you can watch it yourself). And VFE is not installed in the system - no settings in Registry, no files in system folders, only a few files are placed anywhere on hard drive and a shortcut in the menu. PS I aslo have a few different images with different Windows: Windows 98SE, Windows 2000 Professional "standard" (with IE and stuff) and W2k HFSLIPed and reduced. Not more then 5 minutes, no phisical boot disks involved and I'm in the OS of my choice Well, a boot disk image with imaging software is involved in fact And I forgot to mention that I use NTFS on all partitions as this file system is stable and reliable in my opinion.

Camarade_Tux No, of course it's better not to test on the work computers Tomcat76 Thank you! PS Probably I have to buy one motherboard that needs installing SATA drivers (can't afford to buy more then one right now). Have other hardware including a couple of SATA drives (can use it untill the end of October, this computer doesn't need drivers because it maps SATA as IDE drive during installation), probably will need only a CPU in addition to the motherboard. Any advice of some sofisticated model with difficult drivers? Just for testing don't need a new computer.

Interesting It sounds like making some WINNT.SIF work. Does it mean I can include all tweaks from my INSTALL.INF that is ran say with CMDLINES.TXT in HIVEFIX.INF and they will install the same way? Will it work in W2k? What are the modifiers? Can you give an example?

Tomcat76 It's =1,,,,,,3_,4,1,,,1,4 for all files according to scankurban. It's = 1,,,,,,4_,4,1,,,1,4 for SYS files in TommyP's example. It's = 1,,,,,,_x,4,1 in Anderz's example (he made it uncompressed but according to others it's not necessery). Two more tutorials (including MSFN's one) state = 1,,,,,,3_,4,1 for SYS files. Too many choices. Now I'm thinking of what: maybe you are right just placing them into i386 but don't add into TXTSETUP.SIF and DOSNET.INF - when installing drivers Windows will search for them in i386 folder on CD too. But anyway if you don't mind let it be =1,,,,,,3_,4,1,,,1,4 for now. If something goes wrong after testing it's simple to change the string Camarade_Tux You mean you can not install your RAID driver using this method?

Tomcat76 Disturbing you again I replied you in test version topic about it: Maybe other files needed in TXTSETUP.SIF and DOTNET.SIF too. It's better to mentions them too only under [sourceDisksFiles] section. Only TXTSETUP.OEM is definetelly not needed. TAiN Thanx for trying to help No problem, it should work in theory as it works when doing it manually according to reports (I specified the link on such topic in Unattended Drivers Forum). We just need to create full STORAGE*.INI files and find out which files are needed and which can be omitted.

Maybe I understand it wrongly but Grub4dos can't work on NTFS partitions? Or have some bugs? I read on Chinese blog that NTFS support is going to be dropped because of bugs. Replacement MBR utilities work one way - they replace MBR once and forewer and are just boot managers. They also can't be used to run image or an EXE on NTFS file system too. Info from 911cd Forum is very interesting. Maybe usefull for me. The only issue that most programs there are Win32 and how to use them if there is no ready LiveCD nearby? Unfortuanatelly I can't open some links but I'll definitelly do.

jaclaz Thanx! That is very interesting info. I have not visited all links but Grub4dos seems to do the same thing as I suggested with VFE at boot time: chainloading by the normal NTLDR. But I have one more method of running VFE Well, it's probably covered by replacement MBR utilities - when running under Windows VFE tmporary replaces normal MBR with its own. I won't describe one more method using this as it'll be a bit difficult too I agree that free software is good and I like using it (and using it a lot). Unfortunatelly I have not found the right utility for this purpose. Frankly speaking I don't like Ghost either But I like DeployCenter (it was called DriveImage and ImageCenter too)

No the order of sections is not important. It's fine now. I'm not sure about SYS files only. I think only SYS are refferenced in section SCSI.load of TXTSETUP.SIF. And I see some other files in packages: DLL, EXE, CPL, TAG, VXD and PDB. CAT and INF files are not refferenced in scankurban's version. I think it's not important right now.

Tomcat76 Don't be angy with me As I said I'm illiterate in coding Just want to be sure that all four parts are in their places in order it works: [SourceDisksFiles] viapdsk.sys = 1,,,,,,4_,4,1,,,1,4 viamraid.sys = 1,,,,,,4_,4,1,,,1,4 [HardwareIdsDatabase] PCI\VEN_1106&DEV_3249 = "viamraid" PCI\VEN_1106&DEV_3149 = "viamraid" PCI\VEN_1106&DEV_3164 = "viamraid" PCI\VEN_1106&DEV_4149 = "viapdsk" [SCSI.load] viamraid = viamraid.sys,4 viapdsk = viapdsk.sys,4 [SCSI] viapdsk = "VIA ATA/ATAPI Host Controller" viamraid = "VIA SATA RAID Controller" 1. SourceDisksFiles - only SYS files from STORAGE folder should be mentioned if I'm not mistaken. 2. HardwareIdsDatabase - taken from STORAGE.INI 3. SCSI.load - first part of a *.SYS file = *.SYS file,4 4. SCSI - taken from STORAGE.INI too. If it is possible please add the possibility to add information from different STORAGE*.INI - it could be easier to support separate files for different manufactorers. And there is probably some garbage that are not needed to be compressed and placed in i386 too like TXTSETUP.OEM and maybe some other files. We can find it out only in the process of testing PS I've just thought I can create STORAGE folder with STORAGE.INI and any files, run HFSLIP and see the result

Tomcat76 I've just had a look into HFSLIP HFSTOR section. Here is my suggestions: 1. I think it's better to place STORAGE.INI in HFTOOLS and run :HFSTOR section if only *.SYS file in STORAGE folder. Because this way a user may place this INI is in HFTOOLS just for future use and doesn't use any SATA/RAID drivers at the moment. 2. Sorry I'm not too much in the coding but I see only three sections are adding to TXTSETUP.SIF - SCSILOAD, SourceDisksFiles and HardwareIdsDatabase. Shouldn't be one more - SCSI.Load? Example: [SCSI.Load] 3waredrv= 3waredrv.sys,4 a320raid= a320raid.sys,4 fasttrak= fasttrak.sys,4 iastor= iastor.sys,4 nvraid= nvraid.sys,4 s150sx8= s150sx8.sys,4 sisraid= sisraid.sys,4 sisraid1= sisraid1.sys,4 sisraid2= sisraid2.sys,4 ulsata= ulsata.sys,4 ulsata2= ulsata2.sys,4 ultra= ultra.sys,4 viamraid= viamraid.sys,4 viapdsk= viapdsk.sys,4 The difficulty here is that first part iastor should be the name of SYS file iastor.sys without this SYS. Or do you think that it's better to include SCSI.Load part in STORAGE.INI too?