iamtheky

one post every two years and you wasted it

http://support.microsoft.com/kb/894625

thx but, was (fruitlessly) hoping there is a shutdown command from there, or even a janky way to not let it soft boot back up from ghosts -rb or dos debug reboot commands. That way integration can just bag it and tag it.

Yeah thats what I am finding. Maybe someone smart can explain better than I am googling... There is a dos debug code to reboot yet none to leave the system down...what/why is the limitation

you could place it, run it, and delete it, while restricting user input blockinput (1) DirCreate ("C:\temp1") ;creates a temp destination fileinstall ("setup.exe" , "C:\temp1", 1) ;rolls the setup.exe into your compile and when ran deploys it to c:\temp1, overwriting any other setup.exe in the folder. runwait ("C:\temp1\setup.exe") ; runs the setup from the temp destination sleep (3000) ; maybe necessary to wait for the setup to completely exit before you recursively delete the folder DirRemove ("C:\temp1", 1) ; removes the c:\temp1 folder and all files and folders within

what does it tell you when you run the command explicitly. this test shows the command looks ok, so unless the run command has a limitation that msgbox does not, it should be fine. $log = @ProgramFilesDir & '\MyAshampoo\install.log' msgbox (64,"test", @ProgramFilesDir & '\MyAshampoo\UNWISE.exe /S ' & $log, 10) Is the install.log already in that folder...

Wait, Clu entertaining VLK + Nlite? are there valid scenarios for that combo?

maybe $log = @ProgramFilesDir\MyAshampoo\install.log Run(@ProgramFilesDir & '\MyAshampoo\UNWISE.exe /S ' & $log) theres a space after the /S

nope, that would be reboot. these are not ATX boards so the ATXoff (shutdown12, shtdwn16) utilities have not worked either.

If you are just asking if you can set a variable to the log path that should work: $log = @ProgramFilesDir\MyAshampoo\install.log Run(@ProgramFilesDir & '\MyAshampoo\UNWISE.exe /S "$log"')

All your pages were set to "Start at 0" So I changed the first one to "Start at 1" and the subsequent slides "continue from previous selection" Page_0_repaired.doc

**assuming this is an auoit script** there is no need for capturing the contents of the install.log: Run('UNWISE.exe /S "%fullpath%\install.log"') If it is not currently on the box just do a fileinstall ("install.log" , "%destination_path%" , 1) and then use the destination path as the argument for WISE.

you could have searched that string and found threads expanding on the discussion and offering other clsids, as well as sidebars over calling it 'godmode' since it is of no regard what you type before the id.

We have an integration facility that will begin dropping our new images shortly. We have no bearing on their operation so solutions regarding the actual implementation, beyond the behavior on our disc, cannot be utilized. The image we have pulled is sysprepped with some stuff queued up in the runonce, so to make the integration facilities life a little easier we would like the system to shutdown after the image is deployed (not reboot, not exit the application), so they can close it up and ship it with no further interaction. We are considering a PE option atm, if there any other keen ideas they would be much appreciated.

The fact that I only read the Titles has made for some serious gaffes, but I think this time it may have helped....

what you want is autoit. you will need the following commands (and they will be in this order). I suggest you download it then open the script editor and hit F1, the help file is actually quite helpful with this application. splashimageon (your pic) dircreate (the place where you will put stuff) fileinstall (all your stuff) runwait (all your stuff from the place you installed it) splashoff () <--if you want to close your splash properly, probably unnecessary in this instance exit you will then compile, and your runonce will consist of calling this .exe you just made

You are only going to hide it from novices: but as a another roadblock in addition to setting it to hidden: you could also name it [alt+0160] as in the keystroke that will create a blank character you could then change the icon to one of the default blank icons then it appears as a blank space at the top of the folder listing. ---of course not with $oem$ itself, with maybe just a single content folder underneath the $oem$ would appear empty save for the size.

http://technet.microsoft.com/en-us/library...28WS.10%29.aspx

no universal afaik, but you can drop them all http://driverpacks.net/driverpacks/windows...ss-storage/9.01

do ps/2 input devices work? do other usb devices function (storage or otherwise)? has this issue been replicated on multiple systems with the same image? .......and assuming you have tried multiple usb mice/keyboards to rule out the devices

"Internet Based Access" are they restricted to your domain/site/webapp or do they have the entirety of the internet? do they have access to the address bar or other browser properties? Though if you have an xp kiosk image with cmd and notepad available, I dont think anyone is trying too incredibly hard to gain access.

How are they performing this task "checkout the latest product lineup and our services?" browsing your site, watching a video, controlling a slide show, controlling an app? --in a small script you can bind away keys or restrict their cursor to your frame, the question is how much interaction does your user need? imho, it is much easier to start with no control and work forward than vice versa. other ideas: *make sure the BIOS is set to only boot from the physical/network disk, and then pw protect that. *Disable external ports/ usb and such.

You dont have to tell it to run the msps. throw them all in the updates folder and just run setup.exe That and you might need to stick with 8.3 filenames if that is the case OFFICE2007SP2ENGLISH is about 12 characters too long

http://www.dvinfo.net/forum/flash-web-vide...eg2-vs-wmv.html and a decent old article comparing rates to size and such http://www.tomshardware.com/reviews/divx-6,1060-4.html

whats the kiosk for, how much UI? if it is very limited user interaction there might be very global things you can remove or keys you can bind.... Maybe subbing out the physical keyboard for an osk.