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: Zeuspaul who wrote (7429)	5/8/1999 3:04:00 PM
From: Clarence Dodge	Read Replies (1) \| Respond to of 14778

ZP Hey...good to hear from you:-) You must really be cranking out those corbels<g> Thanks for confirming my decision to opt for one 'active' OS. The 2 OS setup was not practical, although I'm glad I experienced how not to have a multi drive machine configured wwithout doing any damage. I see no reason to delete the OS from the SCSI drive. It functions as an alternative boot if you ever need one. ok... thats the only reason to keep it that I could think of. I think I'll slim it down a bit though. If you have considerable effort in the existing SCSI TA install you may want to consider keeping the existing TA install..or at least the data that you have accumulated. All I need to keep is the EOD data download file. the rest can be reinstalled from C:. I'm thinking making a copy of that file and temporarily taking that copy off E: ( the scsi drive), doing the uninstall and put the data file back in the same place before going to C: to reinstall TA. If NT is installed on the IDE drive and TA is 'installed' on the SCSI drive when is the SCSI drive accessed? Maybe the app will run faster. NT may work from the IDE drive and the TA app may access the SCSI drive for data searches? This sounds like the most likely procedure. or is the entire TA app called into RAM? only accessing the page file when you have insufficient RAM? I don't know.. ,i>If you have NT installed on the 'C' drive and apps installed on the 'D?" drive. Make Drive Images in pairs...one for the 'C' drive and one for the 'D' drive. Good point... question: when I need to restore, say the C: image file, should I automatically restore the E: (your reference D:) as well even if not needed? Spots has also recommended making a copy of the new C: install including critical apps to run in event of a prolonged down time. I think thats an excellent idea. Especially since that hidden copy of KOT came in so handy the other week. I'm waiting for Spots to talk more about where to put this copy of the new C:. He seems quite busy with work these days. I said on another removable drive for safety. He said no, put it where no changes have to be made to boot to it. Which I guess would mean also on the same C; as the original. As I said, I waiting for him to get back but my experience with the KOT boot failure says but the new C: copy somewhere other than on C:. Whats your thinking on this?