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: Dave Hanson who wrote (3101)	10/18/1998 11:30:00 PM
From: Dan Spangenberg	Read Replies (2) \| Respond to of 14778

Is the partition readable locally at the server? Do you get any errors when formatting? Is it FAT or NTFS? If it is a partition on a larger drive, what happens if you incorporate the problem space into one of the other partitions? Does it error out then? I would try recreating is as a smaller size, maybe two partitions instead of 1 to test it. Is it any different if you log in as an administrator? Short of checking all of the user permissions and sharing setup, I can't think of anything, other than hardware, that would cause that error. Never seen that before, but I'll think about it for a while. Good Luck Dan

To: Dave Hanson who wrote (3101)	10/19/1998 12:40:00 PM
From: Spots	Read Replies (1) \| Respond to of 14778

>>silly NT network/disk error A shot in the dark. If you had a configuration in the past in which your M partition was something else other than a hard drive partition, you might still have a specification for it somewhere that causes the type of error you describe. The "something else" I have had problems with were CD-ROMs and old network drives. Both of these drive letter assignments can leave their footprints behind to conflict intermittently with a hard disk partition that later gets the same drive letter. Suggestions: Search the registry for "M:". This may lead you to something. Check your network drive assignments to see if M: is assigned as a network drive. This may or may not be visible, but M: will almost certainly appear in the registry if there is an old assignment. A CD-ROM problem that once drove me nuts apparently had to do with the CD player from Power Toys remembering an old CD drive letter which had been reassigned. Good luck. Spots