blinkdt

I believe MU integration is fine, but I continue to experience the same situation faced by raduking on page 2 of this thread. That said, MU integration appears to be nothing more than correctly placing and registering one DLL file based on what I have picked up in this discussion. Your procedure for securing a clean copy of DataStore.edb was crystal-clear and makes perfect sense. I will try to register both .dll's and/or play with this some more.

@'Felix': can you post a link to the thread where you found that image? Looks intriguing....

Nice. So this is what I have: $$\SoftwareDistribution\DataStore\DataStore.edb $$\System32\muweb.dll $Docs\All Users\Start Menu\Microsoft Update (shortcut to C:\WINDOWS\system32\rundll32.exe C:\WINDOWS\system32\muweb.dll,LaunchMUSite target) I'm going to try to register muweb.dll from Cmdlines.txt: [COMMANDS] "regsvr32 /s %windir%\system32\muweb.dll" Not sure about that, though. But worth a shot. Edit: no luck.

Nope, FileGetShortName was not needed. I'm converting many of my scripts based on your find and everything is running smoothly, like so: Run("REGEDIT /S " & @ScriptDir & "\prefs.reg")

It wasn't too long ago that AVG reported all of my compiled AutoIt scripts as viruses. Bummer, but I can deal with that. Nice to see AVG tech support was responsive even for users of the free version.

"Considering that WPI only has one line I assume it should be as follows" Not sure what is meant here. WPI allows for six (6) command lines and two opportunities to import registry keys, before (regb) AND after (rega) the command lines run. First, save your settings as a .reg file (go to the registry and export the relevant key if necessary). Here's an example of an "after" operation: rega[pn]=['REGEDIT /s %cdrom%\\Programs\\Java\\java.reg'] You can also import the .reg file from a command line: cmd2[pn]=['REGEDIT /S %cdrom%\\Programs\\AcronisTrueImage\\Acronis.reg'] Good luck.

I second that! This one has bugged me for ages. Special thanks to Nologic for bringin' it home!

