Oleg_II

Anybody knows the script for taking INF files from say HFDRV folder and placing them renamed and CABed in SOURCESS\I386 folder? For example, if there are 3 INF files in HFDRV - 815.inf, ich3ide.inf, cdma.inf, they will be renamed and CABed into SOURCESS\I386 folder as hfdrv1.in_, hfdrv2.in_ and hfdrv3.inf. There are other files like SYS, BIN, EXE in HFDRV folder too. The names for the INF files may be random (different in each time).

FDV Since the fileset is not a beta now do you think it's time to start another topick for discussing next verion? It would be convinient to identify somehow the versions (for example, IE Removal Fileset after Decembe 23). I've already have suggestions for the next version

I'm trying to download the new installer. But from what I found on www.toymaker.info DLLs are not registered. This makes possible to use HFEXPERT folder only. By the way I found a posting on one forum that some of them may be useful for playing media files with MPC (?).

absolutely. it works primarily in conjunction with the protected files list in SFCFILES. i routinely do this on installs and it works perfectly. Sorry for asking this again but I'd like to confirm it one more time: are you replacing only one SFC.DLL? You don't replace SFCFILES.DLL, don't you? It's probably not exactly the service as a proccess running on the system. It's probably something like one time action under definit condition?

Way too many files, are they all needed?

My 2c redirect.inf Version] Signature=$CHICAGO$ [DefaultInstall] AddReg = Reg.Settings [Reg.Settings] HKCU,"Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders","Personal",0x00000,"D:\Docs" HKCU,"Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders","My Pictures",0x00000,"D:\Docs\Pix"

Pantner You can find a great script here.

Dave Not sure if it is possible for drive openning/closing but you can have a look in your regestry keys using my tweak for enabling sounds on receiving e-mails: [Version] Signature=$CHICAGO$ [DefaultInstall] AddReg = Reg.Tweaks [Reg.Tweaks] ; Sound on receiving e-mails HKCU,"AppEvents\Schemes\Apps\.Default\MailBeep\.current",,0x00000,"chimes.wav" There are some other events you can assign sounds to.

I read only about these DLLs: d3dx9_24.zip d3dx9_25.zip d3dx9_26.zip d3dx9_27.zip And it's obviously one new - d3dx9_28.zip Just one example (I saw a few more): Tomcat76 These files are not critical and can be HFSLIPed using HFEXPERT\WIN\SYSTEM32 folder without registering. But if registering there should be some more lines of the code

FDV Not exactly so The files under question are separete.

They are part of original now Not much benefit in fact. As Crash&Burn said these files are for newer games. Some games won't run without them and most install these files during games installation. There is a possibility that if the files are included in DirectX now they won't be included in newer games in future so one will need to obtain them anyway if wants to run these games. I have these files saved in Additions folder of my installation disk just in case because the files can be added in System32 without registering. I think DirectX binaries and their registration shouldn't change a lot so adding these files maybe is not difficult (for gamers sake only

azagahl Thank you very much! You confirmed it! So we have to ask TommyP to look at this new version

Sorry, my English I meant: when we use your fileset we disable Windows File Protection. We discussed once that after installation we can change SFC.DLL to the original (say from BartPe or with other methods) and it will re-enable Windows File Protection. Will it? And if we disable the cryptographic service through the Registry and even delete its files, will that influence re-enabling Windows File Protection when we chang SFC.DLL back to the original? Or Windows File Protection is something different and independant from the cryptographic service?

