[ Quoting KENNETH ABRAMS to SCOTT LITTLE ] 
 KA> I've run a bbs. I've cosysop'd another bbs. I manage a network at
 KA> work.  All the drive assignments in each of these cases has always
 KA> remained  consistent once each system was initially setup. What are you
 KA> doing to  your system that causes your drive lettering to constantly
 KA> change? And  why?
Mine has remained consistant for a while, (except for the CDROM). But if
I decide I want to move the filebase to a new HDD (when I get one), I'd
either have to reconfigure EVERYTHING, or simple change the SUBST or share
names to match the move.
 
 KA> different OS under which some drives are invisible. If you're talking 
 KA> about a network situation, can't you map network drives to whatever
 KA> you  need?
My BBS is currently on the C: drive (and the messages are on E:) of the 486.
If I log onto it locally, it still expects to find it's files on C and E.
Same type of thing with the CDROM.
Trust me, I had my system set up with permanent, real pathnames before, and 
t
is not multinode/network friendly, and it's a major pain to change the
location of anything.
Regards,
 - Scott
[ admin@cyberia.asstdc.com.au | www.asstdc.com.au/~cyberia ]
--- FMail/2 1.22
3:712/848)
---------------