RogueSpear

Seems like a publicity stunt more than anything. Here we are talking about it right? I've been a big Microsoft proponent for years (decades actually), yet I can't get excited about anything Microsoft is doing at all lately. Call me wrong, negative, out of my mind, whatever.. but all this fluff lately seems like the beginning of the end to me. Like their best days are now behind them. I'll be hanging on to XP Pro with a death grip and I'm already phasing out Office.

Update - 20060321 Removed DVD43 V3.7.0 Removed DVDFab Decrypter V2.9.7.2 Removed DVD Decrypter V3.5.4.0 Removed DVD Shrink V3.2.0.15 Removed EULAlyzer V1.1 Removed Microsoft AntiSpyware Beta V1.0.701 Removed Microsoft Photostory 3 Removed Paint.NET V2.6 was a POS installer - use the installer by godan Removed PowerToy - Color Control Panel Applet Removed PowerToy - RAW Image Viewer V1.0 Build 50 Removed PowerToy - SyncToy V1.0.0.64 Removed Spybot - Search & Destroy V1.4 Removed SpywareBlaster V3.5.1 Removed Winamp V5.21 Removed Windows Defender V1.1.1051 Beta 2 Removed Windows Journal Viewer V1.5 I guess I didn't realize how many people use these things. After so many requests, I've decided to keep most of the installers up. I am taking down some of them down however. Anything that is not free, could get me in hot water with the MPAA, requires a WGA check to download from Microsoft, or has a - generally speaking - creepy EULA, is no longer available.

I've switched over to freeware / Open Source everyplace that I possibly can. Just about the only left that involves licensing now is Windows itself. I do have the oddball machine here and there with Photoshop or something like that, but not enough to warrant specific software. It's been quite an interesting time converting everything over, but now that it's done I'd never go back.

This is actually what I do for about 95% of the shortcuts not associated with an installer. Quite a bit easier too.

Here's a little VBscript for creating a shortcut: On Error Resume Next Dim ws, fs, progdir, strPrograms, scut1 Set ws = WScript.CreateObject("WScript.Shell") Set fs = CreateObject("Scripting.FileSystemObject") progdir = ws.ExpandEnvironmentStrings ("%PROGRAMFILES%") strPrograms = ws.SpecialFolders("AllUsersPrograms") Set scut1 = ws.CreateShortcut(strPrograms & "\Internet\Windows Messenger.lnk") scut1.TargetPath = (progdir & "\Messenger\Msmsgs.exe") scut1.Save I've never tried this with the file missing so I can't say for sure if this will work. When I use code similar to this I always put in an IF EXIST. So it may work, it may not. The first line will suppress any error messages.

I was big into programming years ago. When I say years ago, I mean like 15 to 20 years ago. About 2 years ago I started to fiddle with VBscript and just this year, a little bit of AutoIt. My HTA utility, like your utility, does the job. But I've been desperately searching for the time to immerse myself in VB.NET. I know it's not C# or C++, but it should be flexible enough to allow me to make the kind of tools I want. And it has some relation to VBscript, possibly making it easier for me to master. I'll probably look at this as one of the first projects to try in VB.NET since I have the mechanics down already. I have to say it's kind of amazing what a little bit of batch coupled with NSIS is capable of doing Regarding Delphi. I know it's a well regarded development environment, but personally I'd stear clear of anything having to do with Borland. They currently have all of their development tools up for sale so they can concentrate on something else. I don't remember what the something else is at the moment. It seems odd too since developer tools is really all they're known for.

By default any user can add ten (10) computers. Not sure how MS came up with this number..

I think you have a pretty promising little tool here. I'm not sure what you're developing your utility with, but if it's VB or C# or something from Microsoft, you could easily adapt my code to eliminate the dependance on outside utilities for renaming a computer and the user stuff too.

@Major, I'm sorry I meant to directly respond to that issue yesterday and forgot. The error compressing that file has nothing to do with DP broadband. It's an error that I get on my work laptop, just as you describe. I don't get it on my work or home desktop computers. I have no idea why this is, but I'm basically chalking it up to a bug in Microsoft's utility. Regarding the Moto support - click on the link for the Support List and you'll see support listed for SB510x. The x is a wildcard meaning either 0 or 1

I made a similar utility using an .hta script. I really like the clean look of your utility and the fact that it's an .exe file. Any chance you might be able to enable naming the computer from the same interface? Here's a link to the thread where I posted.

