CompuServe Thread

Hey Don, As things were left in a bit of scramble, some clarification is in order. There is a way with MSDOS.SYS to set up Win 95 so that it either boots to Win 95 or DOS straight. I've spent some time with WFDOS and if you use the Basic Redir the overhead is not bad and it works quite well in a dual boot configuration. NT and WFDOS are a natural. Win 95 is great for what it is but it doesn't facilitate being a DOS server with any great ease. WFDOS is workable and appears to be able to handle the render traffic o.k. I haven't gotten the CD situation worked out entirely but adjusting the Files and Locks attributes in SHARE.EXE should do the trick. The setup on WFDOS is manual and a bit tedious. There is a popup to help but you can't use a mouse. I just built several batch files, one for SHARES and one for USES. Unlike Lantastic it doesn't have a batch builder and overall is pretty primitive. But it does appear to do the job and satisfactorily. The easiest combination to setup is NT and WFDOS. But there are some advantages to using Win 95 as you can run 3DS from within quite easily. It does seem less responsive and the mouse isn't as responsive but its probably worth it. I prefer using a two system approach with two SVGA monitors, one running 3DS and one running Win 95 or NT. WFDOS works fine, not quite as well as Lan 6, but that is offset by the responsiveness of Win 95 and NT 32 bit drivers to some degree. I don't presume this to be the last word on the best setup but it does seem to be the best overall approach as its about as clean as it gets. The Win 95 CD has alot of valuable information on networking etc. which is well worth checking out. It explains how to setup MSDOS.SYS for instance to get a dual boot etc. Hope this has resolved the tangled mess created earlier and will put you on the right course. Alex