Tomcat76

That did the trick. I was using 51115. Thanks.

I executed cdimage /? to see the switches available. My concern with -j1 was the last part of its description: "but some of the filenames in the ISO-9660 name space might be changed to comply with DOS 8.3 and/or ISO-9660 naming restrictions." The ones for -j2 and -n seemed "harmless" to me: -j2: encode Juliet Unicode filenames without standard ISO-9660 names -n: allow long filenames (longer than DOS 8.3 names) DirectX 9 comes with a file called "mpeg2data.ax"....

Thanks for the reply. That's what I tried first but it's not integrated. I see that your batch file is trying to find a few files inside it, but fails to find the right one because it's not looking inside the update\ folder. I found this a bit strange because it seems like a regular hotfix-type update to me.There are no traces of it in the SOURCESS folder after HFSLIP has run. It's an optional program that'll not turn into a recommended update until everybody owns a Microsoft Multimedia House. I'm going to try a silent installation from HFSVPK next time.

BAT2EXEC and C2E can't handle my batch files (too complex?) but maybe it'll work for xtremee.

Well... It works. I'd like to know how to get the SID (domain) through a batch file too. The full string always starts with "S-1-5-21-" and always ends in "-500".

I've put it here for now: http://users.telenet.be/clients/tc76/win/ There's a 7z, a RAR and a ZIP version. Take the smallest one you can handle.

/integrate works for me, though it overwrites svcpack.inf.

It's a known issue. Some virus makers used Quick Batch File Compiler to wrap their "applications", and quite a few anti-virus companies blame the wrapper as a result (whether that's because they're too lazy to check better or because they can't check better I'm leaving in the middle). The maker of QBFC doesn't get much response from the anti-virus companies; see this thread on their user forums: http://www.abyssmedia.com/cgi-bin/iconboar...act=ST;f=9;t=35. On October 27th, 2005, Grisoft wrote back saying that they'd remove these checks from the detection rules. Yeah, right...I've been using AVG for more than a year myself, starting from when it was supposedly "the best" free anti-virus out there, and I continued to use it when Avast took over from them. I'm seriously considering going back to Avast (which I used before AVG) because of all these "false positives".

As far as I know, you can only change the name of the Administrator account and its folder through an unattended installation of Windows. You can change the name as many times as you like when in Windows, but the folder will always be named what was defined during installation.

I've been reading around a bit, and people seem to recommend to use the -j1 switch with cdimage.exe when creating a bootable ISO for a Windows installation CD. But wouldn't this cause problems when integrating DX9 into Windows 2000 with HFSLIP? Wouldn't -j2 or even -n be a better solution given the Win2K-with-DX9 installation cannot be performed successfully from DOS anyway? I could test this myself but I'm a little short on time. Has anyone experimented with this before?

@natan770: Thanks for the reply. That sounds good. Concering the NTFS partitioning... I should've mentioned this in regard with the partitioning, but I forgot: also of importance to me is the drive letters. Since this is Linux, will the Windows installation CDs (2K and XP) receive pre-defined drive letters or will they still have to assign their own? This is what my system drive looks like: C:- 20GB, primary, NTFS D:- 20GB, primary, NTFS E:- 20GB, primary, NTFS F:- 14.5GB, primary, FAT32 LBA The opticals are G and H, and the data drives I, J, K and L. Whenever a system re-install is needed, I do this: 1) Disconnect the data drives 2) Boot with a Win95 floppy (custom version without CD support) and start Norton Disk Editor to kill the system drive for roughly 15 minutes 3) Reboot with Win95 floppy (custom), start EFDISK.EXE (from MasterBooter) and create the four primary partitions but in FAT32 LBA 4) Reboot with Win95 floppy (custom) and format each partition one by one. They are now C:, D:, E: and F:. 5) Reboot and start installation of Win2K onto the C: drive, formatting it as NTFS. 6) When Win2K and all drivers are installed, reconnect the data drives; they're automatically assigned the requested drive letters. 7) Much later: disconnect the data drives and start installation of WinXP onto the D: drive, quick-formatting it as NTFS. I don't like the idea too much of changing drive letters post-installation, if that wasn't obvious...

