--------------- FIDO MESSAGE AREA==> TOPIC: 206 WINDOWS 32BIT Ref: EAI00001 Date: 06/12/97 From: NUNO FILIPE Time: 05:36pm \/To: CHRIS HOLTEN (Read 5 times) Subj: Problem > NF> P.S.- Winfossil doesn't work in NT? What should I > NF> do???? I mean... I a need a fossil driver... :) > Brian Woodruff has a Winfossil Beta 3 for Windows NT on his website > (WWW.WOODRUFF-SOFTWARE.COM). It will work in NT 4.0. Hey, thanks!!!! :) I'm having a few problems configurating Windows NT Workstation 4.0 Codepage. For default, the codepage is 437 :( but I need 860, or if 860 isn't possible 850. Can you help me?? :) NF --- FMail/Win32 1.22 * Origin: Files 'R' Us BBS * Esmoriz * 056-754530 * 22h/8h * 33.600 (2:361/46) --------------- FIDO MESSAGE AREA==> TOPIC: 206 WINDOWS 32BIT Ref: EAI00002 Date: 06/13/97 From: CHRISTER SOLSTRAND Time: 01:08am \/To: GUY BARON (Read 5 times) Subj: 95 registry GB> Hi everybody ... upon installation of windows 95 on my assistants GB> pc I got a message after several power down .... something like GB> `missing registry` GB> Am I facing an intermitent hard disk problem ? any comments ... Maybe. I had a similar problem, but it turned out it was a crack in the motherboard. Incompatibilites between the motherboard and Windows 95 can also be the problem, especially if the hardware's old. Also check the disk controller. GB> Also ... I would like to know if the registry is kept within the GB> windows directory ... Yes, it is. The registry are the two files SYSTEM.DAT (or SYSTEM.DA0, don't remember) and USER.DAT (USER.DA0). ------ remiel ----------------------------------------------------------------- ?pu gnikcab yb naem uoy tahw siht sI --- BBBS/NT v3.33 How-D * Origin: Dalen BBS - +Bergen/Norway+ - <+47-55167262> (2:211/35) --------------- FIDO MESSAGE AREA==> TOPIC: 206 WINDOWS 32BIT Ref: EAI00003 Date: 06/13/97 From: CHRISTER SOLSTRAND Time: 01:08am \/To: JIM WARGULA (Read 5 times) Subj: Defragmentation prog [Defragging NTFS partitions] JW> CS>It's not very difficult, but you need another harddisk. I JW> CS>copied all files on my harddisk onto another, deleted them from JW> CS>the first one (quickformat), and then copied them back. Worked JW> CS>very nicely. JW> That is not difficult, just impossible! ;) Oh? Why is that impossible? ------ remiel ----------------------------------------------------------------- "He's dead, Jim. Hey! @to@, stop that!" --- BBBS/NT v3.33 How-D * Origin: Dalen BBS - +Bergen/Norway+ - <+47-55167262> (2:211/35) --------------- FIDO MESSAGE AREA==> TOPIC: 206 WINDOWS 32BIT Ref: EAI00004 Date: 06/13/97 From: CHRISTER SOLSTRAND Time: 01:08am \/To: NUNO FILIPE (Read 5 times) Subj: Problem NF> The problem is that the code page installed is 437. I want to use NF> 860, but the system said that it is an invalid code page. When i NF> type in msdos prompt "mode con cp select=850" it works, but if i NF> put this in c:\winnt\system32\autoexec.nt it doesn't work! How can NF> i solv this problem???? :) You need to set up the correct country locale in the Control Panel/Regional Settings. For some strange reason, NT sets the country locale to English, no matter which keyboard layout you specify when installing. Set the country locale to the one you want (France?), and make sure the checkbox in the lower left corner is checked. Then click Apply, and when NT asks if you will restart the system, do it. After that, it should work. NF> P.S.- Winfossil doesn't work in NT? What should I do???? I mean... NF> I a need a fossil driver... :) Sorry, can't help you on that one. :( ------ remiel ----------------------------------------------------------------- "Forklar mer!" - Thomas H|ifors --- BBBS/NT v3.33 How-D * Origin: Dalen BBS - +Bergen/Norway+ - <+47-55167262> (2:211/35) --------------- FIDO MESSAGE AREA==> TOPIC: 206 WINDOWS 32BIT Ref: EAI00005 Date: 06/13/97 From: CHRISTER SOLSTRAND Time: 01:08am \/To: BOB DAVIS (Read 5 times) Subj: Substing in NT BD> CS> NET USE M: \\NIDHEIM\M /Y BD> CS> And I received the following error message: BD> CS> The local device name is already in use. BD> You're trying to make M: refer to two different locations. That's BD> impossible. M: must refer to a drive\directory combination on your BD> local machine or a share location on another machine, but not BD> both. The subst command is for local mapping. The NET USE BD> command is for remote mapping. Which one are you trying to do? Both. I need C:\COM to be M: on my local machine, and I need to map C:\COM (on the local machine) to M: on the remote machine. BD> I've been following this thread and its not clear exactly what you BD> are trying to do. I need to get the local substing (M:) mapping to appear shared on the remote machine as M:, in order to get my mail reader working on the remote machine _without_ having to create to sets of configuration files. ------ remiel ----------------------------------------------------------------- "Tro det eller ei... det stod *10* stk!" - Thomas H|ifors --- BBBS/NT v3.33 How-D * Origin: Dalen BBS - +Bergen/Norway+ - <+47-55167262> (2:211/35) --------------- FIDO MESSAGE AREA==> TOPIC: 206 WINDOWS 32BIT Ref: EAI00006 Date: 06/13/97 From: CHRISTER SOLSTRAND Time: 01:08am \/To: CHRIS HOLTEN (Read 5 times) Subj: Substing in NT CH> CS> And I received the following error message: CH> CS> System error 85 has occurred. CH> CS> The local device name is already in use. CH> That indicates to me that the SUBST command is probably working CH> perfectly fine for you Christer. In your .BAT file, SUBST is CH> already mapping the c:\com directory to the logical M: drive, CH> which would be why you are getting the error message when you try CH> to map to that logical drive letter using the NET USE command. NET Yes, SUBST is working, but NET USE isn't. CH> USE will not override a SUBST logical drive mapping. My advice to CH> you would be to just go to the M: drive and do a DIR. According to CH> every thing you are doing in the above batch file, and the error CH> message you are recieving from NET USE, you have to have an M: CH> drive mapping, probably from SUBST. It may not be the logical CH> mapping you want, but you have some kind of an M: drive or you CH> wouldn't get the error message you are getting from NET USE. I have the M: drive, and it is like I wanted it to be. CH> I think this has become quite bit more complicated than it really CH> is Christer . Indeed it has. :) But I still haven't found a way to share the mapped drive on the network, and map it as M: on the remote machine. Or am I supposed to use NET USE on the remote machine, in order to get the local M: to the remote? ------ remiel