mazin

Thanks. I wasn't satisfied with the idea that JS is dependent on CMD for creating that path in the Registry, despite it worked well. Now, JS is completely independent, working on its own to define the path to Winamp.exe. It's now universal. BTW, if you use INF to install Winamp this way, let me know.

Old DOS solutions might work, but might not: start "\\fs1\Basement Plotter HP5500 OR SET fs1=\\fs1\Basement Plotter HP5500 start fs1

Run EXE, then go to: C:\WINDOWS\Downloaded Installations\{9AA435FA-9B29-4D21-A80A-03E887C0F89B}\ACDSee 6.0 PowerPack.msi Run this register.reg before the MSI:

The Final Word: This winamp.js works anywhere, %CDROM% or %SYSTEMDRIVE%, under BATCH method or RunOnceEX! It does all the job: install Winamp, register Winamp, and copy winamp.ini! NOTE: 1- The word CDROM mentioned in winamp.js is merely a word. You can replace it with any other word you like. It represents the drive letter where winamp.js resides; e.g. C:, D:, or whatever. Therefore, this script is usable wherever we put it in, i.e. on a CD or HDD. 2- This script does not install "Modern Skin Support". If you decide to install it, consider adding these strings immediately before the line commented "//closing winamp": WshShell.SendKeys ("%{F4}");//closing Winamp Library WScript.Sleep(500); Also, increase installation time from 45000 to 60000.

I think you used this tweak: ;Disable Welcome Screen and uses Classic Logon [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon] "LogonType"=dword:00000000

Great finding! I didn't know that. I think it's the whole applet of System Properties. Have you played with it?

Yes! This is one of the solutions.

I recall there's a couple of threads on Application Switches forum on how to populate D: (or whatever) as your system drive. Search for them.

OH! It's a real pic. But what does it really mean?

Or I think you used: [unattended] UnattendMode=FullUnattended

Then, you probably need to apply this trick: http://www.msfn.org/board/index.php?showto...ndpost&p=125501 If you do, you won't need taskkill nor Reboot=.......

Whaaat?! Then, no room for unattended AutoMounting?

I wonder why you left the orig idea! It should work well, unless the new idea is more efficient.

-- Feature's Name ----- Title 01 Overland ----------- Overland 02 SoftwareUpdateTool - SWUT Application 03 AltLangPDF_CD1 ----- Alternate Language Arabic PDF 04 AltLangPDF_CD2 ----- Alternate Language Hebrew PDF 05 AutoRun ------------ Autorun 06 DriverCondensed ---- Driver 07 HTML_CFG_ALL ------- HTML.cfg 08 MSIO --------------- Microsoft IO 09 PrinterAssistant --- printer assistant 10 RDT_Passthru ------- hpbvspst.exe 11 RDT_PDI ------------ hpfpdi08.exe 12 RDT_Uninstall ------ Root Uninstaller 13 ReadMe ------------- read me 14 TestPage ----------- TestPage

Looks simple. Go ahead. I'm lazy enough, so I need a proggy to create it for me.

Yeah...I use that reg tweak, too.

Thanks, MCT, for your time. One more question: Don't I have to define a path and name for the ISO file I want to automount?

Thanks in advance.

I read your other thread. You moved fast in configuring DT! What I mean is: How do I automount an ISO in one of the virtual drives I create with your method?

hmm...so you left RunOnceEX...you're moving fast

I'm the second voice (1st after yours). Come on!

- Office is yourZ. - Serial is yourZ. - ........ is yourZ. if i only know how that is considered illegal?

Nice guide. Still, I need the automount trick.

This is my opinion, too.

Especially, for drivers, I also recommend roel's idea.