IWETHEY v. 0.3.0 | TODO
1,095 registered users | 0 active users | 0 LpH | Statistics
Login | Create New User

Welcome to IWETHEY!

New I see.
No, the evil behaviour of which you speak is common to 95, 98, ME, NT and 2000.

Crap in the registry is *always* preserved when you choose to "upgrade" an existing installation.
Shill For Hire
New I have to do a lot of reinstalls . . .
. . . with the registries removed because many of my clients would "have a hard time finding all those disks" to reinstall the software.

I've developed various techniques for preserving the desktop, start menus, DLLs, Fonts, etc., but If a program can't reestablish it's registry entries, I just tell them "well, that's the breaks". Office 97 is never a problem, but Office 2000 is a "reinstall from original media" every time.

"Well, could you just, you know, sort of get it on there for us, somehow?"

"Sorry, we run OS/2, so we don't have any of the Microsoft CD-ROMS. You'll just have to 'find' yours".
New Well, W2K improves one thing
It breaks the user profile information out of the %SYSTEMROOT% tree and into a top-level directory called "Documents and Settings", located on drive C: usually.

But as for people who have Software-With-No-Obvious-Purchase-Order-Number installed, they're screwed and they're going to get more screwed with the arrival of Office and Windows XP.

The reason you have to install O2K from the original media is that you've destroyed the MSI entries in the registry; now O2K doesn't know what's installed and what isn't, so you have to reinstall it.
Shill For Hire
New MSI Entries
I learned far more than I wished to know about MSI Entries when a client:
  • Had problems with Office 2000 Pro bombing out.
  • Attempted to reinstall from a set of Office 2000 Small Business CD-ROMS.
  • Called Automation Access
Yes, the era of "casual licensing" is drawing to a close, at least as far as Windows software is concerned.
New Which is why
I am suggesting StarOffice to any clients that wish to use Office software.

I also can make backups of their CD disks. I suggest that they store the originals in a safe place and install from the backup CDR disks. That way if they lose the CDR disks, or break/scratch/whatever them they will always have the originals to work from. Of course not everyone takes my advice.

A few Windows 95, Office 95, etc CDs went walking away from my place one too many times. So all recent software gets copied to CDR, unless it is copy protected or something. After looking all over for them and tearing up parts of the house, I am convinced that someone walked off with them. That is what I get for leaving the CDs in a CD Tower near my computer area instead of locked in a safe or fire-proof box. :(
"I can see if I want anything done right around here, I'll have to do it myself!"Moe Howard
New CDs have legs
I warn my clients about this. Some pay attention, some don't. those that don't have no Windows CDs within a weeks or two. Hiding them in a drawer that isn't locked is the same as leaving them out on the counter. Office is just about as bad.

This leaves me in the position of reinstalling Windows from my own CD-ROM in many cases, but, if Windows will run I can get the customer's reg number with regedit, and if it won't, I boot on a floppy and search the registry with XTree to find it.
New Which is why we have an IS-Library at work
A file cabinet cataloged by an Access database that has the registration keys in it and the location of each software and who checked it out last. The IS Secretary (we keep losing them, they either get moved to the Helpdesk or they quit for a better job) takes care of it and monitors who has what software. CDs do have legs and can walk out of the office, never to be seen again.

Who takes them? I have no idea. Must be the King of the PATATO-People! :)
"I can see if I want anything done right around here, I'll have to do it myself!"Moe Howard
New Incidentally, were did the NT CDs you are installing at...
home come from? :)

Sorry, I know they're just copies.
New You want the truth?
They came from the MSDN Library, and are backup copies. I am using them to learn how to develop under Windows 2000 and ".NET" as well. They are not on the same network as my work computer, so Microsoft should not have an issue with them.
"I can see if I want anything done right around here, I'll have to do it myself!"Moe Howard
     DOA Windows 2000 Server hard drive - (orion) - (17)
         2000 is Plug-and-Pray . . . - (Andrew Grygus) - (11)
             Eh? - (pwhysall) - (10)
                 I presume 2000 . . . - (Andrew Grygus) - (9)
                     I see. - (pwhysall) - (8)
                         I have to do a lot of reinstalls . . . - (Andrew Grygus) - (7)
                             Well, W2K improves one thing - (pwhysall) - (6)
                                 MSI Entries - (Andrew Grygus) - (5)
                                     Which is why - (orion) - (4)
                                         CDs have legs - (Andrew Grygus) - (3)
                                             Which is why we have an IS-Library at work - (orion) - (2)
                                                 Incidentally, were did the NT CDs you are installing at... - (a6l6e6x) - (1)
                                                     You want the truth? - (orion)
         Have you actually run chkdsk /f? - (pwhysall) - (4)
             I think you're on the right track. - (Another Scott)
             Was not able to run chkdsk /f at all! - (orion) - (2)
                 Install sets - (qstephens) - (1)
                     That is very much what I am doing - (orion)

He’s big and he’s in the vomit!
53 ms