RogueSpear

Yea I do that in VBscript. But that's going to have to wait til tonight or tommorow. Just leaving work and going straight to a client site. Oh happy Monday.. lol

I believe I disable fast user switching in the registry tweaks file.. take a peek in there. [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\FastUserSwitchingCompatibility] "Start"=dword:00000004 ; Set Fast User Switching service to Disabled Enabling Remote Desktop and disabling the Windows Firewall are both taken care of in the .SIF file. [TerminalServices] AllowConnections=1 [WindowsFirewall] Profiles = WindowsFirewall.TurnOffFirewall [WindowsFirewall.TurnOffFirewall] Mode = 0

I made a switchless silent installer that installs all of the InstallShield Script Engine versions (7 - 11). I don't know if this would help out on matters or not. It installs just fine from svcpack.inf. Hit the link in my sig for installers and you'll find it there.

What's actually happening is that the drivers are being copied to the hard drive so that they're available during the PnP enumeration phase of setup. At that time, there is no network connectivity, so the drivers have to be on the hard disk in order to be available. Since there is no way for setup to know what drivers are necessary until it actually does the device detection.. it's cart before the horse scenario. Just because you're copying all of the drivers to the hard disk doesn't mean they have to stay there. After setup has completed, you can always delete the subdirectories that they're in. Whether you do this manually or through batch/script is up to you. And yes you would need to make a seperate image for each model of laptop if it's absolutely necessary that other drivers do not get copied over.

Update - 20060212 Updated DVDFab Decrypter to V2.9.7.0 Updated MSN Messenger to V7.5.0324

My mistake.. he does have Frontier DSL. I still had Roadrunner in my brain after reading an article about how Time Warner is considering purchasing the cable modem franchise from Adelphia out this way.

This isn't a knock on you or your idea, but isn't it rather pathetic that such a thing is even necessary? I find it so infuriating that I need to spend the absurd amount of time that I do on licensing issues. Microsoft is not alone on this issue either. Symantec is another prolific offender. It's not enough that I hand over close to six figures for software that is of questionable quality, but then to spend hours on the phone and replying to emails over this stuff is just insulting.

Howdy from nearby Amherst, NY My brother-in-law lives in Greece and has Roadrunner out there by you. He's experienced similar issues on and off for the last couple of years and it usually seems to happen on the weekends. Of course this could be he's noticing it more on the weekends since that's when he has most of his free time. But I wonder if perhaps they perform network upgrades or repairs in the weekend, figuring it would disrupt business less that way. I have Telcove (formerly Adelphia Business Solutions) for T1 connections and they always do that sort of stuff either in the middle of the night or on the weekend. Sometimes things don't always go as planned however and the service interruption lasts much longer than expected.

It's probably time to resort to Troubleshooting 101. Go back to square one. If you can get the networking to function as expected using untampered install sources, then add things in one by one until you can narrow down what it is that's causing the problem. I know it' a royal pain in the butt, but it's something I've had to do, and countless others here too I'm sure.

Anytime mate EDIT: Well it may be "cleaner" using one file, but then every computer has to decompress the installer even if it's not a VM. Here's the config.txt used with 7-Zip: ;!@Install@!UTF-8! RunProgram="RunHiddenConsole.exe /w msiexec /i VMwareTools.msi /qn" ;!@InstallEnd@!

Forgive me if this is asking the obvious, but do you have $OEM$ parallel to i386? Just thought of something else.. do you have this in your WINNT.SIF file? [Unattended] OemPreinstall=Yes

Hey it's no problem.. I just think that all the recent discussion about this has only served to make the issue a little more confusing. Unfortunately the way that things are at the moment, they just aren't perfect. I'm hopeful that with BTS's forthcoming updates, a lot of these issues will be easily resolved and made automatic.

This little snippet here sets the variable strOEM to the \OEM directory on your install CD/DVD: For Each objDrive in colDrives If fs.FileExists(objDrive.DriveLetter & ":\WIN51") Then strOEM = objDrive.DriveLetter & ":\OEM" Next You can change \OEM to pretty much whatever you like so long as it's on the install media. If you don't want the switchless silent installer executed from the CD/DVD media at all, but rather you've placed it inside \$OEM$\$1 so that it winds up on the root of your system drive, then simply replace this little part: ws.Run(strOEM & "\VMWareTools.exe"),0,Truewith ws.RUN("%systemdrive%\VMWareTools.exe"),0,True

