MHz

The syntax for Start is different with XPSP2. Type Start /? at a prompt to see. Your usage is: Start /Wait "%SystemDrive%\.... should be: Start /Wait "" "%SystemDrive%\..... The 1st use of "" is for the title of the cmd window.

you could try using Del /F /S f = force s = recurse subdirectories. That would halve your entries. But, seems like WFP is possibly replacing them? If so, you may need a patched SFC_OS.DLL?

Certainly can. This makes it easier to maintain the drive, with smaller volumes. Instead of giving them drive letters, you assign them empty folders to mount to. Basically, it is a junction point. I have a 200 gb drive, with 4 volumes. Each is mounted as a folder.

You need to have XP export the keys as RegEdit4 format. When you save, you can see a dropdown box. Use it to select RegEdit4 format. As 98 does not like unicode RegEdit5 format.

Indentify Installer does what USSF does and more. Instant results with rightclick. USSF was a nice inspiration. It has been out classed now.

Identify Installer will make things easier for you. It quickly gives you the information. Installsheild requires the /f2 for logging onto the harddrive, else it will fail. If you unpack the installer, you can put the setup.iss, with the setup.exe, without using /f1, else you need to use /f1 and specify a full address to the setup.iss file.

No one is logged on at cmdlines.txt. Shortcuts for all users profile, go to all users profile. Shortcuts for user profile, go to default user profile. Same happens with reg entries. current user entries, go to default user entries, in cmdlines.txt.

You could try and move the installer window offscreen, with WinMove()

Ram that does not follow the JEDEC standard, is asking for trouble IMHO. One of the major issues with ram of today, is incompatibility with the motherboard. Testing ram in another machine, may prove to being a waste of time. Memtest86 will tell you if you have memory problems. Run it overnight. If any errors come up. Then you have either faulty, incompatible, or ram that has it's timings set incorrectly. Incompatibility and timings, are the problems of using non-JEDEC standard ram.

Your joking right??? It is a distribution share, on a network.

Downolad this, has been tried and tested. If windows gives a warning about inserting the windows cd, then cancel it. The file will then remain patched.

I have used both VMWare and VirtualPC. Both have similar features. VMWare does seem to run better for performance. Have tried and failed with VMWare, to have multiple machines with a single OS image. VirtualPC can do this, so is my preference to use. The small performance difference, seems trival to a good feature.

I do not believe you can. With SetupMgr RunOnceEx runs just prior to logon. You maybe calling the ierunonce.dll manually, to have it running at Cmdlines.txt? No, they remain on the CD. No method mentioned in Ref.chm, to do hide it.

Check your boot settings in Bios.

Use MSConfig, to disable and enable startup items, until you find the offending item. It maybe a bad driver.

Using Components disables the programs and removes the shortcuts. Disabling the programs is not a solution to removing shortcuts. These shortscuts are not created until the desktop is active. They reside in %AllUsersProfile%, so if you delete them once, they will not return. I use an AutoIt script for this. It is called by the HKLM Run key. It waits for a process to start, then does the tidy up process etc, removes the reg value, removes itself and reboots. I set a small reboot timeout, which looks so much better. I have tested a batch script before in the startup folder. This works fine. But an ugly, black window solution. Not tried, but you could enter reg entries, to remove them on the reboot. The runonce key may seem suitable for the task.

Ensure that in AMS5, that the Project window settings, are not set at Always On Top.

BootCfg /? should lead you to the answer.

Try changing your last line with For $i = 1 To 5 WinClose("IsoBuster - Pro - 1.8") If Not WinExists("IsoBuster - Pro - 1.8") Then ExitLoop Sleep(250) Next This will try, up to 5 times to close the window. I normally notice that during RunOnce, you need to ask the window twice, to close.

That is one of Shell32.dll icons. The program that uses that by default is Quick Batch File Compiler.

DOS could automatically copy it to file, without an extension. This would be incorrect for you, so it prompts for whether it is a file with no extension, or a folder. Just adding a backslash to your destination path, should inform DOS, that it is a folder. This will result in no prompt. Edit:fix typo

Window title recognition works with case sensitive, literal strings. No wildcard support. Mode 2 is substring. So you can select any part of the title string. If a title is word1 word2 word3 word4 word5 You can choose any of the 5 words to use, or a group of the words to use. Some valid examples would be word1 word4 word2 word3 You should be able to use even part of a word, if needed. I see what you are doing, you are using a word here, and a word there. No, that is a broken string. It would need the be a substring (1 piece of the string).

That window is just a visable warning, that the system is shutting down. This is very normal. Logging into the desktop, the first time, is a important stage. I would recommend, as Alanoll has recommended, in using 60 seconds for shutdown, other wise your themes etc. will not be setup properly.

No wildcards in window titles. You have 4 options. Opt("WinTitleMatchMode", 1) ;1=start, 2=subStr, 3=exact, 4=advanced 1 is default. Title is from the start of title. So a title with MSFN Forums -> Replying in Wildcards in window namescan be entered as MSFN Forums 2 is substrings. So with the existing title as above, You can just do this: Replying in Wildcards 3 is exact. Exact full title. 4 is advanced. This mode can allow you to use class names instead. You will see class listed in AutoIt Info Tool. This allows you to respond to a window, without knowing it's name. classname=CLASSNAME There are also functions available to get window titles, if you only know part of the name etc. Like WinGetTitle ( "title" [, "text"] ) Many different ways to solve a problem.

You need to have Inno Setup installed. ISTool would be helpful also. You need to use Innounp.exe -x spybotsd14.exe to unpack the installer. This will unpack the files to the current directory. An .ISS file will also be created. You can use the .ISS file to lead you to edit that one, or replace it, and edit to suit. Then use Inno Setup to compile it, back into an installer.