Oleg_II

Would try

Unfortunately I don't know how to put a shortcut to the Control Panel if not with a CPL file. And I meant could you give me a link to the DIRMS_GUI.EXE?

Well, I can't think of anything else that could influence HFSLIP running If you can make an ISO from the files you just copy to the hard disk everything should be OK. Your installation files also seems to be OK. What I'd do in this situation? It maybe not clever but I'd delete previous HFSLIP folder (leave only HFTOOLS contents) and started from a scratch Creat a folder place the latest HFSLIP*.CMD, run for the first time, copy I386 and markup files from the disk to SOURCE folder and try again. If it doesn' work try to create ISO from SOURCE again. If it works but doesn't only work with HFSLIP, try integrate SP2 and do the same process again. A long way but something is going wrong. You have an original CD with XP or it is some kind of OEM?

Link to the gui for DIRMS?

Yes, of course. You can just delete files after installation in SYSTEM32 folder (the problem could be only if you add a DLL and register with that INF file - in this case you have to unregister it first). If you want to remove files from SOURCESS before the installation you'd better remove their entries in LAYOUT.INF and TXTSETUP.SIF or you will have errors about missing files during install. You are right - EXE files go to HFEXPERT\WIN\SYSTEM32 and INF files go to HFSVPK. Please remember that we are talking about EXE files that run without installation. Those could be commandline tools and some little usefull appz.

Can you open these files? Are they all readable?

Flame12121 First question: have you compared the quantity of files in I386 on CD and on hard drive by right click as I described? What folders do you have inside HFSLIP folder? Is there HFCLEANUP folder? Find in SOURCESS (resulting) folder the following files: LAYOUT.INF, SYSOC.INF, SYSSETUP.INF and TXTSETUP.SIF. open them with any archivator like WinRar or WinZip. Any empy files among them?

Squeeto Very interesting! Thanks! But are you sure I never figured that

-I- Don't quite get you - this is a line from the latest set: 53,"Application Data\Microsoft\Internet Explorer\Quick Launch" 53 - User profile directory (%USERPROFILE%)

So I removed all CAT files from SYSSETUP.INF but NT5INF.CAT - if I remove this one the installation complains that it can't find refferenced in SETUPAPI.DLL CAT file signed for OS binaries (?). Unfortunatelly I have not wrote down this but will in a couple of hours. It means that catalogues are still installed with FDV's fileset. Anybody can confirm about this CAT file in nLite? Does it install?

