Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Pastimes : Dream Machine ( Build your own PC ) -- Ignore unavailable to you. Want to Upgrade?

To: Spots who wrote (6259)	2/13/1999 9:51:00 AM
From: Clarence Dodge	Read Replies (1) \| Respond to of 14778

Spots never apologize to anybody Sorry bout that<g> try a couple of other recoveries first (primarily, a register restore). (When you feel up to it) could you outline the register restoration procedure? HKEY_LOCAL_MACHINE\Software\Windows\CurrentConfig\Run which has entries that are run when Windows starts. If you remove a trouble maker, you can reboot and delete it. There's another in HKEY_CURRENT_USER. Thats a start...if I knew what the fructose you were talking about <g> backup a little, please.. Clarence

To: Spots who wrote (6259)	2/13/1999 10:40:00 AM
From: Sean W. Smith	Read Replies (1) \| Respond to of 14778

HKEY_LOCAL_MACHINE\Software\Windows\CurrentConfig\Run which has entries that are run when Windows starts. If you remove a trouble maker, you can reboot and delete it. There's another in HKEY_CURRENT_USER. Thanks I've always wondered where the "Inivisble startup folder" lived. Fruthermore which most already know for 16 bits apps. they like to add an entry run=XXXXXXX or load=XXXXXX in the win.ini or system.ini yet another place to look for culprits... Sean

To: Spots who wrote (6259)	2/14/1999 11:59:00 AM
From: Zeuspaul	Read Replies (1) \| Respond to of 14778

Third, sounds like you used ZP's KOT idea exactly as he proposed it Actually the latest KOT concepts have evolved..and there are several variations on the theme. Clarence has implemented a strategy that includes some of the original proposal..whatever that was.. My concept is to work a system without floppies..ie all restore options available from the keyboard. There are limitations to the idea as the latest restore illustrates. Clarence used floppies (good choice, he had a non floppy alternative, just in case the DI floppy was kept near the IBM reference disk floppy that is still missing) as Drive Image is not an NT executable. Just another one of those NT road blocks..add it to how do you do a straight forward NT install to a harddrive >8.4 GB My only variation on it would be to try a couple of other recoveries first (primarily, a register restore). Actually, I would try an uninstall first,just as you did. Agree..fix it if you can I'm not against the clone idea at all. If it's a fresh clone, it's probably the simplest solution. As you proceed, though, the clones themselves take more and more managing, and they're not small. Agree..The early clones are good to keep around as they are 'clean' installs. Keep a couple of the early builds around as they are small and basic and fit on a CDR. The decisions are not as easy as the build becomes more sophisticated. Yesterdays restore option would be nice to have in the mix..but unlikely without an automated DI option and possibly a third dedicated harddrive. Clones/images DO NOT eliminate the need for understanding the workings of the OS. If a clone assists in a larger more complex build then it also increases the need for tools/skills/knowledge to maintain the build..just another tool in the box. Zeuspaul