Man I seriously don't see what all the grief is with these two .exe files. You can do things one of two ways: either keep the files on the CD/DVD and execute them from there or copy them to the root of your system drive and execute them from there. If your presetup.cmd file is looking for them on the CD then it will obviously fail if they're on the hard disk and vice versa. With RIS you're limited to executing them from the system drive (unless for some reason you want to overcomplicate things and require a CD in the drive). Here is the presetup.cmd that is in the Method 2 helper for RIS: 7za.exe x -y -aoa %SYSTEMDRIVE%\DriverPack*.7z -o"%SYSTEMDRIVE%" 7za.exe x -y -aoa %SYSTEMDRIVE%\000_WinDir.7z -o"%SYSTEMROOT%" %SYSTEMDRIVE%\SetDevicePath.exe %SYSTEMDRIVE%\D START %SYSTEMDRIVE%\WatchDriverSigningPolicy.exe DEL %SYSTEMDRIVE%\DriverPack*.7z DEL %SYSTEMDRIVE%\000_WinDir.7z DEL %SYSTEMDRIVE%\SetDevicePath.exe EXIT Now, you get SetDevicePath.exe and WatchDriverSigningPolicy.exe onto the system drive either by placing them within $OEM$\$1 in your RIS image OR you could place them inside one of your DriverPack 7z archive files. Either way they will end up where they need to be in time for execution. Something I've been doing for a while now is making one big huge DriverPack file called DriverPack_All.7z and the two exe's are inside of that. I find that the copy operation and the decompression runs a little faster when it's one file instead of a dozen or so files. Finally, later during RunOnceEx, the BTS_Finish.cmd is excuted and then all of the extraneous files are cleaned up.

In this thread I have a download that contains a switchless silent installer and an accompanying VBscript that does exactly what you're looking for. The script utilizes WMI to read the BIOS in order to determine that the "computer" is actually VMware.

I've never used awxDTools so I really don't know.

I would not remove either one and see if it works for you, but like I said earlier, if you can't even ping the other computer and Windows Firewall isn't in play here, then there are some other problems.

You don't need to run the NetBIOS protocol, but I believe some of the files associated with it are needed to support file and printer sharing. Also some services are misleading in the titles. The "NetBIOS helper for TCP/IP" or whatever the real name of it is.. well I found out the hard way a few years back that you should not turn that one off - even if you don't use NetBIOS on your network.

Aye Mrs. Peel, this entire collection may be looking for a crib over at Ryan's before too long. Some folks around here are two sammies short of a picnic and xper is considering closing down the Application Installs forum. Consequently, this thread may very well suck the kumura. Luckily I've copied everything to notepad for easy pasting

I've always found home networking to be a huge pain in the butt compared to corporate networking. First of all you need to NOT remove NetBIOS using nLite. Even though you can and should disable NetBIOS on all of your interfaces, there are parts of it that are still utilized in file sharing. Second, I have run into this a million times.. you must have a password associated with the username that you're using to connect with. If you're unable to ping the other computer, and Windows Firewall isn't blocking ICMP traffic, then you have a problem more serious than sharing not working. Something like your network settings being off. Double check, triple check your network settings. Nobody is immune from tunnel vision or overlooking the obvious. I once spent three hours troubleshooting a network issue where I mistakenly entered a default gateway of 192.168.1.10 instead of 192.168.1.100.

Like child's play when you know what you're doing Thanks for taking the time to look into it. That was really cool of you. So if I'm reading all this right it would seem as though this "program" is attempting make someone money by registering hits on an online ad. Now what I need to do is to try and find out where I got this thing from.

I'm going to be making nLite/RVM addons from most of the installers here and add them in to the listing. This is going to take some time as I will simultaneously be doing maintenance updates to most of the installers and refreshing them as well. And of course I have updates of existing programs to repack besides. I will also be including the MD5 values for both .msi installers and .cab addons. Again this will take some time to complete. The file size listing is going to only reflect the file size of the switchless silent installer as previously done.

Yea I pretty much concluded it's bogus. I compared it to the real file on another of my computers. At this point I'd just like to find out where it came from and how it got there. As a matter of interest I suppose I wouldn't mind knowing what crazy things it does too.

Here you go... AdobeGammaLoader.7z

V1.52 - 02/10/2006 - The supplemental NIC drivers have been updated. There is still a conflict between the latest revisions of RealTek's NICs and their older integrated NICs. If you need to support only the older versions, you should remove the updated RealTek drivers from the NIC_Drivers folder. - Automation for a full BTS DriverPack slipstream has been removed. In place is the old style "pause and wait" where you must perform the slipstream/integration on your own. - The nLite sample .ini file has been updated to reflect nLite V1.0 RC6. - Added Restricted Sites Zone protection to the cmdlines.reg registry tweak file.