RogueSpear

You may want to try actually specifying a particular NIC here. I'm not 100% sure on this, but my line of thought is that if you have a FireWire adapter, the settings could be getting applied to it rather than your real NIC.

You have these two lines consecutive, which will pretty much make the first line useless. I'm not 100% sure what this script is trying to acheive other than I see it's using Elcomsoft's excellent registry change utility. The script itself I have to say, and I mean no offense if you wrote it, is terribly disorganized and doesn't follow good practices in many regards.

Not meaning to stray so far off topic in your thread.. programs like CPU-Z, etc. are going through the management logic that reports temperatures, voltages, etc. WMI is capable of reporting quite a bit of info, but with nobody coming up with, much less following any sort of standard for those diagnostic data types, the developers have to resort to speaking directly to the hardware.

Are all three subnets within the same AD forest? If so, have you defined the three subnets within AD?

You can always modify the .msi file to eliminate that requirement which is what I do, but I remember seeing that there's a command line switch for getting around it. Might have been in the huge Nero thread in this forum.

I've always found that changing the metric for a NIC works pretty spotty at best. Rather, I modify the routing table for precisely what I need and that works every time. For instance, my work laptop connects to a wireless network completely seperate from our internal network. The wireless network provides a much faster connection to the internet and this way the bandwidth on the primary network is saved for those trivial things, like our email server After installing a multihomed computer like my laptop, the routing table indicates both interfaces have a metric of 20 to destination 0.0.0.0 (the internet). So what I do is essentially overwrite default routing entry for the WiFi adapter's internet route: route -p add 0.0.0.0 mask 0.0.0.0 192.168.1.1 metric 10This way only the single entry is modified instead of modifying the metric for the entire NIC.

Actually it kind of makes sense. See when I first posted it, I did in fact make a mistake which was later pointed out to me. Gilesw must have cut and paste the info prior to my fixing it. That's what I'm guessing anyway.

I just clicked on the link contained in the quote in your post and it worked for me.. maybe I'm not understanding something?

Programs like CPU-Z, Motherboard Monitor, etc are not using WMI for the reporting. I'm not sure exactly what it is that they're doing, but you'll probably notice that programs like that need to be continually updated as new chipset and motherboards are released.

You may want to check out this guide: http://www.msfn.org/board/index.php?showtopic=65846

When you repack any application where the source is an .msi file, you need to check the shortcut to make sure it's not an advertised shortcut. If it is delete it and create a standard shortcut. Then do your second snapshot.

@Yurek3, at this point I don't know what to tell you. I've tested this out a few times now. Check your .ini file.

@GSM, very nice work there If you run into something you want me to take a look at, please let me know. I'm pretty beyond busy right now with too many things going on.

Version 1.02 - 04/11/2006 presetup.cmd - Wildcards implemented for dealing with 000_SystemDrive.7z and 000_WinDir.7z files. This way you can have multiple files of each, for instance differentiating between work sites. Ex: 000_SystemDrive-CompanyA.7z or 000_SystemDrive-Home.7z. cmdlines.vbs V1.02 - AutoLogon entries in workgroup and domain situations not working for some users. Both issues fixed. 100_Cleanup.vbs V1.01 - Start Menu cleanup has been broken up between All Users and the User Start Menu. The All User Start Menu cleanup routine is now highly customizable from 500_Settings.ini. Restricting certain Start Menu folders to Admin only access will now accept up to 10 custom folder names and is now seperate from the Start Menu cleanup routine. 170_ConfigAccounts.vbs V1.01 - Same issues as cmdlines.vbs. 171_NameSettings.hta V1.01 - Same issues as cmdlines.vbs. 200_ConfigNetwork.vbs V1.01 - I discovered that not all NICs populate the registry entry for ComponentID the same way. The NIC detection code has been modified to properly detect all NICs. This change required changes to 500_Settings.ini. Also, support for two more NICs added. Changes to the documentation in post #1 will be forthcoming. It is important to use the new 500_Settings.ini file with this release as some significant changes were made for the NIC speed and duplex routine, along with some other minor changes.

This isn't a very elegant solution, but I suppose you could always wrap a password protected WinRAR SFX inside the 7-Zip installer. If you wan't to take advantage of 7-Zip's better compression, just make the WinRAR SFX use no compression (store). Personally, I would just use WinRAR itself for such an installer.

Yep, that's about it. Best thing I could suggest is to make a batch or script that deletes the shortcuts you don't want to keep.

Just lettin ya know. You never know when something like that might come in handy

I'm a little late coming to the thread, but if you still have any interest in utilizing the clipboard from a VBscript, just use AutoItX. Set ai = WScript.CreateObject("AutoItX3.Control") text = ai.ClipGet() WScript.Echo "Clipboard contains:" & text You just need to have AutoItX.dll registered.

@MHz, something to watch out for there is that the entry is not always exactly "Adobe Reader". I've seen it with a version number afterwards. That's why I keyed on the beginning of the string.

Indeed it would not.

I think I'll just let GSM handle this one as he seems to be actively working on it now. What I was going to implement was something using Win32_Product instead of Win32_SoftwareFeature. I just wrote this script yesterday for someone in a different forum: Option Explicit Dim ws, fs, strComputer, objWMIService, colSoftware, objSoftware Set ws = WScript.CreateObject("WScript.Shell") Set fs = CreateObject("Scripting.FileSystemObject") strComputer = "." Set objWMIService = GetObject("winmgmts:" & "{impersonationLevel=impersonate}!\\" & strComputer & "\root\cimv2") Set colSoftware = objWMIService.ExecQuery("Select * from Win32_Product") For Each objSoftware in colSoftware If Left(objSoftware.Name, 12) = "Adobe Reader" Then WScript.Echo objSoftware.Name & " is installed." WScript.Echo "The installed version is: " & objSoftware.Version End If Next

Wow, that's the first update in a couple of years I think. I thought this title was pretty much retired.

@Yurek3, I intentionally did not fix the second autologon in order to properly test the fix. Seeing that the fix worked, I'll put out 1.02 tommorow morning. I'm far too tired right now to be messing around with code. Many thanks for working with me on this one.

This comment is a little off topic, but as a cat owner, that "Flo Control" project just about had me splitting my side. That's a pretty interesting post though and certainly makes for some good reading. I imagine that this variation on determining if someone "human" or not will catch on in certain areas.

@Yurek3, You have not mentioned it, but I am assuming that your computer that you are installing is not a member of a domain. If this is the case, then would you mind trying out this replacement file for me. I changed the way that the script handles AutoLogon entries for computers in "workgroup" mode. Also, please make the following change to your 500_Settings.ini file: LogonDomain=%computername% Please note that for the moment, it will only effect cmdlines.vbs. If it works for you I will change the other script as well. This is very strange as I've never needed to do this for non-domain computers before. Please let me know. EDIT: Attachment removed.