pinout

Okay, I used WinINSTALL LE to remove the Launch Condition "Installed OR MM" ("The file you are trying to open is part of Microsoft IntelliPoint Setup. To run Microsoft IntelliPoint Setup, double-click Setup.exe in the root directory.") But now when I run the MSI I get "Error 1406.Could not write to value Model to key HKEY_LOCAL_MACHINE\Software\Microsoft\IntelliPoint. Verify that you have sufficient access to that key, or contact your support personnel." Is there something else I am supposed to modify/remove?

Whats the tool called again that modifies MSI's ? I could do it myself

Trying to figure out how to silently install the IntelliPoint 5.0 software... Downloaded from here Only information I could find was here at AppDeploy.com You extract the files from the EXE and run OEMSETUP.EXE with an OEMSETUP.INI, this works, but it launches a second process (setup.exe), so using START /WAIT is pretty useless. Anyone have another method for installing this?

Yes, quotes are necessary for spaces, but if you dont provide a TITLE parameter using quotes, it will not work! I dont think you guys are actually TRYING these commands before replying. Will work: START /WAIT C:\PATH\APP.EXE START "title" /WAIT "C:\PATH\APP.EXE" START "title" /WAIT "C:\LONG PATH\APP.EXE" Will NOT work: START /WAIT "C:\PATH\APP.EXE" START /WAIT "C:\PATH WITH SPACES\APP.EXE"

Nope, if you use quotes it will not work, try it! 1. Open a Command Prompt 2. Type: START /WAIT "%SYSTEMROOT%\system32\calc.exe" 3. It doesn't open up calc.exe 4. Remove the quotes and it does

I dont really know what you are asking? I just use START "" /WAIT no matter what because if you pass any parameter thats quoted without first providing a title parameter, you'll run into problems. You could do: start "" /wait msiexec /x{B060295C-E378-484C-91BE-DB5C41383FE9} /qb even though its not really necessary in your case

I thought I would share something I finally discovered that I was doing wrong when using the START command. From what I've seen, most people use the START command in this manner: START /WAIT C:\path\to\exe\some.exe This works fine, but not if the path contains spaces. So one would think that to use the START command with a path that contains spaces, you would simply use: START /WAIT "C:\path with spaces\some.exe" But it doesn't work that way. Lets look at "START /?" in Command Prompt: START ["title"] [/Dpath] [/MIN] [/MAX] [/sEPARATE | /SHARED] [/LOW | /NORMAL | /HIGH | /REALTIME | /ABOVENORMAL | /BELOWNORMAL] [/WAIT] [command/program] [parameters] The FIRST quoted parameter is actually the title of the window, so using the command: START /WAIT "C:\path with spaces\some.exe" will actually open a new command prompt window with a title of "C:\path with spaces\some.exe" and not actually execute some.exe The trick is to provide a title parameter, which can be anything you want: START "" /WAIT "C:\path with spaces\some.exe" I just use double quotes with nothing in between (null) I always just assumed this was a limitation of the START command or that I didn't know how to use it properly, until I came across a post on alt.msdos.batch.nt (Windows NT tricks, traps and undocumented features) Your current START commands probably work just fine, but I find this usefull when the name of an installer EXE contains spaces, then I dont have to rename it (I like to preserve original filenames).

if you quote the command or pathname, you have to use START "" look at START /? START ["title"] [/Dpath] [/MIN] [/MAX] [/sEPARATE | /SHARED] [/LOW | /NORMAL | /HIGH | /REALTIME | /ABOVENORMAL | /BELOWNORMAL] [/WAIT] [command/program] [parameters] if you do START /WAIT "command" its going to think "command" is the title thats why you have to do START "" /WAIT "command" seems strange, but thats the way it has to be done if you want to quote the command but you are right, you can do a START /WAIT longpath\command, without having to quote it.. but you can run into problems.. for example if you are trying to execute an exe named setup.exe, it will run setup.exe in system32

I made a directory in $OEM$\DRIVERS\ called CRT (name it anything you want) and placed the drivers for my monitor in that directory, INF & CAT file. Add the $OEM$\DRIVERS\CRT path to your WINNT.SIF, OemPnPDriversPath=DRIVERS\CRT works for me

in my AIM batch file I use: START "" /WAIT "INSTALL_AIM.EXE" /S START "" /WAIT "PSKILL.EXE" minibug.exe kills the minibug.exe process after aim is installed, this seems to prevent the minibug thing from fully installing

use START "" /WAIT "long path\whatever" the START command actually uses the first quoted parameter as the window title, passing "" will fill the first quoted parameter with null and the second one will work