Why not? You can even stay with IE if you want As I said - it could be about 100MB or even less (I don't want to remove speach component and hardware support). By the way, could you please check if nLite removes all CAT files?

OK. You can just search for 'sound schemes' in Google and find a good program if you wish. I saw one or two before. You can navigate to the registry key I specified by: 1. Click on Start button. 2. Click on Run... 3. Type 'regedit' and press enter. 4. Select Edit from the menu. 5. Select Find... 6. Enter 'Schemes' and confirm OK. 7. Navigate to the key. But if you unaware of regestry editing it could be dangerous for you because some changes to the regestry may lead to the computer not working right on not working at all. Don't take it personally but maybe it would be safe to find a program for defining sound schemes. You could go back to registry editing after you 'play' with computer lot enough

It could be the problem. Try doing what: 1. Click twice on my computer. 2. Go Tools > Folder Options... > View. 3. Check "Show hidden files and folders". 4. Click Apply and then OK. 5. Insert your XP into CD drive and navigate to the CD contents. 6. There should be I386 folder on CD. Right click on it and select Properties. 7. Wright down how many files Contains in this folder. 8. Create a folder on your hard disk and name it SOURCE. Open it. 9. Copy from CD folder I386 into SOURCE folder. 10. Right click on just copied I386 folder on your hard drive. How many files it shows? Is the number the same as in step 7? 11. If number is the same, copy your mark files (WIN51, WIN51IP, WIN51IP.sp2) from CD into SOURCE folder too and try to install again. Will it give you any error again?

TommyP Maybe wait for some time before putting this tweak in HFSLIP? It's working good now. Let people test it first. Maybe M$ comes with some explanations by that time.

FDV Do you think W2k3 will be as fast and light as W2k? I have an iso that was freely redistributed by M$. It looks like W2k as far as I remember. And if you think it's worth and may be compared with W2k I can buy it (I'll probably need a few licences if it's good). Have you had a look at that new M$ OS (Vista)? If it's good maybe start learning it and be ready before it comes out Just ask your opinion because I have not tried it. It seems more like XP though. E-mail is sent PS This one should work: [mru_killer] Name ="MRU Eraser" CmdLine =11,,"rundll32.exe setupapi.dll,InstallHinfSection DefaultInstall 128 %SYSTEMROOT%\system32\mru_kill.inf" SubDir ="Startup" IconPath =11,,shell32.dll IconIndex = -200 InfoTip ="Deletes Most Recently Used items and empties data collection Reg keys."

FDV Since you don't create a new thread for the next version I have to post here You asked once about making MRU_KILL.EXE smaller. Why not leave it INF file? It's only 1.59KB And could be easy edited too. I've just tried it - put MRU_KILL.INF in System32, created the shortcut and change Target in link shortcut propeties like this: %SYSTEMROOT%\system32\rundll32.exe setupapi.dll,InstallHinfSection DefaultInstall 128 %SYSTEMROOT%\system32\mru_kill.inf It seems to be working. Now this code should be inserted into SHELL.INF. Will try.

By the way, a small tip on Virtual PC images: Run Virtual PC and create a new PC for installing Windows XP and allocate enough memory for it (I have 512MB on test computer and allocate 256MB for a virtual system). Then turn off Virtual PC and copy the new image somewhere on other disk. Thus you can save a lot of time for testing - if something is going wrong just: - turn Virtual PC down; - delete used image; - copy one from the safe location; - start Virtual PC again.

Hmm... You have everything to run the installation. Next time trying please write down which file is missing. Could you try copy your XP on hard disk, create an image with it and install on Virtual PC without slipstreaming? (create a new PC image in Virtual PC also). You don't need to install it complitely just look if there are any errors before it starts installing drivers. It is for verifying that your original XP disk has no errors, missing files and also that Virtual PC works.

Since it formats and then gives you an error the boot image should be fine. Could you check if there are a few files named something like 'cdrom_nt.5' in SOURCESS folder after running HFSLIP (these names are from W2k, so yours should be different, just look alike)?

Why don't you use DOS version of PM? All files needed can be placed on one 1.4 MB floppy I run a few floppy images from multiboot CD and it's very convinient.

Have a question about Explorer patching. Here is the method of patching Windows Explorer so that 256 colors icon could be available in the tray. Is it worth using? Does it have some side effects?

I had a similar problem with HFSLIP removing components on Windows 2k (kinda alternative nLite May be you deleted some files for cam support. I also found that some driver for new devices need files from DRIVER.CAB that maybe even seems to be for other hardware (my BenQ scanner needs some Toshiba file from DRIVER.CAB?). I solved my problem with commenting from deleting ICAM3.INF and files in it (two or tree files in DRIVER.CAB if I'm not mistaken). It's usb cam here. And for my scanner I commented that Toshiba file in DriverScanners reducer. Or if your cam installation can't find some file you can unpack DRIVER.CAB somewhere and direct search for missing files in that folder.

1. Install any sound scheme or define sound to the events manually through Control Panel. 2. Export this register key HKEY_CURRENT_USER\AppEvents\Schemes\Apps 3. Explore PS I have not tried it but you can download some programs for advanced sound schemes and then explore your registry too. Maybe you can find according values for openning/closing drives

Thanks TommyP Do you think it is worth including in HFSLIP? It's drivers integration part. I though that renaming INF files will be safe for reducing source and you can include this in any part of the script (before or after reducing) PS I forgot, with CABing HFDRV folder source in one HFDRV.CAB and including its entries into DOSNET.INF, LAYOUT.INF and TXTSETUP.SIF too (I suggested the code here.

Tomcat76 That's already something, thanks! for %%i in (HFDRV\*.inf) do makecab /D CompressionType=LZX /D CompressionMemory=21 /L SOURCESS\I386 %%i Two more parts needed: 1. Renaming INF files according to the scheme - hfdrv1.inf, hfdrv2.inf, etc. 2. Inserting HFDRV*.INF to DOSNET.INF, LAYOUT.INF and TXTSETUP.INF.