RyanVM's posts are intriguing, to say the least. I'm using a ham-handed AutoIt script to get the job done at present (please do not ask me to post it--it works but I'm not proud of it). @BoardBabe: the OEM method did not work for me. One author claims DataStore.edb can be deleted and replaced during the install, but most agree that it is one tough nut to crack. Googled "DataStore.edb" and did some reading, turns out it is a database file related to the update feature, no real surprise there. I assume if a current database file can be integrated, then Windows will accept the Microsoft Update feature. The key, then, is to integrate DataStore.edb and related files from the get-go, the first method preferred by it_ybd. So I took a look at RyanVM's UpdatePack and found a few entries in the "entries.ini" file that appeared relevant: ;This section contains entries that need to go into the [Files] section of dosnet.inf d1,DataStor.edb d1,muweb.dll ;This section contains entries that need to go into the [WinntDirectories] section of txtsetup.sif 242 = SoftwareDistribution\DataStore ;This section contains entries that need to go into the [SourceDisksFiles] section of txtsetup.sif DataStor.edb = 100,,,,,,,242,0,0,DataStore.edb muweb.dll = 100,,,,,,,2,0,0 Dropped RyanVM's DataStor.ed_ file in the I386 directory together with my muweb.dll file and expanded DataStor.ed_ as DataStor.edb and DataStore.edb for good measure, dropping them in I386 as well. Updated the dosnet.inf and txtsetup.sif files, but no luck. @RyanVM: is it bigger than a bread box? Any help here would be greatly appreciated by those of use who are looking simply to integrate this feature. I am certain that I have missed a few files and more.

I remember seeing Netscape sitting on a shelf at "Best Buy" for $125...and people where buying it. Good riddance.

Sure. Download the installer HERE and save to desktop. Extract the contents to a folder called 'RocketDock' and place it in the Program Files directory. Place a shortcut to the executable 'RocketDock.exe' on the Desktop and run the program. Now configure it as you like...add icons (.png files) found at WinCustomize, change dock settings, etc. Now quit the program and restart. Your setting are saved in the following registry keys: [HKEY_CURRENT_USER\Software\RocketDock-v0.9.4] [HKEY_CURRENT_USER\Software\RocketDock-v0.9.4\Icons] Export those. Now go to the 'RocketDock' directory in 'Program Files' and create a self-extracting SFX with WinRAR. Add the comment: Path=RocketDock SavePath Silent=1 Overwrite=1 Shortcut=P, "%programfiles%\RocketDock\RocketDock.exe", "Accessories", "A convenient and fun way to organize your desktop icons.", "RocketDock" Shortcut=P, "%programfiles%\RocketDock\RocketDock.exe", "Startup", "A convenient and fun way to organize your desktop icons.", "RocketDock" The SFX will extract the files and create two shortcuts, one in Startup and one in Accessories for good measure. Finally, import the registry keys. My WPI entry looks like this: pn=14 prog[pn]=['Rocket Dock'] desc[pn]=['<center><img src="./icons/RKLauncher.png" width="64" height="128"><br>Convenient and fun way to organize your Desktop icons.</center>'] cmd1[pn]=['REGEDIT /S %cdrom%\\Programs\\RocketDock\\Desktop.reg'] cmd2[pn]=['%cdrom%\\Programs\\RocketDock\\RocketDock.exe'] cmd3[pn]=['REGEDIT /S %cdrom%\\Programs\\RocketDock\\prefs.reg'] dflt[pn]=['yes'] forc[pn]=['false'] cat[pn]=['Accessories'] ordr[pn]=[140] uid[pn]=[''] deps[pn]=[] pn++ The Desktop.reg entry removes Windows-based icons from the desktop. I mean, with the RocketDock in place, who needs 'em? Unlike StarDock's ObjectDock and the RKLauncher, Punk Software writes the dock settings to the registry and not .ini files. That's a good thing, because some unknown process or sequence of events tends to zero out my .ini files for Dock apps.

Search using the keyword "Photoshop" and you will find several threads, like the one HERE!

Thanks, MHz! Let me incorporate your thoughts into a larger script and see what happens in the days ahead. I will post back the result. As an aside, are there any AutoIt books out there that you recommend?

OK, I have a problem in need of a working solution. I am trying to install Microsoft Update (MU) in unattended fashion. I drop the MU shortcut in the OEM structure so that it appears in the Start Menu, register the MUweb.dll, and all should be good. But not so. For some reason, it takes about five attempts to get the site working correctly on my testbed machine. For example, I click the MU link but then receive the error detailed HERE by raduking. Boardbabe notes that this can occur three or more times before the darned thing works properly. In my experience it can happen as many as five times, with the sixth time being the charm. I suppose the problem is caused by simply registering the .dll without benefit of using the IE interface to do it - takes it a few attempts to get in synch. Here's what I have so far: Run( @ScriptDir & "\MUstart.cmd", "", @SW_HIDE) WinWait("Microsoft Update") Sleep(15000) Send("{ENTER}") Sleep(3000) Send("{ENTER}") Sleep(3000) If WinExists("Automatic Updates") Then Send("{!y}") Sleep(1000) EndIf ProcessClose("iexplore.exe") The batch launches MU (sorry, but I am not a COMSPEC guy). An annoyingly long sleep command is used to allow MU to fully load. Two keystrokes take care of the "Start Now" and "Continue" nag screens. Then we check for the error window and respond "yes" if it exists before closing IE. I run this five times for good measure. Here's my question: Anybody have a "Do...Until" loop statement snippet handy that would do this in a clean fashion? We want this thing to loop until the error window is no longer present. Then the script would exit. In a perfect world. @MHz/Nologic: you guys should get a publisher and get published. A book o' AutoIt snippets would be nice, under 300 pages, small type, great for bathroom reading. I'd buy it.

Nice job, Nucleus. If I where in your shoes--considering the solid effort you have invested in this to date--I would go to the trouble of using RegSnap one more time: run your install routine again on a test-bed machine and open FrontPage. When the nag screen prompting you to set FrontPage as your default HTML editor appears, 1) stop, 2) run RegSnap, 3) click "OK" on the FrontPage nag screen, 4) immediately run RegSnap again. Now compare the two settings. You should be able to isolate the RegTweak that will set FrontPage as the default editor. Then retrace your steps and add that tweak to the larger RegTweak file. If I am not mistaken, you should then be good to go. RegSnap is truly amazing. I have played with it for days on end with really interesting results. Another tool in the arsenal.

RegSnap can appear messy, but the primary entries speak for themselves perhaps: HKEY_CURRENT_USER\Software\Microsoft\FrontPage\Explorer\FrontPage Explorer\Settings\DisplayModePrompt New: String: "0" Old: String: "2" HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Default HTML Editor\shell\edit\command\@ New: String: "C:\PROGRA~1\MICROS~2\OFFICE11\FRONTPG.EXE /dde" Old: String: ""C:\Program Files\Microsoft Office\OFFICE11\WINWORD.EXE" /n /dde" HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Default HTML Editor\shell\edit\ddeexec\Application\@ New: String: "Frontpg" Old: String: "WinWord" and HKEY_CURRENT_USER\Software\Microsoft\Shared\HTML\Default Editor\shell\edit\command\@ Value: String: "C:\PROGRA~1\MICROS~2\OFFICE11\FRONTPG.EXE /dde" HKEY_CURRENT_USER\Software\Microsoft\Shared\HTML\Default Editor\shell\edit\ddeexec\Application\@ Value: String: "Frontpg" I would start by importing those following the install and see what happens. Go to the registry, locate the keys, export them and combine them into one file. And if your whole system gets screwed up, well, that's why editing the registry can be a bad thing. Hope you have a test-bed machine.

OK, bear with me here and check me if I'm wrong, but edit is edit and open is open. If you double-click the file your preferred browser should open it. But if you right-click-->Edit, the editor that you specified in the file association should open for editing? That thread was filled with references to players and music/file associations to be sure, but the concept is the same. If you use a proggy like regsnap you should be able to monitor the registry change and isolate the one you seek. I always use the trial version on a test-bed machine when chasing registry tweaks. I'm trying to think of another way but I always come back to the regtweak scenario.