DriverPack Broadband V1.3.2 /B Support List File size: 2.53MB MD5: FBB43497B6E6BBA5860DAD4489BBAB96 Last updated: 20060320 Notes: Drivers needed for cable modems and ADSL modems. Support documentation rewritten to an HTML file that is based on the same HTML file Bashrat uses with the official DriverPacks. I showed him what I had made up and we have his permission to use his file as a template. Any feedback on whether users like or dislike the new support file would be appreciated. If the regulars here seem to be in agreement that this is a good thing, I'll work on converting over the remaining files. If not, we can always stick with standard text file. This DriverPack is not nearly done. I did a little searching around and can't believe how many companies manufacture broadband adapters. Absent and still to add: 3Com, ActionTek, Intel, Toshiba. -Maintenance: Updated the Motorola SURFboard support list for directory M\4. -New: D-Link DCM-200, DCM-201, DCM-202, DSL-100D, DSL-302G Rev. A, and DSL-302G Rev. C. -New: Linksys BEFCMU10 Ver.4 and WCG200 Ver.2. -New: Motorola SB4000 and SB4220. -New: Netgear DG632. -New: SMC EZ Connect 8004CM and 8013WG.

Yes, that's exactly where they are. Just throw 'em in i386 and restart BINL.

You see msi technology is weird. I haven't quite figured it all out yet. When you install things, be it through a flat .msi file or a switchless silent installer, the install process throws some stuff in %SystemRoot%\Installer. This directory is superhidden. It appears to contain .msi files, icons for the ARP listing, and some other odd data files. What seems so strange to me though is that some of the .msi files in there seem like they were generated upon installation of an app using a switchless silent installer. Sort like a reverse process of the /a switch. If advertising applications works for you, that's great. Unfortunately for me, even now in the year 2006, some people have been using a computer in the daily lives for over 10 years and they still don't know the difference between "Logoff" and "Shutdown" when I tell them to reboot. I see this both at my main job and at client sites. Money being spent hand over fist, but no money to properly train the employees. If I advertised applications, it would more than likely generate dozens of support calls.

Removed

I've always made my own VBscript for use with cmdlines.txt to get around the problem with quotes (and some other limitations as well). If you're not handy with VBscript, I'm sure batch could accomplish the same thing for you.

I'm not sure where things stand with the reboot into safe mode issue, but there appears to be a utility that can automate booting into safe mode and then again back into normal mode.

Well when you "assign" an application to a computer and the shortcuts are advertised, I've seen it where every single launch of the application will trigger an msi action. And this isn't even just with repackaged apps either. Problem #2: Advertised shortcuts frequently cause the same problem if you make a switchless silent installer out of it. Considering the is no purpose whatsoever to an advertised shortcut, other than if you actually advertise the program, I see no reason keep the shortcuts as advertised. I have to be honest, you are the first person I've ever encountered who deploys applications in this way. Most admins know what they want installed on the computers in their network and simply assign them to domain or the OU, taking any user interaction (or lack of action) out of the equation.

Fantastic work

I think that the time it takes for setup to crawl through all of the directories and inspect all of the .inf files for every single device installed greatly exceeds the time it takes to decompress 7-Zip archives from the CD to the hard drive. There are some circumstances where having them all on the CD is appropriate. It depends on who the computer is for and what their skill level is, but for me a straight Method 2 seems to be the best balance.

While I still sometimes use this method myself and find it quite useful under certain circumstances, you should be aware that this can add A LOT of time to your install. Further, if you keep the CD in the drive and go to install, as an example, a web cam. When you plug the device in, Windows will search out the entire directory structure of the drivers on CD. This can sometimes go on for 5 minutes.

BTS is planning to add RIS support, including extra NIC drivers, into his next gen slipstreamer. I included auto integration of NIC drivers in AutoRIS. If you like you can simply grab the drivers from there and add them in as you see fit.

I've been administering AD environments since Windows 2000 was around SP1 and advertised shortcuts are nothing but trouble. Now I never deploy apps through a GPO any other way than computer assigned. But back on topic. Advertised shortcuts in repacks that are made into switchless silent installers is a huge no no. All of the .msi files that I have posted for download use unadvertised shortcuts and I use them daily in AD environments. So they really aren't mandatory. Perhaps they are mandatory if you advertise the app rather than push it.

Indeed, I often have applications install to somewhere other than default. I just don't see the need for a couple hundred individual directories inside of %programfiles%. More importantly, I often repackage applications in order to get the settings the way I want them. Whether it's for enhanced security or privacy, or to just get rid something annoying like ads. The other benefit of course is file size. Whichever compression product gives me the smaller size is what I use for any given installer. I'm definately not loyal to one or the other, but if you can figure out how to make an installer with WinRAR, then you certainly shouldn't have a problem making one with 7-Zip. Yea it tends to go quicker making them with WinRAR. Sheer laziness and having no pride in your work is what would lead someone to never investigate all possibilities.

I'm not very familiar with the differences between the two. Does the original offer all of the functionality of the new? If the functionality is present and there aren't any compatibility issues, I'd stick with the original control panel.

Perhaps they're close to releasing an update. I can't imagine if someone were to be making use of the Driver Packs in their project that they wouldn't at least check in here every now and then to see what's going on.