Hey... You're advertising this as a Ghost replacement but I was a bit surprised when I read the features (and the additional features mentioned on your site), so I have a few questions.... 1) Does it support local HDD to local HDD cloning (what I'm using Ghost for 99.99% of the time) and local partition to local partition? 2) "Partition and Format a disk before installing Windows"... Can it partition and format both NTFS 5.0 and NTFS 5.1? The formatting is necessary to have correct drive letters from the start, otherwise I need to pre-format in FAT32 LBA and reformat during Windows installation (as I'm doing now).

If this has been covered before, please tell me what I need to search for because I couldn't find anything relevant. I have a few questions... 1a) Is RunDll32 already accessible during the SVCPACK portion of Windows setup? 1b) When removing two Windows components through RunDll32 on an existing installation of Windows (not tested during Windows setup), they are still marked as installed in Add/Remove Windows Components. What needs to be done to make Add/Remove Windows Components reflect the changes? 2) Is HKEY_CURRENT_USER accessible from SVCPACK? 3a) Is it possible to edit the HKCU registry for user accounts that still need to be created? 3b) Among other things, a value needs to be removed from Run; would the "pre-edit" (3a) take effect quickly enough for the program to not start before its entry is removed from Run? The idea is to remove Windows Messenger, install MSN Messenger, remove the "this program is still running" balloon, remove the balloon to create a Passport account, and to stop MSN Messenger from automatically starting when a user logs on. This is what I got so far. StartX.exe /wait "RunDll32 advpack.dll,LaunchINFSection %windir%\INF\wmaccess.inf,UninstallWM" StartX.exe /wait "RunDll32 advpack.dll,LaunchINFSection %windir%\INF\msmsgs.inf,BLC.Remove" StartX.exe /wait "msiexec /i MsnMsgs.msi /qb-! /norestart" regedit -s patchMSN.reg patchMSN.reg: Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Microsoft\MSNMessenger] "AppSettings"=hex:62,04,00,00 "DSBkgndMode"=hex:01,00,00,00 "PassportBalloon"=hex:0a,00,00,00 [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run] "MsnMsgr"=- I still need to know whether it would work as intended from SVCPACK, and questions 1b, 3a and 3b remain unanswered as well.

Don't know if this is easy to implement (or if it's worth the hassle). This is what I think needs to be done to get it in: 1) Copy wmcsetup.exe into SVCPACK 2) Extract wmcsetup.cat (subdir "update\") and place in SVCPACK too 3) Create a file inside SVCPACK called HFINT.DAT with the following in it: [FixesInstalled] WMCSetup [WMCSetup] ConnectionManager.xml ContentDirectory.xml fsdkreboot.exe MediaReceiverRegistrar.xml WMC_BW120.jpg WMC_BW120.png WMC_BW32.bmp WMC_BW32.jpg WMC_BW48.bmp WMC_BW48.jpg WMC_BW48.png WMC_Color120.jpg WMC_Color120.png WMC_Color32.bmp WMC_Color32.jpg WMC_Color48.bmp WMC_Color48.jpg WMC_Color48.png wmccds.exe WMCCFG.chm WMCCFG.exe WMCCPL.dll wmcsci.dll wmfdist95.exe 4) Extract the files mentioned in HFINT.DAT and place them in I386 5) Edit SVCPACK.INF to include: [setupHotfixesToRun] wmcsetup.exe /q /n /z [ProductCatalogsToInstall] wmcsetup.cat The wmfdist95.exe is the same file as the one we're including for the WinXP WMP9/10 codecs. Maybe this one can be omitted (or the other way around). I think this is everything...

You can try ExeScript but I doubt it will work in DOS.

What's in your Comment.txt? The language pack needs to be installed as well because it doesn't replace any files; it's just a bunch of new files. If the language pack is used, this is executed by the silent installer in my thread: StartX.exe /wait "msiexec /i netfx.msi /qn /norestart" StartX.exe /wait "msiexec /i langpack.msi /qn" StartX.exe /wait "regedit -s patch.reg"

**** OBSOLETE **** This package is suspended in favor of the "Multi Compiler" at http://www.msfn.org/board/index.php?showtopic=61784.

LegitCheckControl.cab, but that's ignored with HFSLIP 51119.

The silent installer goes in HFSVPK as it's a SWITCHLESS installer. Installers for use WITH a switch go in HFSVPK_SW.

I've slipstreamed the silent installer Zxian made over here: http://www.msfn.org/board/index.php?showto...211#entry411281 I get the same result installing it manually on an existing installation of Windows and installing it via SVCPACK during installation of Windows (made with HFSLIP). Whether or not it actually works is something different. I don't have any programs requiring .NET 2.0 so I can't check.

Thanks, but I followed the tutorial in the thread you linked to and managed to make one myself back in August. I just wanted to try this one out. My full findings of the proggie by JASpurrier3: - the langpack is not installed (Windows Update is right) - I still need a reg patch to remove the redundant hotfix entry from Add/Remove Programs - the created installer file is HUGE compared to my older one (19.3MB vs. 12.4MB) but that's because WinRAR is being used here

Same here. WU still asks to install the langpack.

SolidasRock: I had the same problem with setup.exe following a slightly different tutorial (http://www.msfn.org/board/index.php?showtopic=40788). Turns out the problem was with using 7za.exe. When compressing the contents of the admin install folder through the 7-zip UI instead, all was fine.

I've been integrating LegitCheck into the Windows 2000 test installs for a few weeks now and never had a problem until a couple of days ago when I was presented a WGA download dialog on MS Downloads. Two days ago, I read that thread you linked to so I downloaded the new version and integrated it into the test install of Windows XP. I've made two so far (the latter contains two more hotfixes) and it's working on both except that the WGA control is disabled by MSIE. Since I've never integrated this into Windows XP before (only Windows 2000), I don't know if this is expected behavior. Either way, it's easily fixed by removing a REG key as pointed out in one of the posts on that thread.