I guess I don't understand as I am not a FrontPage user: aren't these actions one-and-the-same? In any event, you should be able to create a reg tweak--based on the thread referenced in my first post--to create an association that will allow you to right-click-->Edit and open the file in FrontPage for editing. Or am I completely off base here? Edit: @undeadsoldier Good, but the only options available to me when using that routine where more Office apps and notepad. My preferred editors--HomeSite and Dreamweaver--where not listed. I think this definitely calls for a regtweak to be added following the install and before the app is opened.

As an interim solution, you could exercise the right-click-->Open With option and you should find your preferred editor listed there. But that involves an extra click, so... Another option is to explore the file type world. For example, open Windows Explorer-->Folder Options and click the "File Types" tab. Scroll around and find the file extension you want to edit, maybe in this case HTML. Now click the Advanced button and notice the options available to you under "Actions." Sadly, if you edit the "Edit" action you can see that the path points to an Office app like Word. But more likely than not, your preferred action is already listed in Actions, for example "Edit with HomeSite+." So what's to prevent a user from opening that Action in edit mode, copying that path information, and pasting it into the default "Edit" action? And now, when you right-click-->Edit, your preferred app will open to do the job. And don't forget other file types like HTA, ASP, etc. How one goes about doing all of this in unattended fashion is beyond me, although you will find one heck of a discussion HERE. Me? I "Open With" and can live with that painlessly.

Has anyone else experienced a problem in mapping any theme other than the default? Simply importing the registry settings did not work correctly for me, so I fell back on an AutoIt install method: 1. install the program normally to ensure that all .dll's are registered correctly, 2. copy over the preferred theme file, 3. map the new theme via the CursorXP configuration utility.

Wow, yet another post-install wizard, and this one looks nice n' easy. I'm a big AutoIt fan and would love to learn more about this before giving it a spin with my Windows 2000 installs. Can you post a working sample with integration instructions?

@tommyp & fdv: thank you so very much for providing this tool and your continued efforts. I have applied it to Win2K Pro, Win2K Server, and Win2K Advanced Server with great success. And after reading this entire thread the words of my first grade teacher, Sister Catherine, come back to haunt me again. "Following instructions is a sign of intelligence." She tossed out that truism on occassion as a challenge to her sometimes scatter-brained students, and it never failed to inspire. Your instructions are clear, meticulous, and accurate.

I think you can dispense with all of that TRANSFORMS nonsense by creating an .mst file and saving it alongside setup.exe at the root of the CD. Mine is called "setup.mst" Then open the setup.ini file found in the "Setup" directory and make a few changes to refer to your new .mst and to tell Office how to set the verbosity (is that a word ) [MST] ; The MST section gives the full path to a transform that should be applied. ;MST1=\\server\share\some transform.mst ;MST1=D:\transforms\my transform.mst MST1=SETUP.MST and [Display] ; The diplay section is used for overriding the default UI ; Value Default Description ; Display full Option to override the default UI ; [none, quiet, basic, reduced, full] ; CompletionNotice Yes Option to display a setup completion ; notice for otherwise quiet setup Display=Basic CompletionNotice=Yes Hope that helps.

Hey, nice find, lionhrt. I had been wondering how to change the color of the bar myself but was stumped. Based on your query, I took another look and, well, check this out: 1. The code snippet src="./Graphics" found in the third line of your first code quote is just begging for an actual image to work with. For example, you will notice that the "Graphics" directory is empty, resulting in a transparent progress bar. 2. But let's say you want a red-colored bar. Just create a 1x1 pixel colored image and dump it in the graphics folder, then change the code to refer to the new image, like so: src="./Graphics/redbar.jpg" You can also edit the height and width of the bar, within the confines of the left column, of course. Now you have a red progress bar counting down atop a background placeholder that you can change by editing the class "timer" found in the wpi.css file located in the "Themes" directory. It looks like this by default: .timer { background-color: #18339f; border: 1px solid #000000; padding: 1px; } So you can change the background color, the color of the border, you can even mess with the padding setting if you so desire. One note: if you use an actual picture to act as the coutdown bar, it will obviously become distorted as it shrinks. That has some interesting possibilities, I suppose, but I can't think of any at the moment. Editing your second code block mostly affects the timer-related text. Play with it.

Incredible! Point-and-click easy for the basics. almulder, you, sir, are a scholar and a gentleman, as an old teacher of mine used to say. I just pray you are keeping notes, maybe I can help you edit your resulting manual.

Microsoft's method does turn the trick. Recently picked up a nice keyboard and mouse set, noticed that the 5.2 install disc includes instructions for silent installation in the form of two PDF files buried in the respective IPoint and IType SETUP directories. I have them on my server, you can grab the Intellipoint documentation HERE and the Intellitype documentation HERE. They are about 1.2MB each and certainly answer some of the questions asked here. Edit: but the msi method is hard to beat for convenience and economy of size.