Could someone who downloaded the updated version check if this edition includes D3DX DLLs (Crash&Burn told us about them some day - d3dx9_24.dll - d3dx9_25.dll - d3dx9_26.dll - d3dx9_27.dll I heard that M$ included some D3DX files in the new download (it became more "heavy" in a few MB if you noticed).

I use FDV's fileset and can delete those CATs without worrying about IME's. As far as I understood with FDV's fileset CATs are not needed But some of them like NT5INF.CAT and NT5.CAT should be tested for removing B) Hmm... FDV Just a thought: if the cryptographic service is disabled we don't need its files? Or if we change SFC files later it could be enabled?

Bilou_Gateux When using FDV's files we already disable SFC. I have not tried removing all CATs, only removed 7 of this list and Windows 2k is working on VirtualPC and on a real computer. And I also removed some files from CORELIST.INF - I got only one error registering ODBC when I removed this component. So I think the cryptographic service is disabled with FDV's files. And then we can delete all (or most) CATs? FDV Please be carefull with IME files I don't know for sure but they may be needed by user input. PYIME is for Simplified Chinese PinYin input method. How it connected with IE? Don't know but I remember back when I was using Windows 98 I had to install third party software to unable Chinese characters input in documents. Then when IE5.5 (?) came out it became possible to specify Chinese Simplified input during upgrade and I could type Chinese characters in OE (don't remember about M$ Office at that time). Later a new M$ Office version came out and it has the ability to install IME too. But maybe it's safe to delete these IMEs from the source. Maybe it's related to the MUI or user interface. I think that PinYin input method is installed from PYIME.EX_ from SOURCE\i386\LANG\CHS folder. Should try it.

Don't think it would be a "big thread" because the method is only semi-automatic for those only who knows something about INFs and don't afraid of editing them. But it would be convinient to have one MYDRV.CAB with all drivers for the system. And for a few systems too - one CAB for systems with one type of hardware, other for the systems with different hardware. Just replace the files in the installation source and you are ready to go Or just make one CAB for a few types of configuration...

Good idea! But we are all a little busy I'll have a long hollidays at the end of January and may help with the site. And why placing to the Drivers Forum - let them know B) about HFSLIP of course

TommyP Just sent you a message about this. This method works! But it's not for every user because some INF editing is involved. I've just have a thought: we may have a small database about drivers - which are easy to edit and which are more complex. Or I think if there are more successfull installation it would be better to introduce this method in Drivers section?

I found this in Unattended Windows Discussion & Support > Device Drivers Bilou_Gateux: Very interesting information! So, if I want to delete CATs I should (better?) also delete CatalogFile entry in apropriate INF?

There is a very simple method of integrating your drivers into Windows source with HFSLIP. (Simple method of integrating SATA/RAID drivers could be found here.) First step: preparing driver binaries. All driver binaries should be in extracted format as if they are used for installation through OEM folder structure or like in Bashrat the Sneaky's drivers packs. Most drivers that come in one EXE file could be extracted with archievers like WinRar. Or you can use Universal Extractor. For finding right files among all extracted binaries and getting rid of some garbage I recommend using simple and great tool - Driver Compressor (but you have to extract cabbed files again after using it). Second step: creating folders structure. Create folder HFEXPERT in HFSLIP directory, go inside this folder and create the folder DRIVERCAB. Place all your extracted driver files into DRIVERCAB (for later updates it's better to place drivers in separate subfolders like DRIVECAB\Modem, DRIVECAB\Sound, DRIVECAB\Video, etc.). Comment: What happens if there are files with the same names? You can rename them. I even advise you to rename INF according to the driver type: MYMODEM.INF, MYSOUND.INF, MYVIDEO.INF, etc. But if you rename other files from the packages you should try to rename all entries refferencing this file in an appropriate installation INF. This can be usefull for troubleshouting later problems with replacing some files with doublicated names in DRIVER.CAB too. Third step: editing INF files. We came to the most difficult part as it needs some manuall work. You have to open each INF in DRIVERCAB folder and search for the section [sourceDisksNames] or [sourceDisksNames.x86] and inseart right after it and before any line this code: [SourceDisksNames.x86] 1 = %W2Kcd%,driver.cab,,"I386" (For troubleshouting purposes I'd recommend change %W2Kcd% to drivers nature like VIDEO, SOUND, MODEM - in this case if any error occure you can see clearly which driver has a problem.) Search for the section [sourceDisksFiles] and make sure all entries have '= 1' in it like: [SourceDisksFiles] file1.sys=1 file2.dll=1 Comment: Some INF has a few SourceDisksFiles sections and you have to change them all or add all files to the one section with '= 1' part. I confirm this method works with Windows 2000 Professional and FDV's fileset (maybe it needs Windows Files Protection Mode off) for a least a douzen drivers I used. I have not tried to follow it on other OS and without FDV's modified DLL yet. If you tryed this method with other OS and without WFP off please let us know your results. Issues I had with this method (IMHO all is about of not "well-formed" installation INF files): - Intel graphic driver asks for distribution CD but installs fine without providing it. - My CDMA driver doesn't install (asks for CD too).

FDV Have you updated the fileset on your site? I'd like to reinstall my system this week and only wainting for releaze Or I can use the last beta? You want change anything? I reported an error with copying MRU_KILL.EXE (had to change entries in TXTSETUP.SIF), is it only my problem?

FDV 'Show desktop' works Let this blue "e" goes! But I had to change from mru_kill.exe = 1,,,,,,,,3,3;new to mru_kill.exe = 1,,,,,,,2,0,0

Tomcat76 No problem. It's just another way of installing it B) As far as I know when you install it from the Web there is flash.cab or something like this in IE cache. Maybe it can be somehow deleted. In described case I install it directly to the system without this CAB stage. I can't get how it happens to uninstall it if it is in your SYSTEM32 folder and registered already Doesn't it the same when you install it through an installer? And I don't have IE on my computer - I just associate FLASH files with a flash player

Sorry gents if I'm talking about something different (Flash 7.0.19.0 is here) but some time ago we discussed how to include Windows ASPI driver into installation. Why not to try including Flash in that manner - through HFEXPERT folder The only file you need is FLASH.OCX (I'm talking about Flash 7 but I think it should be nearly the same even if there are a few files needed for Flash 8). Place the file into HFEXPERT\WIN\SYSTEM32. Create FLASH.INF file and place it into HFSVPK: [Version] Signature=$CHICAGO$ [DefaultInstall] AddReg=Filter.Reg [Filter.Reg] HKLM,"Software\Microsoft\Windows\CurrentVersion\RunOnce\Setup","Flash.ocx",,"%11%\regsvr32 /s %11%\flash.ocx" You are done You should only find out what files are really needed for Flash 8 and if FLASH.INF should be customized a bit according to the new version (maybe added some settings). And if you want you can create a switchless installer with IEXPRESS.EXE (included in Windows