Path: news1.ucsd.edu!ihnp4.ucsd.edu!swrinde!newsfeed.internetmci.com!news.mathworks.com!nntp.primenet.com!news.cais.net!van-bc!nntp.portal.ca!news.bc.net!unixg.ubc.ca!freenet.vancouver.bc.ca!gordonf
From: gordonf@vcn.bc.ca (Gordon Fecyk)
Newsgroups: comp.os.ms-windows.win95.misc,comp.os.ms-windows.setup.win95,comp.os.ms-windows.networking.win95,comp.os.ms-windows.apps.compatibility.win95,comp.answers,news.answers
Subject: Win95 FAQs and Answers Part 1 of 14: Administrivia
Followup-To: comp.os.ms-windows.win95.misc,comp.os.ms-windows.setup.win95,comp.os.ms-windows.networking.win95,comp.os.ms-windows.apps.compatibility.win95
Date: 30 Jun 1996 16:27:04 GMT
Organization: Vancouver Regional FreeNet
Lines: 259
Approved: news-answers-request@MIT.EDU
Message-ID: <4r69so$80p@milo.vcn.bc.ca>
NNTP-Posting-Host: opus.vcn.bc.ca
Summary: These postings list many questions asked in said newsgroups,
and answers them as best as I can. I make references to other
Web sites and FAQs when appropriate. Visit the WWW home of
this FAQ (http://www.intouch.bc.ca/win95) for the appropriate
links. This section is the 1st: Administrivia
X-Newsreader: TIN [version 1.2 PL2]
Xref: news1.ucsd.edu comp.os.ms-windows.win95.misc:111596 comp.os.ms-windows.setup.win95:10973 comp.os.ms-windows.networking.win95:7507 comp.os.ms-windows.apps.compatibility.win95:3572 comp.answers:15511 news.answers:61912
Archive-name: windows/win95/faq/part01
Last-Modified: 1996/07/01
Posting-Frequency: Every two months
URL: http://www.intouch.bc.ca/win95/faq1.htm
1) Administrivia, copyrights, etc
What are FAQs?
What is Windows 95?
Why did you write this FAQ about Windows 95?
Why did you cross-post this FAQ to all the .win95
newsgroups? (NEW)
Whose work did you include in this FAQ besides yours?
(UPDATE)
What other FAQs are out there?
What other resources are out there?
Whose trademarks did you use?
What restrictions do you put on usage of this FAQ?
----------------------------------------------------------------------
What are FAQs?
FAQs are Frequently Asked Questions. They're designed to
minimize traffic on USENET by providing answers to common
questions, before users post those questions on newsgroups. If
people knew about FAQs and used them, we wouldn't need
ridiculous high speed links just to distribute USENET news. Read
the FAQs when available. Save copies. Give copies to your friends
on disks (subject to copyrights of course).
Read all about FAQs and get others from mirrors.aol.com.
----------------------------------------------------------------------
What is Windows 95?
Microsoft's newest "low end" operating system for Intel based
computers. In my opinion, they designed it to wean DOS users off
that 20 year old operating system and into some current stuff. It
replaces DOS and previous versions of Windows entirely.
In addition to completely re-working the user interface, Win95
brings over large amounts of Windows NT technology, allowing
app writers to write for both operating systems. One of Microsoft's
requirements for Designed for Windows 95 products is that the
product must also run on Windows NT Workstation 3.51.
It also (supposedly) helps you manage your hardware, your
software, your time, etc better. It's also supposed to make you rich,
good looking, sexually irresistible, and permanently wonderful. Heh
heh...
----------------------------------------------------------------------
Why did you write this FAQ about Windows 95?
The traffic on comp.os.ms-windows.win95.misc is ridiculous, other
Win95 FAQs I read were too sparse, too technical, too
anti-Microsoft, or otherwise too un-useful for the common folk.
Also, Microsoft's FAQ, which shipped with the CD-ROM version,
was pathetic and full of useless crap. But ultimately, I wrote it for
the experience, so I can say, "Hey, I made a Web page!" I hope
this page is useful to you out there.
This FAQ tries to get the big questions answered while going into
some technical detail for those who care. Where content goes
beyond the scope of this FAQ, I link you to appropriate sites.
Why did you cross-post this FAQ to all the .win95
newsgroups?
Because I was asked to. One of the initial letters I received in
response to the FAQ was to have me post it in the FAQ archives
for news.answers, so non-WWW people could use it. And not
everyone has FTP either; people using the Vancouver
CommunityNet have no FTP access at all! Well to get in the
archives I had to actually post it to, not only news.answers and
comp.answers, but the groups directly concerned with the questions
in the FAQ. I wouldn't have received approval from rtfm.mit.edu to
cross-post if I wasn't supposed to.
----------------------------------------------------------------------
Whose work did you include in this FAQ besides yours?
These people:
Rich Graves: He runs the win95netbugs FAQ. He has excellent
tech information but is very anti-Microsoft. He heeds help; he
can't maintain the netbugs FAQ, so if you think you can do it,
ask him.
Jim Farewell: My boss, who allowed me all the resource
material from Microsoft he had, and his computers.
Creative Element: They run the Win95 annoyances FAQ, and
they have plenty of brute-force methods for making Win95
work the way THEY want it to work.
Richard Evans: Who lent me his web server space to allow you
all to preview this FAQ.
Glen Ninow: He runs The InterNet Store (With special
emphasis on the capital 'N' in 'InterNet') and graciously offered
his web server space to me for the permanent home of this
FAQ.
Ben Goetter: He is writing a book on writing MAPI applications
for MS Exchange, and has an excellent Exchange FAQ.
And then there are those who gave suggestions since the first
release:
Eric Gisin [ericg@unixg.ubc.ca] for many corrections and a
hack to MS's TCP/IP Properties sheet to let you make
adjustments without Registry hacking, and for the Emergency
Recovery Disk suggestions.
Ed Babin [ebanin@faa.gov] for some tape backup corrections.
Michael Thomas [mthomas@computerland.net] and too many
others not listed here, for encouragement.
Kurt C. Joseph [josephk@qnet.com] for the advice in running
Win 3.1 within Win95.
Jack H. Pincus [jhpincus@cris.com] for the good news
regarding Corel's version of WordPerfect for Win95.
William Hunt (E-MAIL address unknown) for the RNAAPP
lockup fix.
The brave souls who mail-bombed anyone who gave me sh*t
for cross-posting the FAQ. I got a couple of nasty responses
but I never heard from then ever again... heh heh heh... Perfect
example of how The Net polices itself.
The many many people who told me my downloadable copy
was MISSING! Ack! How can I screw that up? (Kinda proves
that we're all human, huh? We make mistakes.)
----------------------------------------------------------------------
What other FAQs are out there?
Too many... use them.
Win95 Net Bugs:
http://www-leland.stanford.edu/~llurch/win95netbugs/faq.html
Win95 Annoyances
http://www.creativelement.com/win95ann/index.html
The one on the Win95 CD-ROM even though it sucks now
Ben Goetter's Exchange FAQ:
http://www.halcyon.com/goetter/exclifaq.htm
Do a search at Infoseek where they seem to have a lot of dinky
sites, but nothing serious
----------------------------------------------------------------------
What other resources are out there?
There's Microsoft's Windows 95 Resource Kit, which makes a
great start, but will quickly become a doorstop after you get sick of
the sales talk in there.
Definitely check out the Microsoft Knowledge Base,
(http://www.microsoft.com/kb) which has a lot of stuff who you
might've thought only Technet users had access too. They recently
re-did their search engine, so you can search on phrases like
"Confirmed bugs" or "Bugs fixed", or "Files available for
download". This stuff is right to the point. If you don't use Internet
Explorer, visit http://www.microsoft.com/kb/softlib for a
non-IE-viewable page of software. MS's regular Win95 pages have
a bunch of tags that NCSA Mosaic barfs on.
Do a search on Infoseek or Yahoo! or wherever, for other Win95
pages. They're starting to show up finally.
I won't recommend any magazines as of yet, because they're all full
of MS ads and other un-productive junk.
----------------------------------------------------------------------
Whose trademarks did you use?
Windows, MS-DOS, MS Exchange, MS Plus, Internet Explorer,
DriveSpace: Microsoft Corp
NT: Northern Telecom (Go figure)
Norton Utilities, Norton Anti-Virus, Norton Navigator, etc...:
Symantec Corp
Colorado Backup: Hewlett-Packard Corp
Macintosh, AppleTalk: Apple Computer Inc
Pentium, Pentium Pro: Intel Corp
Netscape: Netscape Communications Inc
LANtastic: Artisoft Corp
Disk Manager: Ontrack Systems
DrivePro: Microhouse
Stacker: Stack Electronics
OS/2: IBM Corp
TCPMAN: Trumpet Communications
NetWare, MHS: Novell, Inc
CleanSweep 95, QEMM: Quarterdeck
SoftRAM: Synchronys Software (Evil, evil, evil, evil)
Award BIOS: Award software
MR BIOS: Microid Research
Sound Blaster (whatever kind), AWE32: Creative Labs
Graphics Ultra/Pro/Expression: ATI
WinCIM: CompuServe Inc
WinFax: Delrina Communications/Symantec
----------------------------------------------------------------------
What restrictions do you put on the use of this FAQ?
Currently I can't allow re-distribution of the FAQ because it is
under construction. Send me all your comments. Distribution and
mirroring are encouraged so long as the source is quoted (me!)
Disclaimers:
As MS fixes the bugs and as vendors come up with new products,
this info may be in-accurate. Check with other sources (like the
references above) if you are in doubt of any info I have here. I
would appreciate updates and comments and you will receive
recognition for your work.
The opinions in this FAQ are mine, except where directly quoted
and linked from. They do not reflect the opinions of my employer or
the provider of this web space. Especially as I often argue with both
of them about these topics.
I can't be responsible for any damage this information causes you or
your equipment. Try to avoid using REGEDIT. RTFM. RTFFAQ.
Ask Questions. But don't come crying to me or sic your lawyers on
me if you broke your computer. I can't fix it.
----------------------------------------------------------------------
[Back to Table of Contents]
--
============================================================// //========
= "I am Gordon of Winterpeg. Windows WAS futile." // // =
= Find out why: http://www.intouch.bc.ca/win95 // // =
= Personal E-MAIL: gordonf@vcn.bc.ca \\ \\// // =
= Home Phone: +1-604-526-8724 \\ XX // =
= \X/\X/ =
= "I am Hitler of BorgSoft. I am the middle inital of William H. Gates. =
= Your work will be Microsofted. Resistance is futile. Heil Windows. =
=========================================================================
Yeah I use an Amiga at home. If you don't like my computer, dial
1-800-DIE-BILL and tell someone who cares.
----------------------------------------------------------------------
Path: news1.ucsd.edu!ihnp4.ucsd.edu!swrinde!newsfeed.internetmci.com!news.mathworks.com!nntp.primenet.com!news.cais.net!van-bc!nntp.portal.ca!news.bc.net!unixg.ubc.ca!freenet.vancouver.bc.ca!gordonf
From: gordonf@vcn.bc.ca (Gordon Fecyk)
Newsgroups: comp.os.ms-windows.win95.misc,comp.os.ms-windows.setup.win95,comp.os.ms-windows.networking.win95,comp.os.ms-windows.apps.compatibility.win95,comp.answers,news.answers
Subject: Win95 FAQs and Answers Part 2 of 14: Installation
Followup-To: comp.os.ms-windows.win95.misc,comp.os.ms-windows.setup.win95,comp.os.ms-windows.networking.win95,comp.os.ms-windows.apps.compatibility.win95
Date: 30 Jun 1996 16:28:17 GMT
Organization: Vancouver Regional FreeNet
Lines: 673
Approved: news-answers-request@MIT.EDU
Message-ID: <4r69v1$80p@milo.vcn.bc.ca>
NNTP-Posting-Host: opus.vcn.bc.ca
Summary: These postings list many questions asked in said newsgroups,
and answers them as best as I can. I make references to other
Web sites and FAQs when appropriate. Visit the WWW home of
this FAQ (http://www.intouch.bc.ca/win95) for the appropriate
links. This section is the 2nd: Installation
X-Newsreader: TIN [version 1.2 PL2]
Xref: news1.ucsd.edu comp.os.ms-windows.win95.misc:111597 comp.os.ms-windows.setup.win95:10974 comp.os.ms-windows.networking.win95:7508 comp.os.ms-windows.apps.compatibility.win95:3573 comp.answers:15512 news.answers:61913
Archive-name: windows/win95/faq/part02
Last-Modified: 1996/07/01
Posting-Frequency: Every two months
URL: http://www.intouch.bc.ca/win95/faq2.htm
2) Installing Windows 95
Basics about Win95 vs Win 3.x and DOS you MUST know
How do I install Win95 on a computer with...
...nothing else on it?
...DOS and Windows 3.x on it?
...Stacker (tm) disk compression
...>500 MB drive running Disk Mangler, DriveLamer, etc
...Double/DriveSpace (tm) disk compression
...OS/2 (tm) ? (any 2.x or higher version)
...Windows NT (tm) ? (why?)
...no hard drive? (diskless station)
...notebook computer?
How do I install Windows 95 from...
...floppies?
...CD-ROM drive? (Harder than you think)
...network server? (including how to build a server based
install)
I'm having problems with...
...rebooting after first part of setup
...reading disk 2
..."Safe" recovery
...part two of setup can't read drivers from CD-ROM
...part two of setup can't read drivers from network
Can I install two separate copies of Win95?
How do I install old DOS and Windows 3.1 in a Win95
system? (NEW)
Why should I make a startup disk? (NEW)
Top ten installation mistakes
----------------------------------------------------------------------
Basics about Win95 vs Win 3.x and DOS you MUST know
(UPDATE)
Back up (Make a copy of) your hard drive first, if you don't know
what you're doing!
Windows 95 is a very different beast from Windows 3.1, different
from MS-DOS, different from anything else out there. Treat it like
Windows 95 and not like DOS, and it will install and perform like
Windows 95.
This is especially true with installation. Try to remove as many old
DOS drivers, TSRs, disk compressors, disk managers, etc before
attempting to install. Normally, Setup will recognize a host of such
programs and warn you to remove them before continuing. Heed
that warning! And if you have any doubts as to what Setup will do
to your computer, back up your hard drive first!
One very useful function of Setup is creating a Startup Disk to start
the computer from, in case Win95 can't start on its own. Setup will
ask you if you want a Startup disk just before it copies its files to
your hard drive. Make up a Startup Disk. You can even un-install
Win95 from this startup disk, provided you enabled Un-Installation
in Setup (If you installed on top of Win 3.1).
Another very useful tool, though it doesn't get built during Setup, is
the Emergency Recovery Disk. If you own a CD-ROM version of
Win95, copy the ERU utilities, from Drive:\OTHER\MISC\ERU to
your Win95 directory, after you finish installing Win95. Then, when
you want to make a recovery disk, run ERU.EXE. Afterwards, if
you ever corrupt your Win95 setup, run ERD.EXE (the DOS
program) to re-build the lost configuration!
----------------------------------------------------------------------
How do I install Windows 95 on a computer with nothing else
on it?
You need to prepare a File Allocation Table (FAT) partition on
your hard drive to install Windows 95 to. The first bootable
partition must use FAT file system, regardless of where you install
Win95. If you bought the Win95 package designed for PCs without
Windows (meaning NOT the UPGRADE) it will come with a
startup disk for this purpose. The startup disk works much like the
setup disk for MS-DOS 6.22; it will create a partition and format it
for you. The disk also contains the traditional MS-DOS utilities like
FDISK, FORMAT, SYS, HIMEM.SYS, to do this manually.
It will then ask for Setup Disk 1 or the CD-ROM, which installs the
Win95 setup wizard to take you the rest of the way.
NOTE: Some OEM CD-ROM distributors might not have
included an MS-DOS driver for the CD-ROM drive on the
startup disk. If this is so, when the boot disk setup asks you for
the CD-ROM disk, it won't find it. Tell the manufacturer to
correct this. If you're adventurous enough to do this yourself,
the CONFIG.SYS and AUTOEXEC.BAT files on the boot disk
have instructions on how to add your DOS CD-ROM driver.
If you choose to install the UPGRADE version on to an empty
system, you will need a boot disk with the DOS utilities I
mentioned. You will also need your Windows 3.1 Disk 1, as proof
that you're eligible for the upgrade.
----------------------------------------------------------------------
How do I install Windows 95 on a computer with DOS and
Windows 3.x on it?
Most likely you will have the UPGRADE version of Win95, and in
the case of the CD-ROM version, you will already have a DOS
CD-ROM driver loaded and working. Microsoft recommends you
run Win95 setup from within Windows 3.1, which does work, but if
you plan on installing Win95 in a separate directory than your
existing Windows, you should run setup from DOS instead. Keep it
simple.
If you install from within Windows 3.1, and you choose to install on
top of your existing Windows, be sure to allow Setup to copy your
existing configuration in case you wish to un-install Win95 later.
A safer bet is to install Win95 in its own directory, which gives you
the option to dual-boot between your original DOS and Win95.
Un-installing then becomes a simple matter of "DELTREE
WIN95", and removing the remaining traces from the root directory
(including a "SYS C:" to restore the original DOS system files).
----------------------------------------------------------------------
How do I install Windows 95 on a computer with Stacker (tm)
disk compression?
Microsoft recommends to un-compress your drive before installing
Win95, but it does work with real-mode Stacker drivers. Just install
normally, but keep your real-mode Stacker disk drivers installed
when you do. You will lose performance on disk access as long as
you maintain your DOS version of Stacker. Otherwise the same
rules apply as for DOS and Windows 3.x.
----------------------------------------------------------------------
How do I install Windows 95 on a computer with >500 MB
drive running Disk Mangler, DriveLamer, etc?
These disk managers allow systems, that otherwise can't handle
drives with more than 1024 cylinders, to work with these drives.
They're typically larger than 500 megabytes.
Let me get this 1024 cylinder nonsense straightened out once
and for all. IBM compatibles, ever since the XT, cannot start
from a hard drive partition with more than 1024 cylinders,
even though partitions may exist beyond that and may even be
accessible after starting up. The original FAT file system
cannot exceed this 1024 cylinder limit either, and FAT
partitions can't go past cylinder 1024, regardless of the total
number of cylinders. Other file systems easily handle this, but
not FAT, nor VFAT (Win95). And no Intel-based PC on this
planet can boot from any hard drive partition that sits beyond
this limit, regardless of the file system!
Disk manager hacks and LBA translation reduce the number of
"logical" cylinders, and usually increase the number of
"logical" heads to compensate, in order for these lame PCs to
boot up from such a hard drive. Since LBA translation is built
in to most Intel-based PCs today, use it. Or upgrade your
BIOS. Don't use software to accomplish this translation, and don't
waste time with other software hacks or "magic" to work around
this.
Ontrack's Disk Manager (tm), and MicroHouse's DrivePro (tm)
work OK with Win95's 32-bit disk drivers, so you can install like
you could for an upgrade, but you should consider a BIOS upgrade
and a system backup before attempting to install Win95 on systems
with >500 MB hard drives. These disk managers can get wiped out
by a boot record virus, making your system un-bootable! On a
system that supports large hard drives by design, a virus strike will
not cause such damage (though it will do other nasty stuff of
course).
One precaution to prevent a virus strike (and other mistakes, like
booting off a non-system disk), is to set your BIOS to always boot
from drive C: (like C: first, A: second, or C, A) so your disk
manager software will always load before anything else does.
----------------------------------------------------------------------
How do I install Windows 95 on a computer with
Double/DriveSpace (tm) disk compression?
Simply perform your normal installation as per the Upgrade.
Win95 comes with 32-bit versions of the DoubleSpace/DriveSpace
drivers and they will un-load the real mode drivers from memory
when Win95 runs.
----------------------------------------------------------------------
How do I install Windows 95 on a computer with OS/2 (tm) ?
(any 2.x or higher version)
Microsoft does not support installing Win95 on systems with OS/2,
any version. Attempting to install Win95 on a system like this will
wipe out any capability of starting OS/2.
However, if you use Boot Manager, you can install Win95 in a
partition of its own, or in the same partition as MS-DOS. This will
isolate Win95 from OS/2. Setup will temporarily disable Boot
Manager by making the DOS partition the active partition. To
re-enable Boot Manager after installing Win95, run FDISK and
make the Boot Manager partition (the little 1 MB partition of type
Non-DOS) the active partition again. This also has the advantage of
using HPFS file system on the OS/2 boot partition.
Of course, installing Win95 on an HPFS partition is not possible.
Win95 doesn't have any HPFS file system drivers yet, though I'm
hoping for it.
----------------------------------------------------------------------
How do I install Windows 95 on a computer with Windows NT
(tm) ?
Supposedly, Setup will recognize NTLDR.COM and insert itself
into the list of OSes to boot from. As long as you have a FAT
partition to install Win95 to, this will work. Win95 does not support
installation on an NTFS partition either.
If you want to triple-boot between DOS, Win95, and NT, MS has
some wicked setup procedure that lets you use NTLDR to pick
your booting OS (like OS/2's Boot Manager). The details are in the
Win95 Resource Kit.
----------------------------------------------------------------------
How do I install Windows 95 on a computer with no hard
drive? (diskless station)
NOT RECOMMENDED, though it is possible. The big reason is
Win95 will use a network drive for its Virtual Memory swap file,
which will cause heavy traffic on the file server. Put minimum 16
MB memory on each diskless workstation, to minimize swapping to
the server. Also see How to prevent random hard drive access, to
further reduce server swapping.
To perform a diskless install of Win95, you need a server based
install already on the file server. You also need a real mode
connection to the network (either on a boot disk, or a virtual floppy
on the file server via a boot EPROM on the network card). You
merely install all the Win95 files into your home directory, wherever
that is. Unfortunately, this only works with real mode network
clients; you can't use 32-bit network components on a completely
diskless workstation.
If you use a boot EPROM, you need to make a virtual boot disk
with the Win95 system files (IO.SYS etc) on it. Use whatever
utilities come with your network server to do this. Other details are
in Microsoft's Knowledge Base article Q133349.
----------------------------------------------------------------------
How do I install Windows 95 on a notebook computer?
You merely install it on the notebook as you would on any other
computer. Because of complications with CD-ROM and network
support on some notebook computers, I suggest you use the floppy
disk version, then upgrade to the CD-ROM version once you have
all the hardware working on it.
Setup will recognize special brands of notebook computers
(Toshiba and Zenith for example), and you should change the
"Computer Type" if it did not. This lets Setup tune the power
management features to work with it.
----------------------------------------------------------------------
How do I install Windows 95 from floppies?
For basic systems, and notebooks, this is the best source to install
from. Setup will detect all hardware it can, and add protected mode
support for it. It does take a while to sit and flip disks, but you will
have a clean installation afterwards. This also gives you a good
excuse to delete or hide your CONFIG.SYS and
AUTOEXEC.BAT before running Setup.
First, boot to DOS, then run SETUP on disk 1. If you don't already
have DOS on the computer, boot using any DOS disk and prepare
the hard drive for a normal DOS installation. The Stand-alone
version of Win95 will have a boot disk for this purpose.
----------------------------------------------------------------------
How do I install Windows 95 from a CD-ROM drive?
(Harder than you think)
You need a real mode CD-ROM driver in place to run Setup
initially. My favorite method is to prepare a boot disk (or use the
boot disk from the non-upgrade version) which loads the
CD-ROM drivers, then runs Setup from the CD-ROM.) This way
there's no chance of Setup arguing with a CONFIG.SYS file on the
target drive.
A boot disk only needs these entries in CONFIG.SYS:
DEVICE=HIMEM.SYS
DEVICE=(your CD-ROM driver) /D:MSCD001 (and whatever parameters it needs)
And these lines in AUTOEXEC.BAT:
MSCDEX /D:MSCD001 /M:4 (and whatever preferences you have)
SMARTDRV 2048 2048
I suggest including SmartDrive to speed up the first part of
installation. Include SmartDrive AFTER MSCDEX so it can cache
the CD-ROM accesses.
----------------------------------------------------------------------
How do I install Windows 95 from a network server?
(including how to build a server based install)
Server based installs work like they did back in Win 3.1, but you
need to run a different setup program, NETSETUP.EXE, to install
the server copy. NETSETUP comes on the upgrade CD-ROM
version, and on the stand alone CD-ROM version, in
ADMIN\NETTOOLS\NETSETUP. It does not come with the
floppies or OEM CD-ROM. And you can't get it from Microsoft's
web site, either.
Perhaps the two best advantages of using NETSETUP to make a
server based install, are 1: you can do shared installs, saving local
hard drive space, and 2: you can apply service packs and other
components to server installs, which will take effect for server
based, and local installs. Service Pack 1 Admin Edition includes a
utility to apply the service pack to a server based install.
To use NETSETUP:
Install Win95 on one computer as a stand-alone, and install
network support for it so you can write to the server drives.
Run NETSETUP from the CD-ROM disk. It will list several
tasks you must do to complete the server install.
Do the first task: specify the target server and directory you will
install the admin copy to.
Do the second task: specify the source drive (usually the
CD-ROM) and install. It will perform three passes of installs;
one for stand-alone installs, one for shared installs, and one for
the initial setup files.
(optional) Write an installation script. The script editor is rather
simple; you use the option menus to turn options on and off, to
specify what network components to load, and settings for
them.
Done. Go to a workstation and run SETUP from the server to
test the install, and any install script you wrote.
One dumb thing about NETSETUP is you have to run it from
Windows 95, which means you have to install Win95 once, then
run NETSETUP on that station. NETSETUP will run in Windows
3.1, but you won't be able to create an installation script until you
run it from Win95.
You could also just share out the Win95 CD-ROM over the
network and run Setup from that, or copy all of the WIN95
directory to a single directory on the server, if you won't be doing
any shared or diskless installs.
NOTE: Installing the OEM CD-ROM version to a server using
NETSETUP does not entirely work! The OEM version includes
the MS Internet Explorer from Plus, and the PRECOPY.CAB
files contain references to those components. NETSETUP will
not attempt to install those, which is why MS didn't bother
including it with the OEM version. You could find out what
files it looks for and manually insert them, but that's a bit of a
pain. You'll just have to shell out the $250.00 for the
non-upgrade, non-OEM, Win95 CD-ROM. Installing the
UPGRADE version works, but it will bug you for Win 3.1
evidence before it will install.
I'm thinking about doing a server-based setup FAQ page because
of the questions about MSBATCH.INF and controlling installations
with it. There are, in fact, some pretty cool tricks you can do to
Win95's server based installations.
----------------------------------------------------------------------
I'm having problems with rebooting after first part of setup
On systems with bizarre DOS configurations, you may get a
"Windows protection error", or "This VxD conflicts with another
driver already loaded". This is because a DOS driver loaded before
WIN.COM loaded, and the protected mode driver can't load.
To avoid this, just when the computer reboots for part two of
setup, press F8 when you see "Starting Windows 95..." then select
"Safe mode command prompt only". From here, delete or hide your
CONFIG.SYS and AUTOEXEC.BAT files. Then re-boot and
proceed with part two normally.
You may get this error if you use an un-recognized CD-ROM
driver (Usually the case for IDE CD-ROMs), or if you use a DOS
network driver and a Win95 net card driver tries to load. The
above technique will work around both these cases.
If you have to do this, you won't be able to configure a printer or
copy any other drivers until you finish Setup. No matter; if it asks
you for Win95 files, just cancel, and wait until Setup finishes.
----------------------------------------------------------------------
I'm having problems with reading disk 2
The disks come in MS's new "DMF" format, which holds nearly 2
MB on a 1.44 MB disk. The first disk is a standard 1.44 MB disk,
and Setup loads a driver to read the DMF disks.
A DMF disk can get destroyed by a boot record virus, because the
virus over-writes the DMF boot record. As a precaution,
write-protect the floppies before using them. For some really dumb
reason, Microsoft insisted on shipping the disks write-enabled.
Setup will also try to write your registration info on disk 2. If you
have the disk write protected, you can just hit "Continue" and Setup
will continue without writing to the disk. For details, read KB article
Q136111.
----------------------------------------------------------------------
I'm having problems with "Safe" recovery
If you re-run Setup on a bad installation of Win95, you will get a
prompt to use "Safe Recovery". This will let you either Undo the
install, or Redo the install using safer detection techniques. My
suggestion is to Undo the install, then use the technique above,
regarding Rebooting after first part of setup. Also, try installing on a
target drive with no DOS startup files (CONFIG.SYS).
----------------------------------------------------------------------
I'm having problems with part two of setup. I can't read
drivers from CD-ROM
This means Setup didn't load protected mode CD-ROM drivers for
your drive, which happens for many reasons. This will only affect
your ability to add printer drivers and setting up MS Exchange,
both of which you can skip and do later.
You should make sure, after finishing Setup, you bug the CD-ROM
manufacturer for a Win95 driver. Also check the section on SCSI
and IDE CD-ROM support.
PCI IDE or PCI SCSI adapters won't kick in until the second
re-boot, so such CD-ROMs won't work until then. Just let it finish
and it will work.
Later on, if you have to use real mode CD-ROM or net card
drivers, you can add printers and set up Exchange once you can
use the CD-ROM or network again.
----------------------------------------------------------------------
I'm having problems with part two of setup. I can't read
drivers from the network
If you installed network support but you didn't get a network log in
at the start of part two (so you can access the file server), this
means the Win95 network support didn't install correctly. As per
the CD-ROM install, you can skip the Exchange and Printer setup
until you get the protected mode network support working.
PCI net cards won't operate at all until the second re-boot, when
the PCI Bus driver kicks in. Just let it finish and your net card will
work on the second re-boot. ISA PnP cards react the same way.
This could also mean you skipped network support to begin with,
or it could not load a network card driver. Again, you can skip the
Exchange and Printer setup until you correct this.
NOTE: There is a way to work around this minor problem; use
a real mode network client (Either NETX, VLM, or Workgroup
Connection for DOS) to run Setup from, and tell it to use your
Existing ODI or NDIS 2 driver. This is the default net card
choice if you install from a server-based copy. The second time
it re-boots it will read your real mode driver and add the
components needed to make it work with 32-bit network
software. Finally, after you log in to the server to continue
Setup, it will detect your net card and replace the ODI or NDIS
support with the appropriate Win95 support.
This method of loading network support for PCI and ISA PnP
cards can produce some unusual side effects. For example, if
you booted from a floppy disk to get on the network, Part 2 of
Setup will try to read the NDIS 2 or ODI driver from the floppy
disk! If this occurs you will get a "General failure reading
Drive A:" error message. When you do, re-insert that disk and
hit "Retry" so Setup will continue.
Another side effect is Win95 shutting down in the middle of a
driver file copy! To prevent this, make sure you erase this line
in MSBATCH.INF on the Server copy:
NoPrompt2Boot=1
This line immediately re-boots the computer after the end of all
the Setup Part 2 stuff. If you remove it, Setup will prompt you
to re-start the computer when it's all finished. You should wait
until Win95 detects and installs all other hardware before you
press "OK" on this requester. If Win95 asks you to re-start the
computer at any other time, tell it NO.
----------------------------------------------------------------------
Can I install two separate copies of Win95?
The problem with this is there's only one MSDOS.SYS file, which
points to only one copy of Windows 95. You could edit
MSDOS.SYS (which is just a text file in Win95) to point to either
copy, but this is annoying. A better technique is to borrow
someone's copy of OS/2 and install Boot Manager, then have two
bootable partitions, each with its own copy of Win95.
The first technique is great, however, for developers experimenting
with their apps, without destroying their primary copy of Win95,
and for those without friends using OS/2.
----------------------------------------------------------------------
How do I install old DOS and Windows 3.1 on a Win95
system? (NEW)
I do not recommend installing old DOS on a Win95 machine at all.
Win95's included MS-DOS 7.0, in Single Mode, can run anything
that previous versions of DOS can, including Windows 3.1 or
Windows for Workgroups! If you have to run old DOS programs
that don't run in DOS sessions in Win95, check out the Running
MS-DOS Games page.
With that aside, to install the missing utilities that DOS 7.0 blatantly
forgot from DOS 6.22:
Find the OLDMSDOS directory on the Win95 CD-ROM in
DRIVERS\OLDMSDOS, or download them from Microsoft's
web site.
Run the INSTALL.BAT from that directory, within Win95.
When asked to, shut down and re-start your computer. This is
because the old DOS programs are really from DOS 6.22, and
the batch file SETVER's them to that version of DOS.
You'll find other old DOS toys in the directories of DRIVERS,
including MSD and MSBACKUP.
To install Windows 3.1 or Windows for Workgroups on a system
running Win95:
Find your original Win 3.1/WFWG disks of course. Silly.
Exit to Single mode DOS by Start Menu/Shut Down, and
"Restart computer in MS-DOS Mode".
Make copies of any CONFIG.SYS or AUTOEXEC.BAT you
have (You shouldn't have these anyway!)
Run SETUP.EXE from your Win 3.1 disk 1 and install normally,
into any directory that Win95 isn't in! Like C:\WIN31
When Setup finishes, choose the option to Exit to DOS.
Make copies of any changes that Win 3.1 Setup made to your
CONFIG.SYS and AUTOEXEC.BAT, and restore your
original versions of these files. You'll need these copies later on!
Type EXIT to go back into Win95.
Find WIN.COM in your Win 3.1 installation, right-click on that
file, and hit "Properties".
Hit the Program tab, hit Advanced, hit "MS-DOS Mode", hit
"Specify new MS-DOS Configuration."
In the empty spaces below, copy & paste the text from the
saved CONFIG.SYS and AUTOEXEC.BAT that Win 3.1
Setup modified. CTRL-V works in these text boxes to paste
text from the clipboard in. Add a LOCK C: to the end of the
special AUTOEXEC.BAT (for 32-bit disk and file access, if
you wish to use it).
Modify the resulting text entries so you use the right versions of
these files. Finally OK everything.
Use Win95 versions (C:\WIN95\.....) of these files:
HIMEM.SYS
EMM386.EXE
SMARTDRV.EXE
Use Win 3.1 versions (C:\WIN31\... or C:\WINDOWS\...) of
these files (WFWG actually)
IFSHLP.SYS
NET START
MSCDEX (If you share a CD-ROM via WFWG)
When you double-click on WIN.COM here, or on its resulting PIF
file (Shortcut to MS-DOS program), your computer will re-start
using this special DOS configuration. When you exit Win 3.1,
Win95 will re-start. Trust me; this is the absolute best way to get
Win 3.1 working on a Win95 machine, if you don't have an older
DOS already installed.
NOTE: Windows for Workgroups, in particular, will ask you to
"Restart Computer" sometimes. This is fine; Win95 won't try to
re-start because a line in the special AUTOEXEC.BAT
(WIN.COM /EX) won't execute, and your computer will re-start
still using the special DOS configuration. The only way to get
back into Win95 safely, is to exit Win 3.1 with Program
Manager (File/Exit Windows).
Also notice, that you'll find files named CONFIG.W40 and
AUTOEXEC.W40 in your hard drive. These files are Win95's
DOS configuration. Leave them alone! Don't touch them!
Win95 copies these back to CONFIG.SYS and
AUTOEXEC.BAT when you finish with Win 3.1.
And don't try to install old DOS on a Win95 machine. Just don't.
You'll regret it. And don't ask me why. You'll regret hearing why.
Heh heh...
----------------------------------------------------------------------
Why should I make a startup disk? (NEW)
(Why didn't I think of this question? Thanks guys)
The startup disk contains a handful of basic utilities you can use to
fix your broken Win95 installation, and even un-install Win95. The
traditional DOS utilities for disk management are in there, as are a
version of EDIT, REGEDIT, and the un-installer.
To make a startup disk, answer "YES" to the question about the
startup disk. If you skipped this part and want to make up a startup
disk, run Control Panel, Add/Remove Programs, and hit the
"Startup Disk" tab.
Notes regarding REGEDIT on the startup disk
The version of REGEDIT on the startup disk only lets you import
and export Registry pieces (or the whole Registry) to text files you
can edit using good ol' EDIT. To build an editable copy of the
Registry, change to your Win95 directory and type:
REGEDIT /E REGBCKUP.REG
This will export the two Registry files to a text file with said name.
Copy this text file to a separate floppy disk (it'll exceed 1 MB
easily) and edit it as you feel necessary.
To completely re-create a Registry from this backup text file, from
your Win95 directory type this:
REGEDIT /C REGBCKUP.REG
REGEDIT can also import and export portions of the Registry.
Outside of Win95, type REGEDIT by itself for a list of extra
options.
----------------------------------------------------------------------
Top ten installation mistakes
10) Hitting the "exit" button on the 13th disk
9) Lending your install disks to a friend, after you let Setup write
your name to Disk 2
8) Installing on your station at work, without letting your M.I.S.
manager know (He'll find out though...)
7) Installing on top of Windows 3.1 without enabling Un-install
6) Installing from a un-supported CD-ROM drive or network
5) Installing on a system that doesn't work with 32-bit disk & file
access in WFWG 3.11
4) Restoring a backup of old Windows on top of your new Win95
install (real dumb)
3) Not doing a backup of old Windows before installing
2) Leaving the floppies write-enabled while installing
1) Installing from a BOOTLEG CD-ROM (Watch it: They're
showing up now. Buy the original and save yourself the troubles!)
----------------------------------------------------------------------
[Back to Table of Contents]
--
============================================================// //========
= "I am Gordon of Winterpeg. Windows WAS futile." // // =
= Find out why: http://www.intouch.bc.ca/win95 // // =
= Personal E-MAIL: gordonf@vcn.bc.ca \\ \\// // =
= Home Phone: +1-604-526-8724 \\ XX // =
= \X/\X/ =
= "I am Hitler of BorgSoft. I am the middle inital of William H. Gates. =
= Your work will be Microsofted. Resistance is futile. Heil Windows. =
=========================================================================
Yeah I use an Amiga at home. If you don't like my computer, dial
1-800-DIE-BILL and tell someone who cares.
----------------------------------------------------------------------
Path: news1.ucsd.edu!ihnp4.ucsd.edu!swrinde!newsfeed.internetmci.com!news.mathworks.com!nntp.primenet.com!news.cais.net!van-bc!nntp.portal.ca!news.bc.net!unixg.ubc.ca!freenet.vancouver.bc.ca!gordonf
From: gordonf@vcn.bc.ca (Gordon Fecyk)
Newsgroups: comp.os.ms-windows.win95.misc,comp.os.ms-windows.setup.win95,comp.os.ms-windows.networking.win95,comp.os.ms-windows.apps.compatibility.win95,comp.answers,news.answers
Subject: Win95 FAQs and Answers Part 3 of 14: Re-Installation
Followup-To: comp.os.ms-windows.win95.misc,comp.os.ms-windows.setup.win95,comp.os.ms-windows.networking.win95,comp.os.ms-windows.apps.compatibility.win95
Date: 30 Jun 1996 16:29:50 GMT
Organization: Vancouver Regional FreeNet
Lines: 186
Approved: news-answers-request@MIT.EDU
Message-ID: <4r6a1u$80p@milo.vcn.bc.ca>
NNTP-Posting-Host: opus.vcn.bc.ca
Summary: These postings list many questions asked in said newsgroups,
and answers them as best as I can. I make references to other
Web sites and FAQs when appropriate. Visit the WWW home of
this FAQ (http://www.intouch.bc.ca/win95) for the appropriate
links. This section is the 3rd: Re-Installation
X-Newsreader: TIN [version 1.2 PL2]
Xref: news1.ucsd.edu comp.os.ms-windows.win95.misc:111598 comp.os.ms-windows.setup.win95:10975 comp.os.ms-windows.networking.win95:7509 comp.os.ms-windows.apps.compatibility.win95:3574 comp.answers:15513 news.answers:61914
Archive-name: windows/win95/faq/part03
Last-Modified: 1996/07/01
Posting-Frequency: Every two months
URL: http://www.intouch.bc.ca/win95/faq3.htm
3) Re-installing Windows 95
Things to try before re-installing
Things to do before re-installing to ensure good re-installation
(UPDATE)
Top ten re-installation mistakes
----------------------------------------------------------------------
Things to try before re-installing
Oh No! You installed some 16-bit program and it over-wrote too
many Win95 system files! You need to re-install... or some other
disaster makes you think you need to re-install.
Not. Win95 has a pretty good defense mechanism against 16-bit
programs that replace system files, and other disasters. All key
system files have a backup copy in %WINDIR%\SYSBCKUP
(where %WINDIR% is where you installed Win95). Most cases,
Win95 will detect that system files got over-written and it'll offer to
copy Win95 versions back. Let it do so! This includes any
WINSOCK.DLL files (You should use Win95's dial up networking
anyway, not Win 3.1 dialers like Trumpet).
If it doesn't do that, you can always copy them back yourself. Go
into "Safe mode command prompt only" (Press F8 on "Starting
Windows 95..." then select said option), then:
XCOPY C:\WIN95\SYSTEM\SYSBCKUP\*.* C:\WIN95\SYSTEM
from the DOS prompt.
Also, try editing SYSTEM.INI. Inspect the [386Enh] section for
any additional "device=xxxxx.386" drivers. On a clean Win95
install, you shouldn't have ANY of these files. This goes double for
any "vshare.386" files that show up; Win95 has a built-in *vshare
driver. Removing old Win 3.1 386 Enhanced drivers will clear up
many problems.
If you get a "Registry corrupted" error of some kind, inspect your
hard drive for errors. On the requester that tells you to "Restore
from backup and Restart", press CTRL-ESC to bring up the
Win95 task manager, and run SCANDSKW.EXE from there to
check the drive for errors. SCANDSKW does a better job of
scanning Win95 drives, and it handles long filename problems better
than SCANDISK does at the DOS prompt. Once it finishes, you
can hit that button to restore the Registry and re-start. However, if
you continue to get this kind of error, start investigating your hard
drive system. You might be over-driving your HD at Mode 4 when
it's not designed for it, for example. Or maybe the drive's just on its
last legs and dying. Do a back up as soon as you can!
This Registry stuff is actually a good reason to use User Profiles.
Each user will have their own copy of the second half of the
Registry; the USER.DAT file. If the master USER.DAT gets ruined
and you need to completely re-install, you can bring back your
program settings for your 32-bit programs just by logging in as one
of the users. Your hardware (SYSTEM.DAT) config is still toast,
but you can rebuild that easy enough just by re-running the "Add
new hardware" control panel.
----------------------------------------------------------------------
Things to do before re-installing to ensure good
re-installation (UPDATE)
Ok, the above techniques didn't work and you have to re-install.
Here's what to do to make re-installing work best:
Plan to re-install from DOS, not from within Windows or Win95.
This way it'll assume a fresh installation.
From the DOS prompt outside of Win95, change to your
%WINDIR% directory, and type this:
ATTRIB -H -S -R *.DAT
This will un-hide the Registry files SYSTEM.DAT and
USER.DAT. Then delete them. That's right, delete them. A
corrupted Registry will cause no end of trouble until it's killed dead.
If you have user profiles you can restore USER.DAT easily enough.
If you were smart enough to make up a Registry backup with the
startup disk, you can try re-building it after you delete the
SYSTEM.DAT and USER.DAT, if you're sure that the backup is a
good copy. Still outside of Win95, change to your Win95 directory
and type:
REGEDIT /C REGBCKUP.REG
This will kill the current Registry files and re-build them from the
.REG text file. If necessary, specify the disk path in the filename,
after all, that .REG file will easily exceed 1 MB, and you probably
copied it to a separate disk. If you didn't make a backup, you'll
have to re-install your 32-bit apps and settings, but that's safer than
trying to use a corrupted Registry.
Remove all the DOS drivers and TSRs you can, so it won't hinder
Win95's Setup. If you have the CD-ROM version, only have the
DOS CD driver, HIMEM.SYS, and MSCDEX loaded.
Edit the remaining SYSTEM.INI to remove all foreign drivers from
the [386Enh] section. A clean SYSTEM.INI's [386Enh] section
will look exactly like this:
[386Enh]
ebios=*ebios
device=*vshare
device=*dynapage
device=*vcd
device=*vpd
device=*int13
display=*vdd,*vflatd
mouse=*vmouse, msmouse.vxd ; the mouse driver may vary, but shouldn't be .386
woafont=dosapp.fon
PagingDrive=C: ; this may vary depending on the swap file
keyboard=*vkd
device=*enable
MinPagingFileSize=32768 ; these will vary depending on your swap file
MaxPagingFileSize=32768 ; Or they may be even missing, that's OK
You might also have a "device=*vpowerd" if you have power
management on your system. Don't forget: All of Win95's drivers
really sit in the Registry, not here.
The best bit of advice I can offer, regarding disaster recovery, is
use the Backup program which comes with Win95, or use any
backup program designed for Win95, to do a Full System Backup.
This kind of backup will copy The Registry to tape as well as the
hidden and system files. When you complete the re-install, restoring
this tape will restore all your original settings. All of them.
----------------------------------------------------------------------
Top ten re-installation mistakes
10) Inserting the 13th disk before reading the "Things to try before
re-installing" section
9) Restoring your old Windows 3.1 backup on top of your
re-installed Win95 (again? Shame on you)
8) Not reading the Installation part of the FAQ over again before
re-installing
7) Forgetting to un-compress your DriveSpace drive before
re-installing
(It's best to make a separate compressed volume, and keep your
Win95 directory OFF it)
6) Forgetting to erase the corrupt Registry before re-installing
5) Using that BOOTLEG CD-ROM to re-install from (Didn't you
learn the first time?)
4) Re-installing the Win 3.1 program that made you re-install
Win95
3) Forgetting to remove old garbage from SYSTEM.INI,
CONFIG.SYS, AUTOEXEC.BAT
2) Ignoring the Installation part of the FAQ, which might've
prevented the need to re-install
1) Not backing up your system after you first installed Win95
----------------------------------------------------------------------
[Back to Table of Contents]
--
============================================================// //========
= "I am Gordon of Winterpeg. Windows WAS futile." // // =
= Find out why: http://www.intouch.bc.ca/win95 // // =
= Personal E-MAIL: gordonf@vcn.bc.ca \\ \\// // =
= Home Phone: +1-604-526-8724 \\ XX // =
= \X/\X/ =
= "I am Hitler of BorgSoft. I am the middle inital of William H. Gates. =
= Your work will be Microsofted. Resistance is futile. Heil Windows. =
=========================================================================
Yeah I use an Amiga at home. If you don't like my computer, dial
1-800-DIE-BILL and tell someone who cares.
----------------------------------------------------------------------
Path: news1.ucsd.edu!ihnp4.ucsd.edu!swrinde!cs.utexas.edu!uwm.edu!news-res.gsl.net!news.gsl.net!nntp.coast.net!news.kei.com!newsfeed.internetmci.com!info.ucla.edu!news.bc.net!unixg.ubc.ca!freenet.vancouver.bc.ca!gordonf
From: gordonf@vcn.bc.ca (Gordon Fecyk)
Newsgroups: comp.os.ms-windows.win95.misc,comp.os.ms-windows.setup.win95,comp.os.ms-windows.networking.win95,comp.os.ms-windows.apps.compatibility.win95,comp.answers,news.answers
Subject: Win95 FAQs and Answers Part 4 of 14: De-Installation
Followup-To: comp.os.ms-windows.win95.misc,comp.os.ms-windows.setup.win95,comp.os.ms-windows.networking.win95,comp.os.ms-windows.apps.compatibility.win95
Date: 30 Jun 1996 16:30:17 GMT
Organization: Vancouver Regional FreeNet
Lines: 165
Approved: news-answers-request@MIT.EDU
Message-ID: <4r6a2p$80p@milo.vcn.bc.ca>
NNTP-Posting-Host: opus.vcn.bc.ca
Summary: These postings list many questions asked in said newsgroups,
and answers them as best as I can. I make references to other
Web sites and FAQs when appropriate. Visit the WWW home of
this FAQ (http://www.intouch.bc.ca/win95) for the appropriate
links. This section is the 4th: Un-Installation
X-Newsreader: TIN [version 1.2 PL2]
Xref: news1.ucsd.edu comp.os.ms-windows.win95.misc:111599 comp.os.ms-windows.setup.win95:10976 comp.os.ms-windows.networking.win95:7510 comp.os.ms-windows.apps.compatibility.win95:3575 comp.answers:15514 news.answers:61915
Archive-name: windows/win95/faq/part04
Last-Modified: 1996/07/01
Posting-Frequency: Every two months
URL: http://www.intouch.bc.ca/win95/faq4.htm
4) UN-installing Windows 95
Things to try before giving up
How do I un-install Windows 95 on a computer...
...where I installed Win95 on top of my old Windows 3.x?
...where I installed Win95 on separate directory or drive?
...with DriveSpace 3 (tm) disk compression?
...with server based install?
...diskless workstation?
Top ten UN-installation mistakes
----------------------------------------------------------------------
Things to try before giving up
You can read the Re-Installation part of this FAQ, which covers
some ways of fixing problems without re-installing, and which
covers some tips to make a good re-installation.
Failing that, try again from scratch, with an empty system (Meaning
BACK-UP your system first, THEN delete everything and try
again), using the techniques in the Installation part of this FAQ.
Completely kill everything, even, if necessary, doing a low-level
format from your BIOS setup. Yes I know that you aren't
supposed to re-low-level-format IDE and SCSI hard drives, but it
does work in a pinch.
Failing that, check with the hardware makers for Win95 versions of
drivers, etc, and look in the MS Knowledge Base, and see about
trading your hardware for Win95 compatible types. Don't waste
your time with un-supported hardware. Check out the Hardware
Compatibility List which contains a lot of out-dated crap, but they
did sort it by manufacturer nicely for you.
Also check with your software makers and tell them to get their
ASSES in gear, and make Win95 compliant versions of their
software, or to fix their Win 3.1 software to make it work.
(Soapbox mode on) Microsoft didn't spend a whole year and a
half of beta testing, just to be ignored. Even though this is what
Novell/WordPerfect Corporation did. They're awake now... heh
heh heh (Soapbox mode off)
Or, you could just try Service Pack 1. They did fix a couple of
dumb problems (with ECP printer ports for example, if you think
the printer stopped working when Win95 came along...)
----------------------------------------------------------------------
How do I un-install Windows 95 on a computer that I installed
on top of my old Windows 3.x?
If you enabled the UN-INSTALL feature back in Setup, go to
Add/Remove Programs in Control Panel, and remove Windows
95. This will restore your original Windows config files, your
original DOS config files, and the original partition table and boot
record of the target drive.
If you didn't enable un-install, you'll have to trash your Win95
directory using the technique below, and re-install Win 3.1 fresh.
----------------------------------------------------------------------
How do I un-install Windows 95 on a computer that I installed
on separate directory or drive?
There's no fancy un-installer for this kind of installation. However,
you can just:
DELTREE %WINDIR%
and that'll work. To do this, get your DOS setup disks and boot
from the first disk. Then, exit that setup program to a DOS prompt.
From here you type:
>SYS C:
DELTREE C:\WIN95 (or wherever)
DELTREE C:\PROGRA~1 (The old "Program files" directory)
COPY AUTOEXEC.DOS AUTOEXEC.BAT
COPY CONFIG.DOS CONFIG.SYS
then re-boot.
You can then run Windows 3.1 File Manager, with "Show
Hidden/System Files" turned on, to hunt for other files you don't
recognize.
----------------------------------------------------------------------
How do I un-install Windows 95 on a computer with
DriveSpace 3 (tm) disk compression?
If you installed DriveSpace 3 from MS Plus and you chose to
un-install Win95, you can still access DriveSpace 3 drives, as it
keeps the real mode component DRVSPACE.BIN there. DOS will
recognize this version of DRVSPACE.BIN and load it. Of course,
it'll eat 100 KB of conventional memory, so you had better back up
your compressed drive and re-partition it, to kill DriveSpace 3
completely. Otherwise, the techniques above for removing Win95
will work just fine.
----------------------------------------------------------------------
How do I un-install Windows 95 on a computer with a server
based install?
The techniques above will work for a server based install, just make
sure you get your right version of DOS and your old DOS network
drivers back when you do it. It's also a lot less to delete.
----------------------------------------------------------------------
How do I un-install Windows 95 on a diskless workstation?
You'll need to change back to your DOS boot disk or DOS virtual
boot disk, then just clean out Win95 from your home directory. If
you installed on top of a Win 3.1 diskless install, you're better off
re-installing Win 3.1 fresh.
----------------------------------------------------------------------
Top ten UN-installation mistakes
10) Reading the Things to try before giving up section after
un-installing
9) Reading the Re-Installation section of the FAQ after un-installing
8) Forgetting to convert the important MS Word (tm) 7 document,
when un-installing
7) Forgetting that your database was written in Access 95 (tm)
when un-installing
6) Forgetting to try restoring that backup you made before
un-installing
5) Calling Microsoft tech support after un-installing (Think they'll
help you now?)
4) Un-installing, then realizing that your software vendor isn't selling
Win 3.1 stuff anymore
3) Having a friend or technician discover a virus after you thought
Win95 caused all your troubles, and after you un-installed
2) Un-installing because the program you need to use the most
doesn't work (The program's broken, not the OS)
1) Buying Win95 in the first place, if you un-installed for keeps
----------------------------------------------------------------------
[Back to Table of Contents]
--
============================================================// //========
= "I am Gordon of Winterpeg. Windows WAS futile." // // =
= Find out why: http://www.intouch.bc.ca/win95 // // =
= Personal E-MAIL: gordonf@vcn.bc.ca \\ \\// // =
= Home Phone: +1-604-526-8724 \\ XX // =
= \X/\X/ =
= "I am Hitler of BorgSoft. I am the middle inital of William H. Gates. =
= Your work will be Microsofted. Resistance is futile. Heil Windows. =
=========================================================================
Yeah I use an Amiga at home. If you don't like my computer, dial
1-800-DIE-BILL and tell someone who cares.
----------------------------------------------------------------------
Path: news1.ucsd.edu!ihnp4.ucsd.edu!swrinde!howland.reston.ans.net!nntp.coast.net!news.kei.com!newsfeed.internetmci.com!info.ucla.edu!news.bc.net!unixg.ubc.ca!freenet.vancouver.bc.ca!gordonf
From: gordonf@vcn.bc.ca (Gordon Fecyk)
Newsgroups: comp.os.ms-windows.win95.misc,comp.os.ms-windows.setup.win95,comp.os.ms-windows.networking.win95,comp.os.ms-windows.apps.compatibility.win95,comp.answers,news.answers
Subject: Win95 FAQs and Answers Part 5 of 14: Usage
Followup-To: comp.os.ms-windows.win95.misc,comp.os.ms-windows.setup.win95,comp.os.ms-windows.networking.win95,comp.os.ms-windows.apps.compatibility.win95
Date: 30 Jun 1996 16:30:53 GMT
Organization: Vancouver Regional FreeNet
Lines: 595
Approved: news-answers-request@MIT.EDU
Message-ID: <4r6a3t$80p@milo.vcn.bc.ca>
NNTP-Posting-Host: opus.vcn.bc.ca
Summary: These postings list many questions asked in said newsgroups,
and answers them as best as I can. I make references to other
Web sites and FAQs when appropriate. Visit the WWW home of
this FAQ (http://www.intouch.bc.ca/win95) for the appropriate
links. This section is the 5th: Usage
X-Newsreader: TIN [version 1.2 PL2]
Xref: news1.ucsd.edu comp.os.ms-windows.win95.misc:111600 comp.os.ms-windows.setup.win95:10977 comp.os.ms-windows.networking.win95:7511 comp.os.ms-windows.apps.compatibility.win95:3576 comp.answers:15515 news.answers:61916
Archive-name: windows/win95/faq/part05
Last-Modified: 1996/07/01
Posting-Frequency: Every two months
URL: http://www.intouch.bc.ca/win95/faq5.htm
5) Basic Win95 usage
...vs Windows 3.x
...vs MS-DOS (tm)
What is this "Explorer" thing?
How do I...
...find my old Win 3.x programs?
...make a program read a file I click on?
...change what program opens what kind of file?
...run Windows 3.x programs? (including Windows games)
How do I install and run Win 3.1 after installing Win95?
(NEW)
...run MS-DOS apps?
...run MS-DOS utilities? (Xtree (tm), Norton Utilities (tm),
etc)
...run MS-DOS games?
...format or copy disks?
...search for files?
...search for files with certain information in them?
...add my own items to the Start Menu?
The Desktop, Start Menu, and shortcuts
...change my display resolution?
...change my display driver?
...disable the "Full window drag" feature of MS Plus?
Some MS-DOS utilities are missing. Where can I get them?
Should I buy these new fancy utilities for Win95?
...Norton Navigator (tm) ?
...un-installers?
...anti-virus programs?
...Microsoft Plus (tm) ?
...RAM compression programs?
Top ten mistakes running Windows 3.x programs
Top ten mistakes running MS-DOS programs and games
----------------------------------------------------------------------
Basic Win95 usage vs Windows 3.x
Win95 sports the cool new Explorer Desktop, in an attempt to be
more Mac-like. Try to forget what you know about Program
Manager, File Manager, Print Manager, etc because very little of it
applies!
Win 3.1 programs will run like they used to; the window might look
a bit different, and there might be some extra buttons on the border,
but they will work otherwise.
Get used to using your right mouse button. On an Amiga, the right
button was a "menu" button, which brought up a hidden menu. On
OS/2, it brings up menus for each object you click on. On Win95,
it acts like the OS/2 right-click except it pretty much works on
anything; window title bars, the Start Menu, any kind of icon,
properties sheets, whatever.
Win 3.1 programs run in a single process under Win95,
co-operatively multitasking as they always did since Windows/386.
This means one Win 3.1 app can suspend the entire Win 3.1
session. In fact, one Win 3.1 app can suspend all of Win95! This is
purely for compatibility.
----------------------------------------------------------------------
Basic Win95 usage vs MS-DOS (tm)
Microsoft kept DOS for compatibility and nothing else. Win95
includes MS-DOS 7.0, which under Win95, is a multitasking DOS.
DOS programs run in protected sessions like Win95 programs do,
and the system pre-emptively task-switches between Win32
sessions, DOS sessions, and the single Win 3.1 session.
COMMAND.COM is now a multitasking command prompt.
Win95 can unload it on command, unless a DOS program is
running from it. Some Win32 character-based programs can run
from COMMAND.COM, if they don't depend on Windows NT
features. Outside of Win95 though, COMMAND.COM, and the
rest of DOS, is just DOS.
The biggest difference between old DOS and DOS 7.0, is it does
not allow direct disk writes, to prevent filename corruption and
virus infection. Effectively, if a program tries to write to the disk
directly while outside of Win95, you will get an evil message telling
you to restart your computer. Normally this is good, but some
"good" programs (like Windows 3.1 running 32-bit disk access,
which DOES work in DOS 7.0 by the way) need to access the
disk directly. If you can trust such programs, type:
LOCK C: (or whatever drive letter)
before running the program. Notice, however, that LOCK C: only
works outside of Win95 (like when you "Restart the computer in
MS-DOS mode" for example), and within Win95, no direct writes
are allowed under any circumstance.
Some DOS TSRs no longer supported under Explorer are PRINT
and SUBST. As a general rule, don't run any DOS TSRs that fiddle
with the disk handler (such as Norton SMARTCAN or
CASMGR) or require direct access to hardware (like PRINT).
----------------------------------------------------------------------
What is this "Explorer" thing?
Like I wrote above, it's Win95's new default shell. Explorer actually
has two big parts and several little ones. The two biggest parts you
will see right away are the Desktop and the Taskbar. I won't go
into details, because Microsoft has lots of basic stuff about these
two devices.
I will go into details on the little pieces, however. Microsoft
combined the functionality of many utilities (including File Manager,
Control Panel, Print Manager, Remote Access, Windows Setup,
PIF editor) into it. Control Panel is pretty obvious and works much
the way it did back in Win 3.1. The others were completely
renamed and re-worked, and it'll just take some "Exploring" (pun
intended) to learn them.
Running "EXPLORER.EXE" with Explorer running will merely
open a File Manager style window, with directory trees and split
displays. "Exploring" directories like this is great for power users
who need to find something fast. Right-click on any folder or drive
and select "Explore" to begin "Exploring" from that point. You aren't
running multiple processes of Explorer; you're merely opening
another Explorer window separate from the Desktop.
Print Manager got replaced by the Printers folder in "My
Computer". You create and maintain printers here, though there is a
shortcut to it from Control Panel, for compatibility. When you
create printers here you may use Win 3.1 printer drivers (though I
don't recommend this) or Win95 drivers. Microsoft claims NT
drivers will install here as well.
Remote Access gets replaced by Dial-up Networking, which is
now a general network connection through modems. Dial-up
Networking covers regular RAS connections, Internet connections,
and connections to NetWare Connect servers for remote NetWare
log ins.
Windows Setup is kinda scattered all over the place, but you'll find
the main components in the Control Panel's Add New Hardware,
Add/Remove Programs, and System programs.
PIF files are now "Shortcuts to MS-DOS Programs", and you bring
up a DOS program's properties to edit its PIF file. Check out How
to run DOS programs in Win95 for details.
----------------------------------------------------------------------
How do I find my old Win 3.x programs?
Win95 Setup copied all your group files (.GRP) from Program
Manager into a directory called (what else), "Start Menu". It copied
the icon groups into little directories which you can view by pressing
the Start button, and selecting "Programs".
One notable exception to this, is Setup eliminated the "Main"
program group entirely. It'll relocate Main items into the root of the
Start Menu, and remove icons that no longer apply (like File
Manager).
If a program installer just copied a .GRP file to the hard disk, rather
than add the icons through the Windows APIs like its supposed to,
you can add that group to the Start Menu by finding the .GRP file
itself, and opening it (double-clicking it). If programs also try to
change PROGMAN.INI, which contains the group listings, Win95
will move them to the Start Menu the next time you re-start.
----------------------------------------------------------------------
How do I make a program open a file I click on?
Explorer lets you browse your hard drive and click on documents,
as well as programs. This works exactly like clicking on documents
in File Manager; simply double-click on the document.
If you click on a file with an extension it doesn't recognize, Explorer
offers up a list of programs and lets you choose which one you
want. You can also give a descriptive name to the file type (such as
"Doom data file" for .WAD files).
----------------------------------------------------------------------
How do I change what program opens what kind of file?
To edit file types, select the View menu and Options in any
Explorer window. Hit the "File types" tab and you can edit, add, or
delete known file types. Some file types are hidden from this display
(such as "System File") to keep you from hurting them. I'll tell you
how to find them later.
You can do much more than Open a document. Some document
types have more options than Open if you right-click on them. For
example, .BAT files have an "Edit" command which brings up
Notepad. To add this functionality to your own documents, go
back to the "File types" tab and find the file type you want to add
this to, and hit Edit. You can then Add an action, such as "Edit",
which launches a separate program and opens that file. This
worked great for me; I have an "Edit" option added to all my
HTML documents which launches MS-Word, an extra "Edit as
Text" option to use Notepad instead, so I can remove the extra
crap that Internet Assistant put in, and "Open" launches Mosaic to
view the document.
----------------------------------------------------------------------
How do I run Windows 3.x programs? (including Windows
games)
If there's an icon in the Start Menu, you can run it from there. You
can also find the executable itself by browsing the hard drive, then
opening it. Self-installing archives, such as Win95 Service Pack 1,
are one kind of Windows program you'll need to run by browsing
and opening.
If you don't see your old program group on the Start Menu, or if a
program just copied a group file (.GRP) to the hard disk, just find
the .GRP file it installed and Open it. This runs a converter that
builds Shortcuts for the Start menu.
Windows programs will even run from a DOS session under
Win95. Type the name of the executable like you would for any
DOS program. You can open documents from the DOS session
with the START command (just like the Start Menu "Run"
command). "START MyDocument.doc" will run Microsoft Word,
and load MyDocument.doc into memory.
A handful of Win 3.1 and Win 3.0 programs won't recognize that
you have a newer version of Windows, and report an error like,
"This program requires Windows 3.1 or better". Well, you have a
"Setver" kind of workaround for such programs in Win95; the
[Compatibility] section of WIN.INI. For example, to install
Outpost 1.0 on Win95, you can edit WIN.INI so
"INSTALL=00020000" instead of 00040000; that number is a
Windows version reporting number. This will make INSTALL.EXE
think it's running in Win 3.1. Later on, if the main program acts the
same way, you can add entries to WIN.INI with that version ID
that matches Win 3.1. A handful of entries exist already, for known
programs.
NOTE: Win95 will restore any changes you make to programs
called INSTALL or SETUP in the [compatibility] section of
WIN.INI. When you make your changes, do them from
SYSEDIT.EXE, then run your installer. Win95 instantly
changes the entry back to 00040000 after the program finishes
installing.
There's a cute utility for real dumb Win 3.1 programs;
MKCOMPAT.EXE, in your Win95 directory. Run this program to
turn on compatibility switches to make dumb programs work. This
is a last resort, and I'd rather you harass the program's publisher or
author to make them fix it.
----------------------------------------------------------------------
How do I install and run Windows 3.1 on a system now
running Win95? (NEW)
If you installed Win95 in a separate directory (You smart person
you), you can do a very cute trick: Hit Start/Shut Down... and
"Restart computer in MS-DOS Mode". This will take you straight
to a DOS prompt. From here, change to your Win 3.1 directory
and just type WIN.
This little trick works because Win95 DOS (DOS 7.0) already
loaded the necessary HIMEM.SYS XMS driver, which is all Win
3.1 really needs to load. Performance will be poor, because there's
no disk caching active at this time, and no fancy network stuff will
probably work either, because you aren't using Win 3.1's version of
IFSHLP. To get these working, check out the tricks used to run
MS-DOS games and prepare special PIF files for, what MS calls, "
Single mode MS-DOS". Be sure to include the Win 3.1 versions of
IFSHLP.SYS, MSCDEX, and NET START, and Win95 versions
of other base drivers such as EMM386. Also include LOCK C: to
let 32-bit disk and file access work.
How do I install Win 3.1 fresh in a Win95 system?
First, Shut Down, and Re-start the computer in MS-DOS mode. If
you have a CONFIG.SYS or AUTOEXEC.BAT file (Which you
don't need really), copy these to a safe place.
Next, insert your Win 3.1 setup disk 1 and run SETUP.EXE from
it. This performs a normal Win 3.1 or WFWG 3.11 install. When
prompted for your Windows directory location, be EXTRA
CAREFUL to use a different directory name than your Win95
installation!!!!!!
Next, let Win 3.1 Setup proceed as normally. When it finishes,
copy any changed CONFIG.SYS and AUTOEXEC.BAT it made
up and save them with different file names, and restore the previous
versions of these files.
Next, return to Win95 by typing EXIT. Look for WIN.COM in the
Win 3.1 directory you installed it in, and right-click on it. Select
"Properties". Then use the same techniques I mentioned above for
setting up a special PIF file for Single Mode DOS. This way, you
can specify a proper Win 3.1 startup sequence and avoid polluting
your Win95 configuration. You can also use Win 3.1 versions of
IFSHLP, NET, and MSCDEX as required. Now, when you launch
this version of WIN.COM from Win95, it will re-start your
computer using that special configuration. When you exit Win 3.1,
Win95 re-starts.
----------------------------------------------------------------------
How do I run MS-DOS apps?
You can either run a DOS session by hitting
Start/Programs/MS-DOS Prompt and run the DOS program from
there, or open it from Explorer. If it's a DOS program, Win95 will
start a DOS session and load the program into it.
NOTE: If you launch a DOS program from Explorer, it will
create a PIF file for it (Also called a "Shortcut to MS-DOS
Program"). If it can't write to the directory where the program
resides, it will write the PIF file to %WINDIR%\PIF.
If you want to avoid making four hundred PIF files, run the
MS-DOS Prompt first, then run the program within that session. It
will use the program properties built into the default PIF
(DOSPRMPT.PIF) instead of making one.
----------------------------------------------------------------------
How do I run MS-DOS utilities? (Xtree (tm), Norton Utilities
(tm), etc)
Like any other MS-DOS program, but avoid utilities that do direct
disk writes, like DOS versions of SpeedDisk, Norton Disk Doctor,
DiskEdit, etc as these won't work in DOS sessions, because
Win95 won't let you perform direct disk writes in a DOS session.
If you have to run utilities that access the disk directly (like sector
editors), you must exit to DOS (Restart computer in MS-DOS
mode) and LOCK the hard drive you will edit (LOCK C: ). This
will allow the direct disk access to work.
Utilities to avoid include DOS versions of ScanDisk, Defrag, and all
their cousins. Win95 comes with Windows version of these utilities
that work with long filenames etc, and Peter Norton has Win95
versions of his utilities, too.
----------------------------------------------------------------------
How do I run MS-DOS games?
I go into a whole whack of detail on this subject, but to make life
real simple, run your games in DOS sessions under Win95, like you
would any DOS application. A handful of useful Properties settings
to turn on include, "Protected", "Prevent DOS programs from
detecting Windows", "Full Screen", and "Always Suspend".
DOS games can work with protected mode CD-ROM, sound, and
network drivers easily. All the real mode hooks are there. Basically,
you don't need to load any DOS drivers for anything to make a
game run.
For more details, jump to the Running MS-DOS Games section.
----------------------------------------------------------------------
How do I format and copy disks?
Right-click on the floppy drive in "My Computer" and select
"Format". Get used to using the right mouse button. To copy disks,
right-click on the drive and select "Copy..."
----------------------------------------------------------------------
How do I search for files?
Explorer has a nifty file find tool built in. Right-click on where you
want to start searching and select "Find". You could also hit Start
Menu/Find.
You can search your entire computer (including floppy drives and
net drives), or a single drive for a file. Type in the filename (or part
of the filename) and hit Find. Wildcards (*, ?) are permitted but not
required. Don't forget you're dealing with long filenames now.
You can search text within files, search for files with certain dates,
certain sizes, even search for computers on a network.
----------------------------------------------------------------------
How do I add my own items to the Start Menu?
The Start Menu's just filled with shortcut files. The easiest way to
add an item is to drag an icon on top of the Start button.
If you're a bit more selective on where you want to put the shortcut,
right-click on the Taskbar and hit Properties. Select "Start Menu
Programs" and you can add or remove items. The Shortcut Wizard
helps you find the item you want to make a shortcut to.
----------------------------------------------------------------------
The Desktop, Start Menu, and shortcuts
The Desktop and Start Menu are just directories on your hard
drive, filled with .LNK files, or Shortcuts. They may also have
regular files in them, but Start Menu items have to be .LNK or .PIF
files.
If you right-click on the Start button, you can Open the Start Menu
like any other disk directory and move stuff around.
----------------------------------------------------------------------
How do I change my display resolution?
Right-click on any empty Desktop space and select "Properties".
You can change the wallpaper, screen saver, appearance of
windows, and display mode. If you change display resolution
without changing the colour depth, Win95 will re-size the desktop
and ask you if it's OK to use it. If you change the display's colour
depth (like 8-bit to 16-bit for example) Win95 will re-start.
Many advanced display drivers (such as ATI's DirectX Drivers)
will add extra tabs to this properties sheet. Take advantage of them.
Still others (like Diamond's S3 drivers) will let you change display
depth (number of colours) without re-booting. Unlike Win 3.1
drivers however, these utilities use hooks in Win95 set aside by
Microsoft for this purpose. Get a proper Win95 display driver to
take advantage without damaging your system.
----------------------------------------------------------------------
How do I change my display driver?
In Display Properties, select the settings tab. Hit the "Change
Display Type" button. This will let you change the video driver and
monitor driver.
----------------------------------------------------------------------
How do I disable the "Full window drag" feature of MS Plus?
Microsoft Plus' "Display Enhancements" are a bit of a processor
hog. You can turn off the Full Window Drag by hitting the "Plus"
tab in Display Properties, and just turning it off.
----------------------------------------------------------------------
Some MS-DOS utilities are missing. Where can I get them?
You might be looking for QBASIC or some other item from DOS
6 missing here. These are available on the CD-ROM version.
They're in DRIVERS\OTHER\OLDMSDOS, and you'll find a
batch file that will copy them to your %WINDIR%\COMMAND
directory. After a re-boot they'll be available. You need to re-boot
because these are direct copies of DOS 6.22 programs, and the
batch file SETVER's them to that version.
If you installed Win95 on top of old DOS, your DOS directory will
still be in your path, and you can run the old DOS utilities without
having to install them from the CD-ROM. Setup will conveniently
add them to the SETVER table.
----------------------------------------------------------------------
Should I buy these new fancy utilities for Win95?
...Norton Navigator (tm) ?
If you used Norton Desktop you'll instantly miss FileAssist and
those cool toys. I suppose it's OK, but a system running Navigator
requires more RAM than Win95's Explorer does by itself. Expect
additional disk swapping after installing this.
New users should just try Explorer for a while first. There's no real
point to buying a shell extension when you don't know how to use
the default shell. After all, why would Microsoft spend so much
time developing this interface, only to have you buy shell
enhancements for it? Such shell extenders are really for power users
only.
...un-installers?
A must-have, if you run many old Win 3.1 programs. Make sure
you obtain a Designed for Windows 95 version; Win 3.1
un-installers don't recognize The Registry, where Win95 stores
most of its configuration info.
Be very careful of installing Win95 programs with such an
un-installer active. Designed for Win95 apps include their own
un-installer, and if you use the utility's un-installer instead of the
program's own, the un-installer can remove more than it's supposed
to. It could also remove less. CleanSweep 95 (tm), for example,
warns you to this effect. Heed that warning!
The publishers of un-installers are preying on the fear of new Win95
users that they HAVE to use a "professional un-installer" for even
Designed for 95 apps. Get serious. If a program can't un-install
itself it doesn't deserve the logo. Complain to them, or to Microsoft,
who awarded the logo rights to them.
...anti-virus programs?
Again, Designed for Windows 95 is the key. Otherwise, run the
anti-virus software outside of Win95.
...Microsoft Plus (tm) ?
Also a must-have, if you have a fast machine. System Agent makes
up most of the purchase price by itself, running maintenance
programs like ScanDisk and Defrag unattended.
The other cool stuff that comes with it are for power users only,
though its web browser will get you started on The Internet with
minimal fuss. Later on you can install Netscape Navigator or MS
Internet Explorer 2.0, or even NCSA Mosaic like me, to replace
this cheap web browser.
...RAM compression programs?
Yeah right. Build Washboard Abs in three weeks. "I was a 98
pound weakling until I installed SoftRAM 95." RAM compression
only works when there's a defined API for accessing data RAM, as
there is a defined API for accessing disks, and there is no such thing
in Win95. At least, there's no way to regulate how the program
accesses any RAM it allocates.
Save yourself the hundreds of dollars of invested time and buy more
RAM instead. These programs were great for Win 3.1, where they
fixed inadequacies in the operating system. Win95 has considerably
more horsepower by itself, but it thrives on a 16 MB system for
running the big mainstream apps. MS Works 4.0, however, will run
on an 8 MB system effortlessly. Try the techniques in Swap file &
caching theory to speed up the system and run more programs.
If you really need the power to run 100 programs at once, buy a
big computer and install Windows NT, which will run all the Win95
apps anyways. Then you'll have no resource limitations, no swap
file limitations, in fact, no DOS limitations.
----------------------------------------------------------------------
Top ten mistakes running Windows 3.x programs
10) Installing a Win 3.1 un-installer
9) Installing a Win 3.1 communications program (replacing Win95
COMM.DRV)
8) Installing a Win 3.1 utility pack
7) USING a Win 3.1 utility pack
6) Installing a Win 3.1 app that replaces core system files
5) Installing a Win 3.1 backup program, especially since Win95
backup programs are here for FREE
4) Installing Norton Desktop for Win 3.1 and expecting it to work
3) Installing a RAM compression program for Win95
2) Installing a RAM compression program for Win 3.1
1) USING a RAM compression program for Win 3.1
----------------------------------------------------------------------
Top ten mistakes running MS-DOS programs and games
10) Loading CTMM16.SYS (SB16 driver) in Win95 because a
game manual said to do it
9) Loading MSCDEX.EXE in Win95 because a game manual said
to do it
8) Making a boot disk before realizing how .PIF files work,
because a game manual said to do it (I think you get it by now)
7) Installing QEMM 8.0 (or any version) just because you can't get
one game to work
6) Adding EMM386.EXE to CONFIG.SYS before learning how
PIF files work
5) Letting a "techie" friend add EMM386.EXE (or any other real
mode driver)
4) Letting a "techie" friend make your game work before he reads
this FAQ
3) Running Norton SpeedDisk 6.0 and forgetting you have long
filenames now!
2) Making a boot disk for a game before seeing the "Prevent DOS
programs from detecting Windows" switch, or before specifying a
special DOS config for that program
1) Running Win95 with a host of DOS drivers and memory
managers. Get Win95 drivers for your stuff and make Win95
perform like Win95!
----------------------------------------------------------------------
[Back to Table of Contents]
--
============================================================// //========
= "I am Gordon of Winterpeg. Windows WAS futile." // // =
= Find out why: http://www.intouch.bc.ca/win95 // // =
= Personal E-MAIL: gordonf@vcn.bc.ca \\ \\// // =
= Home Phone: +1-604-526-8724 \\ XX // =
= \X/\X/ =
= "I am Hitler of BorgSoft. I am the middle inital of William H. Gates. =
= Your work will be Microsofted. Resistance is futile. Heil Windows. =
=========================================================================
Yeah I use an Amiga at home. If you don't like my computer, dial
1-800-DIE-BILL and tell someone who cares.
----------------------------------------------------------------------
Path: news1.ucsd.edu!ihnp4.ucsd.edu!swrinde!howland.reston.ans.net!nntp.coast.net!news.kei.com!newsfeed.internetmci.com!info.ucla.edu!news.bc.net!nntp.portal.ca!van-bc!unixg.ubc.ca!freenet.vancouver.bc.ca!gordonf
From: gordonf@vcn.bc.ca (Gordon Fecyk)
Newsgroups: comp.os.ms-windows.win95.misc,comp.os.ms-windows.setup.win95,comp.os.ms-windows.networking.win95,comp.os.ms-windows.apps.compatibility.win95,comp.answers,news.answers
Subject: Win95 FAQs and Answers Part 6 of 14: Hardware
Followup-To: comp.os.ms-windows.win95.misc,comp.os.ms-windows.setup.win95,comp.os.ms-windows.networking.win95,comp.os.ms-windows.apps.compatibility.win95
Date: 30 Jun 1996 16:31:24 GMT
Organization: Vancouver Regional FreeNet
Lines: 689
Approved: news-answers-request@MIT.EDU
Message-ID: <4r6a4s$80p@milo.vcn.bc.ca>
NNTP-Posting-Host: opus.vcn.bc.ca
Summary: These postings list many questions asked in said newsgroups,
and answers them as best as I can. I make references to other
Web sites and FAQs when appropriate. Visit the WWW home of
this FAQ (http://www.intouch.bc.ca/win95) for the appropriate
links. This section is the 6th: Hardware
X-Newsreader: TIN [version 1.2 PL2]
Xref: news1.ucsd.edu comp.os.ms-windows.win95.misc:111601 comp.os.ms-windows.setup.win95:10978 comp.os.ms-windows.networking.win95:7512 comp.os.ms-windows.apps.compatibility.win95:3577 comp.answers:15516 news.answers:61917
Archive-name: windows/win95/faq/part06
Last-Modified: 1996/07/01
Posting-Frequency: Every two months
URL: http://www.intouch.bc.ca/win95/faq6.htm
6) Making your hardware work
Device Manager basics
Does Plug & Play work on systems without a Plug & Play
BIOS?
How do I make this card work...
...sound card
Sound Blaster (tm), SB Pro, SB16, AWE32 (tm)
Sound Blaster 16 Plug & Play (UPDATE)
Clone sound cards listed with Windows 95
Clone sound cards that need DOS drivers to run
sound card NOT listed with Windows 95
...network card
card listed with Windows 95
card NOT listed with Windows 95
Using old ODI drivers with Win95
Using old NDIS2 drivers with Win95
...scanner card
...caching IDE or caching SCSI card
How do I make this drive work...
...CD-ROM drives
SCSI and IDE
Proprietary drives with special cards
Using DOS drivers (Avoid at all costs!)
...tape drives
SCSI tape drives (UPDATE)
Non-SCSI tape drives (Floppy, parport, FC-20,
whatever)
...removable drive
SCSI optical drives (are there any other kinds?)
other SCSI removable drives
non-SCSI removable drives (Don't bother)
Flash PC card or hardcard for a notebook computer?
How do I make this input device work...
...un-listed mouse
...graphics tablet
...MIDI keyboard
How do I fix hardware conflicts?
How do I get a list of what card is using what IRQ? (or
whatever)
How do I tell Win95 about cards it doesn't have drivers for?
Using "Safe Mode" to fix hardware problems
Basic ISA Plug & Play theory (Don't bother if you don't like
details)
Basic PCI Plug & Play theory (Don't bother also)
Other PnP theory (SCSI, monitors, printers, PCMCIA, etc)
Top ten hardware mistakes
----------------------------------------------------------------------
Device Manager basics
Right-clicking on "My Computer" and selecting "Properties" brings
up a properties sheet for the whole computer, including all
hardware. You find the hardware info on the Device Manager tab.
Device Manager is Hardware Central on Win95. Because PC
hardware is an absolute pain to configure, Win95 tries to show you
how your hardware's set up here.
Not all devices show up here, however. Only hardware devices
with Win95 drivers will appear here. Devices with Win 3.1 drivers,
pure software devices (like video codecs or PC speaker sound
drivers), and DOS real mode drivers will not show up here. If you
use such drivers, Device Manager cannot avoid hardware conflicts.
Get Win95 drivers for your stuff, or dump your hardware in favor
of devices with Win95 support. Save yourself the headaches. Or
just check out How to reserve resources if you just have to use the
old stuff.
----------------------------------------------------------------------
Does Plug & Play work on systems without a Plug & Play
BIOS?
Yes it does, amazingly. Win95 will assume the role of PnP manager
if your system does not have a PnP BIOS.
This is actually advantageous, because BIOS authors haven't gotten
the idea down pat yet. Early Award BIOSes, for example, don't
work with SB16 PnP boards, or boards with Crystal's CS4232
sound chipset, because these devices have multiple resource needs
that these BIOSes can't handle. Other bugs include locating PnP
network boards on top of Joystick ports.
Whose BIOS does work, then? If you have a board with Intel's
Triton chipset, visit www.mrbios.com. He has a shareware BIOS.
Try to get a non-PnP BIOS for your MB if you have troubles.
Phoenix and Intel worked pretty close together to straighten it out,
and while I haven't seen an AMI PnP BIOS yet, I'm sure they are a
bit more careful than Award is.
----------------------------------------------------------------------
How do I make this sound card work...
Sound Blaster (tm), SB Pro, SB16, AWE32 (tm)
Simple. Plug it in and load Win95 drivers, or run Add New
Hardware. One thing Win95's really good at finding, is original
Creative Labs hardware. To make DOS games run in DOS
sessions, you might need to change the card's settings.
Win95 tends to allocate odd resources to SB16s. To avoid this,
make sure those resources are available, including freeing them in
your BIOS setup if you have such an option.
Sound Blaster 16 Plug & Play
Plug & Pray is more like it.
The PnP manager will have problems configuring this card if its
"preferred resources" aren't available. Try to free up the standard
I/O, Interrupt, and DMA values a Sound Blaster normally uses:
A220, I5, D1, H5 (DMA 5). If you use an Award BIOS be sure to
set those resources as "No/ICU" or otherwise available for use.
Non PnP systems will work with the SB16 PnP card, because
Win95 will allocate resources the card can actually use.
Whatever you do, do not install Creative's PnP Manager
software on a Win95 system. That DOS/Win 3.1 PnP Manager is
for systems running good ol' DOS. You will need the DOS PnP
Manager for setting up Single Mode DOS programs, where you
specify a new DOS configuration for the game, however. Try not to
let the PnP manager installer add anything to your Windows
directory; you can specify this when you install the PnP Manager by
changing the Windows directory choice to "None".
NOTE: Creative's newest PnP sound cards come with a whole
slew of sound utilities that replicate many of Win95's built-in
programs! This is a waste of disk space. For example, you try
to use Creative's CD player, you insert an Audio CD, and
Win95's CD Player auto-runs. Stupid.
Clone sound cards listed with Windows 95
Microsoft included quite a list of weird chipsets in Win95's sound
support, and most of the Windows Sound System clones offer
Sound Blaster emulation in DOS sessions! The list currently
includes:
OPTi 929 and 929A
OPTi MAD16
TI/IBM MWAVE (Through CD-ROM version)
Windows Sound System (Analog Devices 1448 and Compaq
(tm) Business Audio)
ESS 688 and 488
Clone sound cards that need DOS drivers to run
Only SB16 class cards actually need "drivers" to operate, or at
least, they're the only ones that actually stay resident when you load
them. Other cards (Mozart class cards for example) will work with
Win95's SB Pro drivers, or Windows Sound System drivers.
But if you have a card that won't work with SB drivers, or it
supposedly requires DOS drivers, here's what to do. I'll use Oak
Mozart class cards as an example, as this works perfectly with
Mozart cards:
Install the card software, and be sure NOT to install Windows
support for the card. Just to be sure, back up SYSTEM.INI
before installing the software.
Reboot the computer, but hit F8 on "Starting Windows 95..."
and select "Command Prompt Only".
Type MEM /C, and compare this module listing with the files in
the CONFIG.SYS and AUTOEXEC.BAT that the sound
software modified. Do any of the resulting files remain resident?
In the case of Mozart class cards, they will not remain resident.
If the sound software modified SYSTEM.INI, restore it with the
backup you made.
If no files remain resident, reboot and let Win95 run. Then install
drivers for the SB Pro, or Windows Sound System, depending
on what the card emulates. Re-boot and see if sound works.
Here's what's happening: The DOS "drivers" load and initialize the
sound card. Once this initialization is done, it will operate like a
regular SB or WSS card, and you can use Win95 drivers for SB or
WSS. This technique also works for CD-ROM support; if you let
the sound card "driver" initialize the card, then install Win95 support
for whatever CD-ROM card it emulates, it will work without having
to load DOS CD-ROM drivers for it.
Sound card NOT listed with Windows 95
Cards not listed with Win95 will 90% work with Microsoft's SB
Pro or Windows Sound System drivers. WSS cards will even work
with DOS games in DOS sessions, if you enable Sound Blaster
emulation. Still other cards, like Crystal's CS4232, do SB
emulation in hardware, at the same time as WSS.
See the previous section on using initialization "drivers", which will
let you use Win95's SB Pro or WSS drivers with your unlisted
sound card.
----------------------------------------------------------------------
How do I make (this network card) work?
Win95 introduces a new version of Network Device Interface Spec
(NDIS) 3.1. NDIS 3.1 allows for PnP events, such as activating
network clients when you insert a PCMCIA card. Win95 comes
with quite a handful of NDIS 3.1 drivers for many cards, and I'll
cover them first. I also go into a whole mess of network stuff in
another section.
Net card listed with Windows 95
If a card is listed in Win95's built in driver list, it has an NDIS 3.1
driver. Most of the time, Add New Hardware will detect it and
install a driver for it. If not, you can manually add the driver from
the list. On occasion, Win95 will goof on its first resource choices,
but as it tells you, you can immediately run Device Manager to
correct it.
Net card NOT listed with Windows 95
Of course, no hardware maker should be in the DOS box business
these days without Win95 drivers. Check with them first.
Otherwise, Win95 will use NDIS 2.0 or ODI drivers if you're
stuck. Both options sit below.
Using old ODI drivers with Win95
Life stinks sometimes; too many card makers believe only Novell
does PC networks. Ahh well. Real mode ODI drivers will work
with Win95 protected mode protocols and drivers, as Novell
designed ODI to work with NDIS protocols and clients.
You need three real mode TSRs to use a network card with an
ODI driver:
LSL.COM (Comes with the net card)
The net card driver itself (Referred to as an MLID)
ODIHLP.EXE (Comes with Win95)
You also need to install the "Existing ODI driver" using Add New
Hardware, or Network control panel. Adding the "Existing ODI
Driver" will install ODIHLP.EXE, needed to link the real mode
drivers with NDIS 3.1.
Finally, you need to write a NET.CFG for the ODI support. NDIS
on top of ODI only works with Ethernet and Token-Ring (If you
know of others please tell me!) ArcNet will not work in this
configuration. You also need to specify all the frame types your
adapter type can handle, for example:
link driver 3c5x9
frame ethernet_802.2
frame ethernet_802.3
frame ethernet_snap
frame ethernet_ii
Some NDIS protocols require the weird frame types. In particular,
TCP/IP requires ETHERNET_II.
Copy this NET.CFG to the same directory where you keep LSL
and the net card driver itself (Stick them in your Win95 directory
for convenience).
Using old NDIS2 drivers with Win95
Like ODI support, Win95 will use real mode NDIS 2.0 drivers as
well, but this eats significant amounts of conventional memory; even
more than ODI drivers use!
To use an NDIS 2.0 driver, you use Add New Hardware as
before, and tell it where to find the NDIS 2 driver. You can
configure the card like any other NDIS 3.1 card, but Win95 will
add this line to AUTOEXEC.BAT:
net start
This will load PROTMAN and the .DOS net card driver into
conventional memory. When WIN.COM loads, it will load the
NDIS 2 protected mode helper and start the network. NDIS 2
driver info will appear in The Registry, and should also appear in
PROTOCOL.INI for compatibility.
Some NDIS 2 drivers exist in DRIVERS\NETCARD on the
Win95 CD-ROM, so check there if you don't see your card listed.
Also check out Microsoft's Win95 driver library.
----------------------------------------------------------------------
How do I make this scanner card work?
If you own an HP scanner you're in luck; HP designed Win95
versions of their TWAIN scanner interface software. HP's TWAIN
currently depends on Advanced SCSI Programming Interface, so
you need a Win95 driver for your SCSI host adapter to use it.
Non-SCSI scanners can work with the Win 3.1 software provided
for it, but try to avoid loading real mode scanner drivers just to
make your cheap hand scanner work. Don't waste your time. It
may be possible to find a Win95 TWAIN driver for your
non-SCSI scanner; ask the manufacturer.
Check out Epson's home page for Win95 versions of TWAIN for
their Action Scanner and ES series scanners. These support their
SCSI and Parallel Port scanners. Again you'll need a Win95 driver
for your SCSI card, as Epson's TWAIN requires ASPI as well.
----------------------------------------------------------------------
How do I make this caching IDE or caching SCSI card work?
Promise Technology has Win95 versions of its Caching IDE host
adapter drivers, so be sure to grab them. Tekram will also have
drivers for its IDE caching adapter, but the SCSI caching adapter
should work with Adaptec 1540 drivers if they didn't get around to
writing Win95 SCSI drivers yet.
Most of the time, the standard IDE drivers will work with caching
IDE cards, though they won't take advantage of the card's cache. If
you do manage to get a Win95 caching IDE driver, try to set
Win95's own cache to bare minimum (384 KB) so you make good
use of your controller's cache instead. Edit your SYSTEM.INI's
[vcache] section:
[vcache]
maxfilecache=384
Then it will almost solely rely on the controller's cache and free up
valuable memory for your programs.
----------------------------------------------------------------------
How do I make this CD-ROM drive work?
I know of three classes of CD-ROM devices in Win95:
IDE: These work off standard IDE adapters if you have Win95
drivers for the IDE cards. Just plug and play, like you're supposed
to. No fancy CD-ROM controller drivers. And yes, you CAN use
an IDE CD-ROM and hard drive on the same cable, and still get
32-bit access on both devices. The IDE miniport driver takes care
of the gory details. CD-ROM drives alone on a secondary adapter
must be a Master drive; ATAPI spec demands there be a Master
device on each IDE adapter to work properly. Grab Microsoft's
IOS.VXD Update if you're having trouble playing videos etc off an
IDE CD-ROM.
SCSI: Win95 works best with SCSI-II CD-ROM drives,
regardless of your host adapter type. Just get Win95 drivers for the
SCSI card and let ASPI find it. CD-ROM Jukeboxes even work
quite well, though some SCSI-I jukeboxes will have troubles.
Otherwise, PnP works well here, too. SCSI is the way to go for
many such devices in the same computer. There's an update for
some CD-ROM Jukeboxes available if you have troubles.
Proprietary: These include the Mitsumi, Sony CDU-3xx,
Matsushita (Panasonic/AT) interfaces. These require a CD-ROM
miniport driver specially designed for the card and the drive
combination you have! For example: You can't use a TEAC
CD-ROM with a SB Pro CD-ROM card driver; you have to use a
TEAC driver designed for the SB Pro card and TEAC drive.
Proprietary interfaces include those built into sound cards; most of
the time they emulate one of the three proprietary CD-ROM cards,
and you can use a Win95 driver.
Using DOS CD-ROM drivers (Avoid at all costs!)
You only need to use a DOS CD-ROM driver if you exit Win95.
This includes the "Restart Computer in DOS mode" option, where
you can't play a game in a DOS session under Win95. Look here
for details on how to do this properly.
If you find you need a DOS CD-ROM driver to use the drive in
Win95, then the drive's broken. See the dealer or manufacturer to
get it fixed or get a Win95 driver for it. I find that real mode
CD-ROM drivers in Win95 are very un-reliable.
----------------------------------------------------------------------
How do I make this Flash PC card or hardcard work on my
notebook computer?
To make the Flash card work, just insert it! Provided you installed
Win95 drivers for your notebook's PC card slots, it will mount it
and assign a drive letter to it.
To make Win95 support PC cards in protected mode, run the PC
Card control panel. The first time you run this, it offers to install
32-bit support. Let it do so! It will also remove any real mode and
Win 3.1 drivers it recognizes, but for weird PC card software you
might need to do some trimming afterwards. Just hide or delete
your DOS startup files, and trim off any unusual entries in
SYSTEM.INI.
----------------------------------------------------------------------
How do I make this tape drive work?
Microsoft's backup program only works with cheap tape devices,
like the floppy port and parallel port tape drives. If you have one of
these then just use the built in backup program. For other kinds of
drives, see below.
SCSI tape drives
Colorado Memory Systems, who wrote the MS Backup for
Win95, was kind enough to release a version that works with more
tape devices. Download Colorado Backup 1.51 and install it, for a
Win95 tape drive subsystem that supports SCSI tape drives. Get
excellent speed and reliability with this software and SCSI tape
drives.
NOTE: (Sigh) Colorado, and HP, stopped making their
Colorado Backup 1.51 free to all, and have started shipping
version 1.60 with all new HP tape drives. So it looks like we
have to pay for this. I suggest purchasing Arcada's Backup
Exec for Win95 in its place.
WARNING: Colorado's HPBACKUP 1.60 and their newest
TRAVAN T4000s tape drive sucks! The drive sticks half way
through a back up on an Adaptec 1520 card or on a Sound
Blaster 16 SCSI-II. If you own anything with Adaptec's
AIC-6360 chipset, don't buy this drive!
Non-SCSI tape drives (Floppy, parport, FC-20, whatever)
If you own a Colorado non-SCSI tape drive, Download Colorado
Backup 1.51. Version 1.51 also handles TRAVAN parallel port
drives and floppy based drives attached to an FC-10 or FC-20
controller card. Non-Colorado customers should ask their
manufacturer for Win95 versions of their software. For example:
Arcada supports Conner floppy-based tape drives. The reason
behind this is Colorado's tape drivers will FIND non-Colorado
drives, but the backup program will blatantly ignore them. Ahh...
what do you want for free?
Conner also has a basic Win 3.1 version of Backup EXEC patched
to support Win95 long filenames and Registry back-ups; check
with your tape drive dealer for a free update.
Microsoft's built in back-up program works with old cheap
QIC-40 and QIC-80 class devices attached to a floppy port or
parallel port, and you won't really get a performance boost with
third-party software here anyway.
----------------------------------------------------------------------
How do I make this removable drive work?
SCSI is your best, and in some cases, your only choice for
removable drives.
Just get a good Win95 compatible SCSI adapter and you can pick
& choose between many optical, SyQuest, floptical, whatever...
drives. The SCSI driver will find and mount any such devices it
finds, though some disks require partitioning. You can't partition
removable disks using FDISK, but Adaptec just released their
EZ-SCSI software for Win95, which includes a removable disk
partitioned. EZ-SCSI 4.0 will work on pretty much any SCSI
adapter, because Win95 has ASPI support built in. Non-Adaptec
owners can buy it. Adaptec's WFDISK (Windows disk partitioner)
for Win 3.1 will work too, as it uses ASPI.
----------------------------------------------------------------------
How do I make this un-listed mouse work?
Use the Standard mouse driver. Win95 has three standard drivers
for three different mouse ports; serial, PS/2, and Bus. The Bus
Mouse driver will work with mice plugged into an ATI Graphics
Ultra card.
Since no one designs mice for something other than these three
connectors, you're probably better off getting a replacement mouse
if it doesn't work with Win95. For $10.00 you can find a good
serial mouse.
----------------------------------------------------------------------
How do I make this graphics tablet work?
Both SummaGraphics and CalComp have Win95 versions of the
WINTAB interface, for their tablets. For other tablets you should
see about switching them to emulate a Summa or CalComp tablet,
or check with your manufacturer. As more pointing device makers
write Windows NT support, Win95 support will increase.
Many tablets work alongside of mice; when you move the mouse,
motion is relative, and when you move the tablet motion is absolute,
depending on the range of tablet you calibrated your screen to.
----------------------------------------------------------------------
How do I make this MIDI keyboard work?
Load a Win95 driver for your MIDI interface, and use the same
Win 3.1 software you used before, to record your MIDI
keystrokes and other events. Win95's Sound Blaster drivers
support MIDI through the joystick port, and MPU 401 compatible
cards will work with the MPU 401 driver. Microsoft also included
an MT-32 driver.
----------------------------------------------------------------------
How do I fix hardware conflicts?
Device Manager is your best tool for resolving conflicts. Any device
that failed to start will have a (!) identifier with it, indicating some
kind of failure. Bringing up properties for that device will go into the
details.
If your card causes a hardware conflict, you can adjust its settings
with the Resources tab. If your card uses jumpers, you will need to
power off the computer and adjust them, before the device will
work. If it is a software configurable device, adjusting the resources
may allow the device to start up without having to re-start the
computer. Sound cards often react like this.
You might have a resource conflict with a real-mode driver, or a
Win 3.1 driver. These you can't resolve using Device Manager, but
you can tell Device Manager to reserve resources for such devices.
Double-click on "Computer" in Device Manager, and you can view
all resources in use, or reserve resources for non-Win95 drivers.
Reserving memory resources this way works like EMMExclude=
lines in SYSTEM.INI.
----------------------------------------------------------------------
How do I get a list of what card is using what IRQ? (or
whatever)
Bring up Device Manager and double-click on "Computer". This
will let you view IRQs and other resources in use by Win95 drivers.
You can also hit Print on the Device Manager sheet, which will
print a whole "MSD" style report of hardware resources in use.
----------------------------------------------------------------------
How do I tell Win95 about cards it doesn't have drivers for?
Bring up Device Manager and double-click on "Computer". Hit the
"Reserve Resources" tab, and tell it which IRQs, DMA channels,
etc are in use by non-Win95 drivers. Reserving memory like this
works just like excluding addresses in EMM386, or using
EMMExclude= in SYSTEM.INI.
You MUST do this if you use real mode drivers or Win 3.1 drivers
that Win95 can't recognize, otherwise when you install a PnP
device it may try to allocate the used resources to the new device!
----------------------------------------------------------------------
Using "Safe Mode" to fix hardware problems
Safe Mode is a debugging mode which allows you to fix problems
without loading the offending drivers. You should not have to run
Safe Mode for any other purpose, in fact you can't run any big
applications, except Device Manager, while in there. ScanDisk
works in Safe Mode, but it takes much longer to perform disk
checks.
To start your computer in Safe Mode, hit F8 on "Starting Windows
95...", then select Safe Mode from the choices. This option
automatically comes up if you interrupt Win95's boot up process,
or it freezes up or otherwise fails to start.
Also, while in Safe Mode, Device Manager cannot tell you about
resource conflicts, because the drivers didn't load. You might also
notice drivers for hardware you don't have; they will appear if there
were remnant Registry entries for them. These driver-remnants are
good candidates for removal!
----------------------------------------------------------------------
Basic ISA Plug & Play theory (Don't bother if you don't like
details)
A PnP BIOS keeps a record of resources in use through a
Non-Volatile RAM (NVRAM), usually part of its Flash BIOS
EEPROM. When you add a device, Win95 tells the BIOS to add
the resources in use to this list. A BIOS must have these calls
available to Win95 or it will never know about what the OS added
or reserved. The NVRAM is not the same as CMOS RAM, which
makes me wonder why they don't just replace the CMOS with
NVRAM for storing other settings, like lost hard drive parameters.
Heh heh...
Also, when you install a PnP device, the BIOS polls it for the
resources it requires. The PnP device will have "Preferred",
"Acceptable", and "Marginal" operating resource requirements. The
BIOS will assign resources based on what the device can use, and
record the resources used in its NVRAM. Win95 can ask the
BIOS what resources are in use, and it can ask the BIOS if any
new devices exist, which is when you get the "Windows has found
new hardware" message. On a Non-PnP system, Win95 handles
all PnP requests by itself and stores config info in the Registry.
Buggy BIOSes might not handle cards with multiple devices on it. If
you think you have a buggy BIOS, see about disabling its PnP
features and let Win95 take over as PnP manager. In this condition,
Win95 stores all resources in use in its Registry and polls PnP cards
by itself.
----------------------------------------------------------------------
Basic PCI Plug & Play theory (Don't bother also)
PCI was Plug & play by design. A PCI BIOS will assign resources,
but the PCI cards don't care what resources they get. Often, the
PCI cards end up in unusual I/O spaces (like above the 3FF range
of the original XT).
Some PCI cards have hard-wired resource requirements (like
video cards), but the newest video cards are beginning to wean off
that requirement, as games stop depending on VGA and use
DirectDraw under Win95.
As per ISA PnP, The BIOS keeps its PCI config info in its
NVRAM, and Win95 keeps a copy in the Registry.
----------------------------------------------------------------------
Other PnP theory (SCSI, monitors, printers, PCMCIA, etc)
SCSI: Supposedly you can power-on a SCSI device while you
computer is running, and Win95 will enumerate and mount it
instantly! OK, not entirely. Sometimes it takes a few presses of F5
in Explorer before the new device appears, but it should work. The
newest SCSI peripherals can auto-configure themselves, where the
host adapter assigns them a SCSI ID. Normally, Win95 ASPI will
scan the SCSI bus on power-up and present you with the "Found
new hardware" requester.
NOTE: A handful of SCSI drivers for Win95 seem to be missing
Logical Unit Number (LUN) support. LUN support lets things
like CD-ROM Jukeboxes work, by assigning a drive letter to
each LUN. The result is: You will only see ONE device and not
six or seven. To fix this, get an updated Win95 driver for your
SCSI card, or get a different card (All Adaptec drivers for
AHA-1510 and up have LUN support; others you might be able
to turn on LUN support in their "Settings" tab in the Device
Properties.) Also check out MS's CD-ROM Changer Driver
Update.
Monitors: Win95 video drivers can poll the monitor for scan rate
information, if the monitor can reply back. Somehow it does this
through the VGA cable, but I really don't know how!
Printers: PnP printers are just starting to show up. This is where the
printer sends back info about itself on a bi-directional parallel port.
The "Windows has found new hardware" requester will show up,
asking you for a Win95 printer driver, and you can begin using the
printer right away.
PCMCIA: If you have a notebook computer, you need Win95.
Forget that messy DOS PC card driver nonsense and
incompatibilities with certain PC card chipsets, and special "no card
services" drivers. Win95 runs Card Services in protected mode,
using no conventional memory, and will give you the "Found new
hardware" requester when you insert a new card for the first time.
Modems work straight away with Win95 TAPI programs. Net
cards will re-connect to the network for you when you insert them.
SCSI cards will mount all devices on its cable. And best of all: You
can still use dumb DOS programs that require EMS memory at the
same time!
----------------------------------------------------------------------
Top ten hardware mistakes
10) Using a DOS CD-ROM driver
9) Using real mode PCMCIA drivers (DOS PCMCIA sucks!)
8) Using a Gravis Ultrasound with Win 3.1 drivers (Visit Gravis,
GUS owners, and get your fair support!)
7) Running a Win 3.1 setup program to install drivers
6) Running a DOS setup program to install Win 3.1 drivers
5) Installing a Plug & Play modem without enabling Plug & Play
4) Buying a piece of hardware without Win95 support
3) Buying a whole bunch of HDs, CD-ROM, tape drive, scanner,
without considering SCSI
2) Buying a notebook computer without Win95
1) Buying an IBM compatible with an Award PnP BIOS (Upgrade
to MR BIOS soon!)
----------------------------------------------------------------------
[Back to Table of Contents]
--
============================================================// //========
= "I am Gordon of Winterpeg. Windows WAS futile." // // =
= Find out why: http://www.intouch.bc.ca/win95 // // =
= Personal E-MAIL: gordonf@vcn.bc.ca \\ \\// // =
= Home Phone: +1-604-526-8724 \\ XX // =
= \X/\X/ =
= "I am Hitler of BorgSoft. I am the middle inital of William H. Gates. =
= Your work will be Microsofted. Resistance is futile. Heil Windows. =
=========================================================================
Yeah I use an Amiga at home. If you don't like my computer, dial
1-800-DIE-BILL and tell someone who cares.
----------------------------------------------------------------------
Path: news1.ucsd.edu!ihnp4.ucsd.edu!swrinde!newsfeed.internetmci.com!info.ucla.edu!news.bc.net!news.mindlink.net!van-bc!unixg.ubc.ca!freenet.vancouver.bc.ca!gordonf
From: gordonf@vcn.bc.ca (Gordon Fecyk)
Newsgroups: comp.os.ms-windows.win95.misc,comp.os.ms-windows.setup.win95,comp.os.ms-windows.networking.win95,comp.os.ms-windows.apps.compatibility.win95,comp.answers,news.answers
Subject: Win95 FAQs and Answers Part 7 of 14: Networking
Followup-To: comp.os.ms-windows.win95.misc,comp.os.ms-windows.setup.win95,comp.os.ms-windows.networking.win95,comp.os.ms-windows.apps.compatibility.win95
Date: 30 Jun 1996 16:31:55 GMT
Organization: Vancouver Regional FreeNet
Lines: 1896
Approved: news-answers-request@MIT.EDU
Message-ID: <4r6a5r$80p@milo.vcn.bc.ca>
NNTP-Posting-Host: opus.vcn.bc.ca
Summary: These postings list many questions asked in said newsgroups,
and answers them as best as I can. I make references to other
Web sites and FAQs when appropriate. Visit the WWW home of
this FAQ (http://www.intouch.bc.ca/win95) for the appropriate
links. This section is the 7th: Networking
This section will be split into NetWare and non-NetWare
sections on the next update.
X-Newsreader: TIN [version 1.2 PL2]
Xref: news1.ucsd.edu comp.os.ms-windows.win95.misc:111604 comp.os.ms-windows.setup.win95:10981 comp.os.ms-windows.networking.win95:7515 comp.os.ms-windows.apps.compatibility.win95:3580 comp.answers:15519 news.answers:61920
Archive-name: windows/win95/faq/part07
Last-Modified: 1996/07/01
Posting-Frequency: Every two months
URL: http://www.intouch.bc.ca/win95/faq7.htm
7) Windows 95 networking
Windows 95 networking basics you MUST know
How do I connect to...
...other Windows 95 computers?
...other Windows for Workgroups computers?
...Novell NetWare (tm) servers?
What do I have to do to a NetWare server to work with
Win95 clients?
NetWare 2.x
NetWare 3.x
NetWare 3.12
NetWare 4.x and NetWare Directory Services
How do I run DOS TSRs in a login script?
Using clients from Novell (Client32, NETX, VLM)
How do I connect to NetWare servers while I'm not
running Win95?
How can I receive NetWare popup messages?
Why don't I get a NetWare login prompt?
Bugs to watch out for, and patches
How do I disable password caching?
Top ten NetWare mistakes
What does Client32 offer that MS's client doesn't?
(NEW)
What's this about Client for NetWare being only
NetWare 2.2 compliant? (NEW)
...Windows NT servers and Windows NT domains?
How do I get Win95 to honor NT %username% ? (and
other NT user variables) (UPDATE)
Bugs to watch out for, and patches
How do I disable password caching?
How do I log in to multiple domains?
Top ten NT network mistakes
...Banyan Vines( tm) servers? (Who uses this anyway?)
...LANtastic( tm) servers? (Yes Virginia there IS a 32-bit
LANtastic!)
...AppleTalk (tm) AFP servers?
...IBM OS/2 LAN Servers? (NEW)
...other network servers? (DOS client advice)
The Internet?
How do I share my hard drive or printer to...
...other Win95 users?
...on The Internet?
...other Windows for Workgroups users?
...other NetWare users? (Avoid if possible)
How do I make RPRINTER work?
...on a network using NDS? (NEW)
...Macintosh (tm) users?
...other computers' users? (SAMBA network clients)
How do I run DOS TCP/IP or packet-driver apps in DOS
sessions in Win95? (NEW)
How do I print to HP JetDirect (tm) printers on the network?
(UPDATE)
JetDirect Port Aliasing, or How do I print from DOS
programs to JetDirect Printers?
I heard that Win95 has (this cool feature). How do I set up...
...system policies?
...on a NetWare network?
...on a NetWare network using NDS?
...on a Windows NT network?
...on another network with a 32-bit client?
...on another network with a DOS client?
...on a peer to peer Win95 network? (It is possible, but
not easy!)
...user profiles? (Requires system policies to work
effectively)
...on a stand-alone workstation?
...on a NetWare network so it'll follow the user around?
How do I make roving Desktop and Start Menus
work on NetWare?
...on a NetWare network using NDS?
...on a Windows NT network so it'll follow the user
around?
...on another network with a 32-bit client? (Not possible
on DOS clients)
Why user profiles is a really cool and useful feature!
...remote administration?
...on a NetWare network? (UPDATE)
...on a NetWare network using NDS? (NEW)
...on a Windows NT network?
...on a Peer Win95 network?
...user level access to shared drives and printers? (as
opposed to multiple passwords)
Windows 95 has (this security bug). How do I fix...
...the "cancel" button on the login window?
...the Samba bug I heard about?
...the NetWare C$ bug I heard about?
...the password caching bug?
How do I disable password caching?
How to enable user level access to eliminate the need to
cache passwords
Visiting Rich Graves' Win95NetBugs site for details
Useful network utilities
----------------------------------------------------------------------
Windows 95 networking basics you MUST know
I briefly described NDIS 3.1 back in the Hardware section, but I'll
cover it quickly here again. It's a Plug & Play version of Microsoft's
Network Device Interface Spec, which lets you do cool stuff like
dis-connect from the network when you un-dock your notebook,
then re-connect as soon as you insert a PCMCIA network card, or
dial in with your modem.
Win95 has four classes of network components: Clients (For using
shared resources), Services (for sharing or controlling shared
resources), Transport Protocols (To communicate over network
cards), and the network cards themselves. Protocols can use any
network card, and usually, clients and services can use any protocol
(there are specific dependencies, such as Client for NetWare on
IPX/SPX Protocol). Clients are actually file system drivers, which
use local caching (VCACHE) to off-load the server a bit.
NDIS 3.1 software does NOT occupy conventional memory, so if
you have all Win95 clients, services, drivers, and protocols, you
can run your DOS programs within Win95 without worrying about
how much RAM you have. This goes for IPX network games too.
All net components in Win95 should conform to this, otherwise
don't waste your time. This includes avoiding Novell's Client32,
because they're forcing a 32-bit ODI, and .NLMs, and crap that
belong in a NetWare server. Be Warned: I'm quite anti-Client32,
and I tend to preach using MS's clients for the sake of
simplicity and speed. If you have a problem with this, leave this
page now.
----------------------------------------------------------------------
How do I connect to other Windows 95 computers?
Get a Win95 compatible net card for each machine, tie the cards
together however they're supposed to tie together, and install these
components on it:
Client for MS networks
Win95 net card driver
NetBEUI Protocol (Or any single common protocol;
NetBEUI's the easiest to set up, but IPX will get you a bit more
speed)
File & Print Sharing for MS Networks
Usually, when you insert a net card for the first time, Win95 Setup
will install Client for MS and Client for NetWare networks, and all
the needed components, at the same time. After everything works
you can remove un-needed stuff to make it faster.
Use unique computer names and a common workgroup name in the
Identification tab. To ease browsing difficulties, set aside one
computer to be turned on all the time (the one that has the printer is
a good candidate), and set "Browse Master: Enabled" on that
machine's File & Print Sharing properties.
----------------------------------------------------------------------
How do I connect to other Windows for Workgroups
computers?
Set up the Win95 machine as you would for networking Win95
machines together. The WFWG machines use the same protocols,
from the Transport protocol up, as Win95 does. On the WFWG
machine, tell it to install Microsoft Windows Network support.
Set aside one Win95 machine to act as Browse Master, as Win95
machines take browse master precedence over WFWG machines.
This will ease browsing troubles. Set that machine's FPS properties
to "Browse Master: Enabled".
NOTE: If you use IPX Protocol on the Win95 machine and
you're connecting to WFWG servers, turn on "I want to enable
NetBIOS over IPX", because the WFWG servers normally use
NetBIOS over IPX. Otherwise change the WFWG station's
protocol to "IPX/SPX Transport", instead of "IPX/SPX
Transport with NetBIOS". Microsoft refers to this as Direct
Hosting over IPX, rather than through NetBIOS, which
explains the speed boost you'd get.
----------------------------------------------------------------------
How do I connect to Novell NetWare (tm) servers?
First, ask your administrator if he prepared the server for Win95
clients. This is critical, if you want your administrator to like you.
Then, Install Client for NetWare networks, and fill in the "Preferred
Server" value in CNW's Properties. Set your primary login to
"Client for NetWare Networks".
Also, install IPX/SPX protocol (It will install automatically along
with Client for NetWare), and select a frame type in its Advanced
properties. Auto-detect does not always work. Your choice of
frame type depends on what the NetWare server uses. NetWare
3.11 and earlier typically use 802.3, later servers use 802.2.
The next time you restart, you will get a NetWare login requester
asking for your name and password. When you feed it this, your
NetWare login script will execute.
More details for NetWare Directory Services later.
----------------------------------------------------------------------
What do I have to do to a NetWare server to work with
Win95 clients?
Many, many, people have crashed NetWare servers with Win95
computers using Microsoft's Client for NetWare. A lot of this is
from the client pushing the server, but a lot more of it comes from
mis-understandings from users!
The most critical thing to do to a NetWare server is to update its
software. Old .LAN drivers might not keep up with the Win95
clients. An old '386 or '486 class server will also have troubles
keeping up with Pentiums running Client for NetWare. Novell's
VLM Client for DOS causes many of these troubles too. Details
are at Rich Graves' Win95NetBugs site.
Special notes for server versions below:
NetWare 2.x
Ensure you disable Packet Burst and long filenames on the Win95
clients, by adding these lines to the clients' SYSTEM.INI file:
[nwredir]
SupportBurst=0
SupportLFN=0
You can also use a non-burst frame type (802.3), and enforce no
LFNs via system policies.
NetWare 3.11
These servers have a nasty time with Win95 clients using long
filenames and packet burst. Use the NetWare 2.x techniques
above, or apply PBURST.NLM and the OS/2 name space fix,
available at Novell's NetWire site. Back up your server before
powering up a Win95 client for the first time!
Client for NetWare will not use long filenames on a NetWare 3.11
server unless you explicitly tell it to, meaning you KNOW you have
the name space patch installed. If you want to use long filenames on
a patched NetWare 3.11 server, you should set up a system policy
to enforce LFN usage, or include:
[nwredir]
SupportLFN=2
in SYSTEM.INI.
NetWare 3.12
This, according to my observations, is a patched and bug-fixed
NW 3.11. This is the server that Microsoft did most of their client
testing on, and it will work with packet burst and long filenames
without patches. You still need the OS/2 name space to support
long filenames. Set the frame type on the Win95 stations to
Ethernet_802.2.
NetWare 4.x and NetWare Directory Services
If you don't need to use NDS and you have Bindery emulation
available on the server, you can use the Client for NetWare as per
NetWare 3.12 servers. The big catch is it won't recognize an NDS
login script! To work around this, you can hand-copy the NDS
system login script to SYS:PUBLIC and call it NET$LOG.DAT.
Another work-around is to log into the server in Bindery mode (An
option available in LOGIN.EXE, or just log in with regular Client
for NetWare) and run a copy of NW 3.12's SYSCON to make
system and user login scripts for Bindery mode. Details are in KB
article Q128253.
However, Microsoft released an NDS Service which will use NDS
login scripts and work with NDS programs. Install Services for
NDS by adding it as a Service (you still need Client for NetWare
installed). Services for NDS is part of Microsoft's Win95 Service
Pack 1, Admin Edition. You will also need the Shell32 Fix and the
NWSERVER fix, which come with Service Pack 1, and six DLL
files from Novell which come with the NetWare 4.x server. You
will still need Bindery emulation for peer sharing (File & print
sharing for NetWare) and Remote Administration. Set the User
Level security provider to point to this server running Bindery
emulation and you're all set. Or just don't bother with peer sharing
via NetWare (Which you shouldn't do anyways except for Remote
Administration.)
I had the opportunity to finally try Services for NDS this week (25
APR 96) and it appears to run just fine. After I hand-copied all
DLL files from Novell's SYS:\PUBLIC\CLIENT\DOSWIN
directory to SYS:PUBLIC, I could run NWADMIN and the other
Win 3.1 NDS utilities in there.
NOTE: The NDS client still depends on accurate Bindery
emulation running on the Preferred Server. If you use any
additional services that depend on User Level Security (such as
Remote Administration) be sure you set the Bindery context to
match the Organizational Unit you want your user list for. In
an absolute worst case, set the Bindery context to point to each
of your Organizational Units and Organization. Type this at
the server console, or include it in AUTOEXEC.NCF (Of
course, use your real unit names, not the example MYORG):
Set Bindery Context = O=MYORG,OU=UNIT1.MYORG,OU=UNIT2.MYORG
How do I load TSRs from a login script?
You can't. Win95 runs the login script from a single DOS session,
which completely unloads when the login script finishes. Loading
TSRs from a login script is stupid anyways, in fact, loading DOS
TSRs in Win95 in general is stupid.
But if you have to load network TSRs, Win95 did keep the old
WINSTART.BAT capability. WINSTART.BAT, in the
%WINDIR%, executes just after all the network components load,
and just before the login prompt comes on. Load your TSRs in that.
They will be available from all DOS sessions afterwards. Details are
in KB article Q127794. Yes this does work; I can run Cheyenne's
ARCSERVE (tm) for Windows 5.01 by loading BREQUEST.EXE
this way. Which reminds me: Do any of you know of a 32-bit
BTRIEVE requester for Win95 yet?
----------------------------------------------------------------------
Using clients from Novell (Client32, NETX, VLM)
I won't touch Client32 yet; you can read about it at Novell's
Client32 Home Page and make your own judgments. However,
some applications need to see real mode NetWare clients (even
though all the real mode hooks are there with Client for NetWare,
and with Services for NDS). So...
To use a DOS client, you will need all the regular DOS client
software (LSL, IPXODI, etc). Once you have all that in place, you
can add Win 3.1 support from Network Control Panel as a Client.
NETX: Novell no longer recommends running NETX, but it does
work as it did with Win 3.1. Install the DOS client, then add
"Novell NetWare Shell 3.x" as a Client from Network Control
Panel. Setup will prompt you for Novell's disks when needed.
VLM: This works better with Win95 than NETX, and is "Safer"
than Client for NetWare for your finicky programs and NDS apps.
Try this as a last resort, if you can't get the app makers to clean up
their programs. Use Novell's regular DOS installation of this client
(Don't add the Windows software from Novell's setup), then add
"Novell NetWare Shell 4.x and above" as a Client from Network
Control Panel. Setup will prompt you for Novell's disks when
needed.
NOTE: Do NOT use Client for MS/File & Print Sharing for MS
networks alongside a real mode Novell client! Neither Novell nor
Microsoft support this, and the mix of real mode/protected mode
clients can cause loss of hair for network administrators. Use all
protected mode clients and services if you want NetWare logins
AND peer sharing. Client/FPS for MS networks works great
alongside Client for NetWare, and even Client32 from Novell.
Client32? Well, I don't believe in it myself, because Novell
introduced its server concepts to Win95; concepts that belong in
the server. Read all about it in Novell's Client32 FAQ.
At either rate, try to avoid this, unless you like seeing multiple
instances of IPX or you don't use a notebook computer (Novell
didn't get Dial-up Networking working right with Client32 quite
yet). If you update the server, Win95 clients can run VLM or Client
for NetWare safely.
WARNING: Novell's starting their Windows 95 conspiracy.
(OK this is my imagination but think about it for a bit...) They
released an NPRINTER "Open Beta" a while back, which
requires their Client32 because it uses NLMs instead of VxDs.
Read about Win95 NLMs in Novell's Client32 FAQ; they're
basically writing a CLIB/NLM subsystem for Windows 95 that
completely replicates Win95's VxD functionality and takes up
more space. I figured out how to make MSPSRV (Microsoft's
PSERVER for Win95) working in NDS so you can use that
instead.
Why do I care? You ever see Novell writing NLM subsystems
for the Macintosh client? For the OS/2 client? No. So why are
they wasting their time here? What makes Novell so special
they can't work with the OS instead of against it?
----------------------------------------------------------------------
How do I connect to NetWare servers while I'm not running
Win95?
Win95 Network Setup installed a real mode client for NetWare at
the same time as the protected mode one. If you exit to DOS
("Restart in DOS mode") or boot to "Command Prompt Only", and
you're using Microsoft's Client for NetWare, you can log in to the
NetWare server by typing
NET START NWREDIR
at the DOS prompt. This will load a NETX compatible client using
NDIS2 drivers and protocols. You can then change to your login
drive and perform a normal DOS client login. Since it's only a
NETX compatible client it can't perform NDS logins; so you could
try:
NET START NWLINK
VLM
Which uses Novell's VLM client, to do NDS logins. I haven't tried
using Microsoft's IPX and Novell's client together, but in theory it
should work. If it doesn't, you can always load Novell's net card
drivers (LSL, etc) and VLM.
NOTE: NWREDIR's real mode components take more
conventional memory than a NETX client would, so you should
only use this if your application can't run in a DOS session, or
if you're performing any debugging. However, these
components will automatically load high if you have upper
memory available. You should prepare a special PIF file for
this kind of configuration.
----------------------------------------------------------------------
How can I receive NetWare popup messages?
With Client for NetWare, use WINPOPUP. Add it from
Add/Remove Programs/Windows Setup, in the Accessories
components. Keep this loaded or you won't be able to see or send
pop up messages. WINPOPUP will receive messages from
Bindery and NDS clients, but you can only send messages to
Bindery clients. Novell's SEND command in a DOS session will let
you send messages to NDS clients.
You can force WINPOPUP to load by keeping a copy of it in
SYS:PUBLIC (or any other public place) and enforce a System
Policy to run it on start-up. In Default Computer/System/Run, insert
an entry with a UNC path to WINPOPUP.EXE, such as
\\SRV\SYS\PUBLIC\WINPOPUP.EXE. This way, the users don't
have any excuse for not seeing pop up messages.
NOTE: Enforcing a policy like this will prevent any other
programs that run from this Registry entry (like SAGE.EXE
from MS Plus) from running. If you have to, include an entry
for SAGE.EXE as well (No error messages come up if the file is
missing, so no worries if some machines don't have Plus) or
any other programs that run from this Registry key (Example:
MSPSRV.EXE; Print Agent for NetWare). Again, if a machine
doesn't happen to have the file, the user won't notice an error
message or anything.
I've tried a couple of ways of getting WINPOPUP in people's
faces without disturbing the Run Registry key. One of them is
to set up a custom Startup folder in the server, but this requires
User Profiles and prevents anything else running from the
Startup group. I've also tried including it in the system login
script (#C:\WIN95\WINPOPUP); this works very well but it
won't start minimized. I can't seem to get the START.EXE
command working in a login script but feel free to try it; the
login script processor will run any DOS or Windows program.
There's of course, putting it in load= in WIN.INI, or better yet,
sticking a shortcut (WINPOPUP.LNK) in the load= in WIN.INI
so you can start it minimized, but you have to go edit each
Win95 station to do it. (Sigh)
For all of Novell's clients, their supplied NWPOPUP works just
fine. I'd even hazard a guess that NWPOPUP would work on
Client for NetWare, but I haven't tried it yet.
----------------------------------------------------------------------
Why don't I get a NetWare login prompt when Win95 starts?
(NEW)
This is related to a password caching problem I read about on
Win95NetBugs. If the .PWL file is around 900 bytes, it will
by-pass the NetWare login prompt and start Win95 straight away.
Login scripts won't execute, and the only way to get them to
execute is to Shut Down/Close all programs and log on as different
user, and re-log in.
To correct this, delete all .PWL files in your %WINDIR% and
re-start the computer. While you're at it, disable password caching
via system policies.
----------------------------------------------------------------------
Bugs to watch out for, and patches (and links to appropriate
Win95NetBugs pages)
Automatic Frame Detection Bug: Auto detect does not always
work, especially in multi-protocol networks. Bring up IPX
properties and manually select a frame type.
NWSERVER security bug: If you use Remote Administration, it
may keep the admin share active after you dis-connect! Apply
Service Pack 1 to fix.
SAP Advertising kills IPX routing: When Win95 stations act like
NetWare servers, all hell can break loose. SAP traffic can bog the
network, clients might log in to a Win95 station instead of the real
NetWare server. Don't use File & Print Sharing for NetWare to
share out printers and files to non-Win95 clients; use the server and
print queues like you're supposed to, or use Client/FPS for MS
networks instead. More on print sharing via RPRINTER later.
NOTE: Novell's latest patch sets for NetWare 3.11, 3.12, and
4.1 correct routing problems caused by lots of SAP traffic.
Visit netwire.novell.com and get the base OS patch sets for
your version of NetWare.
Password caching: Win95 will store your login password locally,
and the password encryption is easily cracked! Apply Service Pack
1 to fix, or better yet, disable password caching and use User Level
Security for peer sharing. Check out the System Policies part to
find out how to do force this.
Server self-destructs when booting Win95: Any general mishap that
occurs to the server that either causes an ABEND or otherwise kills
it (I won't get into technical details; all I know is that Win95's
demonstrated that it does bad stuff to NetWare servers). Check the
steps you need to prepare the server or dis-arm the Win95 client.
----------------------------------------------------------------------
How do I disable password caching?
Set up a system policy file, and include "Disable Caching of Login
Password" or "Disable Password Caching" in Default
Computer/Network.
----------------------------------------------------------------------
Top ten NetWare mistakes
10) Using a '386 machine as a server with Pentiums running Win95
as clients
9) Installing File & Print Sharing for NetWare without knowing
what you're doing
8) Enabling long filenames on a NetWare 3.11 server (Patch it
first!)
7) Installing Novell's Client32 out of fear
6) Using regular Client for NetWare to log in to an NDS server
5) Turning on SAP advertising in a large routed network
4) Leaving "Auto-Detect" as the frame type for IPX
3) Not specifying the preferred server in Client for NetWare
properties
2) Not updating the server before adding Win95 clients
1) Not using system policies (Always a good idea to use system
policies for basic stuff)
----------------------------------------------------------------------
What does Client32 offer that MS's client does not?
This question bugs me all the way down to Hell. Novell Client32's
features probably won't be used by about 90% of us. For the
remaining 10%, I will assume you already know everything about
Windows 95, and this FAQ will consequently be useless to you.
Thphth.
OK, back to reality: What does Client32 have extra?
Synchronizes time with the preferred server automatically
Lets you log in to multiple NDS trees
Lets you use NetWare over TCP/IP (referred to nby Novell as
NetWare/IP)
Brings Novell's NLM technology to Win95
More control over IPX protocol
Supports Packet Signature for extra security
There are a couple of other tidbits, but these are the biggest
attractive features of Client32. To work around or obtain these in
order using MS's clients:
Use MS's NDS client in addition to the Client for NetWare
(even for Bindery servers) to sync time automatically, or include
#NET TIME in the login script
I thought the whole point of NDS was to avoid multiple
"domains" or directories. Who needs multiple NDS trees?
No answer for NetWare/IP, but understand that NetWare/IP is
just IPX over TCP/IP. I would say don't waste time with
TCP/IP and stick with IPX.
NLMs replicate Win95's VxD technology needlessly. We don't
need no stinkin' NLMs in Win95.
IPX is the easiest routable protocol to implement. The only
settings I found needed to change are frame type, max sockets,
and max connections, all controlable with MS's IPX
"compatible" protocol just fine.
Packet Sig belongs in the realm of Maxwell Smart and the Cone
of Silence. If you're not in this realm, don't bother.
The point I'm trying to make is, try to use the stuff that comes with
the OS before resorting to memory-hogging add-ons. Client32's the
biggest hunk of code to grace the networking scene and it
complicates the system far too much for 90% of us.
----------------------------------------------------------------------
What's this I heard about Client for NetWare only being
NetWare 2.2 compliant?
I've heard bullsh*t about this since Novell's tech note
announcement regarding FPS for NetWare. Novell states that
Microsoft's File & Print Sharing for NetWare identifies itself as a
NetWare 3.12 NCP server, but really uses codes and packet types
from NetWare 2.2 servers. This is why that Client32 can't see
Win95 computers running FPS for NetWare, even with SAP
advertising turned on.
OK, I believe that MS reverse-engineered NetWare 2.2 to make
FPS work. What I don't believe is everyone else claiming that the
REST of Client for NetWare is only 2.2 compliant. NetWare 2.2
clients (and MS's FPS for NetWare) can't do Packet Burst. Client
for NetWare and NetWare 3.12 servers (and better) can.
NetWare 2.2 clients (like NETX) can't log into NDS trees. OK,
neither can Client for NetWare, but the NDS add-on fills that gap.
You're going to say that MS's NDS client is only NetWare 2.2
compliant?
And so what if FPS for NetWare only acts like a 2.2 server? I only
recommended FPS for NetWare for sharing between Win95
machines and for Remote Administration. In these two jobs, FPS
for NetWare works as designed.
And here's a good one for Novell. In the same document, they
claim that Remote Registry Service depends on FPS for NetWare.
Wrong. (Insert buzzer sound here.) While Remote Registry
depends on User Level Security, that security comes from a
security API in Win95 (SECUR32.DLL), which goes through the
security provider software that comes with the CLIENT. It does
not depend on any file sharing service. If Novell wanted to make
Client32 work with remote administration, they could write their
own security provider code. Bet they can't do that in NLMs.
Thphth.
----------------------------------------------------------------------
How do I connect to Windows NT servers and Windows NT
domains?
Microsoft released Windows NT 3.51 purely to support Windows
95 clients. If you have Windows NT servers or workstations and
Win95 workstations, upgrade to NT 3.51. Save yourself the
hassles.
If you aren't using NT domains, you can connect to the NT
workstations and servers as you could any MS Windows Network
client; install Client/FPS for MS networks.
Client for MS Networks can also perform NT domain logins,
similar to how the NetWare client performs NetWare logins. You
just specify that you want to log in to a domain in the Client for MS
properties. You needn't specify the name of the domain controller;
just the name of the domain. Unlike the domain client in Windows
for Workgroups, however, you log in to the domain first, then into
Windows.
Upon re-boot, Win95 gives you an MS Client login prompt. Feed it
your username and password, and your NT login script will
execute.
----------------------------------------------------------------------
How do I get Win95 to honor NT %username% ? (and other
NT user variables)
Win95 isn't Windows NT, so it can't receive NT user profiles
which include the environment variables. However, there's a cool
LanManager utility that works on NT servers: PUTINENV.
PUTINENV copies all the LanManager user variables (including
%USERNAME%) to a DOS client. But it only copies them to the
local DOS session's environment; you will need to copy the variable
to the global Windows environment with WINSET, a utility that
comes with the Win95 CD-ROM.
So, to copy the user variables over during a login, copy
PUTINENV.EXE and WINSET.EXE to the domain controller's
NETLOGON share, then add these lines to the login script:
\\server-name\NETLOGON\PUTINENV L
\\server-name\NETLOGON\WINSET USERNAME=%USERNAME%
(Repeat the WINSET line for any other user variables in the user's
NT profile.)
You could also map a drive and run the programs from that
mapped drive, or even from the client's local hard drive. Since
Win95 supports commands using network paths, however, it's far
easier to just copy them to the server.
For interest's sake, PUTINENV also works with Windows for
Workgroups clients. Of course WINSET won't work, being a
Win32 program, but you could use the same script for WFWG and
Win95 clients without harm. NT clients will GPF on running
WINSET too. Read the note on Rich Graves' Site.
Windows Magazine also has many tips on writing NT login scripts,
and have a sample master login script for your viewing pleasure. It
includes a Win 3.1 equivalent of WINSET called SETW.EXE too.
----------------------------------------------------------------------
Bugs to watch out for, and patches
Since Microsoft meshed Win95 and NT so closely together there
are hardly "any" bugs, but Rich Graves does mention a few at his
Win95NetBugs site.
Hah, I lied! I know two bugs, and they relate to Remote
Administration...
Admin share (\\machine\c$) remains active after you terminate
the Remote Admin session (I noticed this since Service Pack 1)
Domain Admins can edit parts of an NT server's Registry!
To prevent these bugs from creeping up, make sure you protect
that Domain Admins group with your lives.
There's the Password Caching bug of course, but you can disable
password caching.
----------------------------------------------------------------------
How do I disable password caching?
The best way is to set up a system policy which does so. You can
disable caching of the login password, or caching altogether.
----------------------------------------------------------------------
How do I log in to multiple domains?
Although you can't LOGIN to multiple domains, LOGIN and
ATTACH are two very different actions. You will need to establish
a Trust relationship between the two domains, a topic best covered
in Microsoft's NT Resource Kit. Once set up though, you can map
drives to shares on the other domains through the login script, or
browse through Network Neighborhood, as though they were part
of your domain.
----------------------------------------------------------------------
Top ten NT network mistakes
10) Using a LanManager server as a domain controller (hah hah
hah)
9) Using an NT version earlier than 3.51 for Win95 clients
8) Not using system policies (Always a good idea to use system
policies for basic stuff)
(oops... not enough mistakes to fill the list! You got any?)
----------------------------------------------------------------------
How do I connect to Banyan Vines (tm) servers? (Who uses
this anyway?)
Banyan has a 32-bit client for Win95. By what I read on their
installation instructions, it's a proper Win95 client for a VINES
server. I don't have access to a VINES server, so if you have any
insight on this, please tell me.
----------------------------------------------------------------------
How do I connect to LANtastic (tm) servers? (Yes Virginia
there IS a 32-bit LANtastic!)
Artisoft has a Client for LANtastic, that pretty much works like
Client for MS networks! You can map and browse server drives,
share drives with the LANtastic service, capture and share printers,
and have your connections saved per user, via User Profiles.
Because they use the OS nicely, you could use the Client for
NetWare, for example, and LANtastic client at the same time, if for
some unusual reason you didn't want to use Client for MS for peer
sharing. Now this is playing nicely!
NOTE: Artisoft stopped offering their Client for LANtastic on
their web site. Visit Artisoft's site or your favorite vendor for
LANtastic for Windows 95.
----------------------------------------------------------------------
How do I connect to AppleTalk (tm) AFP servers?
Miramar Systems has a Win 3.1 client and server for AFP, which
they managed to hack into Win95. Miramar told me via E-MAIL
that they will release a Win95 client and server in June 1996. With
any luck it can co-exist with other Win95 components.
----------------------------------------------------------------------
How do I connect to IBM OS/2 LAN Servers?
At first I thought MS would've abandoned OS/2 completely, but
according to KB article Q149206, Client for MS networks will
work with LAN Server domains. Specifically, they wrote that
Client for MS works with OS/2 LAN server versions 1.2, 1.3 (and
CSD), 2.0, 3.0, and 4.0.
As such, you can treat the LAN Server domain like the MS Man
Manager or Windows NT domains. Set up the Win95 client
appropriately.
MS noted that file and print sharing are the only services that Client
for MS supports. Apparently, IBM's LAN Server management
software won't run on a Win95 station. Keep a Win 3.1 or DOS
station handy for this.
----------------------------------------------------------------------
How do I connect to other network servers? (DOS client
advice)
Microsoft TRIED to allow weird DOS clients, with Win 3.1
support, to work in Win95 like they did in Win 3.1. Win 3.1
support for networks shows up as a stand alone Client in Network
Control Panel. For example, if you install Novell NETX support,
you don't need to add any protocols or net cards. The big limitation
is you can only install ONE Win 3.1 network client.
The best advice I can give is to only use the network support the
vendor gives you. Don't try to use DOS clients alongside Client for
MS Networks, for example.
If you have to make more conventional memory available, you can
use real mode HIMEM.SYS and EMM386.EXE, and prepare a
normal DOS configuration that will start up before Win95 does. At
this point it would perform much like Win 3.1 did, but it should
work.
----------------------------------------------------------------------
How do I connect to The Internet?
Since Win95 comes with nearly all the components you need to
connect to The Internet, the easiest way is to grab Microsoft's
Internet Explorer and run it. The first time you run it, the Internet
Setup Wizard comes up and asks you a bunch of questions only
your service provider can answer. Get an answer sheet from your
provider for these settings:
Dial-in phone number
Login Name (Not E-MAIL name); may include descriptors like
%PPP or whatever
Login Password (Whatever you chose when you signed up)
IP address and Subnet mask if manually given, or use "My ISP
provides me one"
DNS server addresses (in the form of XXX.XXX.XXX.XXX)
Full E-MAIL address
Mail server address (usually something like mail.nowhere.com)
Mail server username (Usually the same as your login name)
Mail server password (Usually the same as your login
password)
Items to have handy: News server address, outbound mail
server address, Gateway address (if not using default gateway)
These are the items the Internet Wizard will ask you for. The
Wizard will prepare IEXPLORE.EXE, the main Web browser, and
Microsoft Exchange for sending and receiving electronic mail. It will
also prepare a dial-up networking connection with all the right
switches turned on, or off, and install all the needed components
from your Win95 disks or CD-ROM. The only fine-tuning you'll
need to do is to add the news server address to Internet Explorer
(or whatever news reader you want to use), and maybe add an
Outbound Mail Server name to Exchange's Internet Mail
properties, if the provider has a different server to process
outbound mail.
About 99% of us will connect to The Net using a modem and a
dial-up line, but for the rare few of us that have a direct network
connection, the Wizard will work with that too.
Oh yes, it will make you use Internet Explorer. No matter; just use
it to get your favorite Web browser, such as NCSA Mosaic for
Win95, or (ACK!) Netscape, and install that afterwards.
You can always re-run the setup wizard if the provider's settings
change, or if you change providers. You'll find it in your
Accessories group on the Start Menu. I cover the rest of the
Internet stuff in a separate page.
----------------------------------------------------------------------
How do I share my hard drive or printer to other Win95
users?
Install File & Print Sharing for MS networks in your network setup.
If you set up the computer like I told you back in the How do I
connect to other Win95 computers? section, this'll already be done.
Next, right-click on any drive or folder you want to share, and
select the "Sharing" menu. You can specify a read-only or full
access share like you could in Windows for Workgroups, or make
it dependent on password.
----------------------------------------------------------------------
How do I share my hard drive or printer to other Win95 users
on The Internet?
This is pretty tricky because you need to run NetBIOS over
TCP/IP. You can't just type "\\206.116.13.2" and expect a list of
shared resources to appear. Running NetBIOS over TCP/IP
usually requires a WINS server, but you can also do NetBIOS
naming through DNS, or by manually writing an LMHOSTS file,
neither of which I recommend.
One problem I noticed is, if you specify a name in HOSTS or
LMHOSTS, the machine you're referring to had to have the same
name in its Identification tab, on its Network Properties. This tidbit
I got from Rich Graves' site.
Your easiest bet is to obtain a free FTP server for Win95, available
at www.windows95.com. Then the other user can just use their
FTP client or browse using their web browser, using
"ftp://206.116.13.2" as the URL. To find out what your IP address
is (if you have IP addresses assigned to you on the fly), run
WINIPCFG.EXE from the Win95 directory and bring up
properties of the "PPP Adapter", while you're connected.
----------------------------------------------------------------------
How do I share my hard drive or printer to other Windows for
Workgroups users?
Just like you would for Win95 users. Be careful if you use User
Level security, because WFWG clients won't recognize weird
security providers, like NetWare servers. Either share out to "The
World", or specify a Windows NT domain as your security
provider, and have the WFWG client log into it. Or, simply use
Share Level security a'la WFWG.
NOTE: If you chose IPX as your base protocol between Win95
and WFWG computers, you should decide if you want to use
NetBIOS or not, because WFWG has one default (NetBIOS
ON) and Win95 has another default (NetBIOS OFF). Neither
WFWG nor Win95 need NetBIOS over IPX unless you're
specifically running NetBIOS apps, so on the Win95 machine
have "I want to enable NetBIOS" turned off in IPX properties,
and change the protocol on the WFWG machines to "IPX/SPX
Transport" instead of "IPX/SPX Transport with NetBIOS".
Microsoft calls this "Direct Hosting over IPX" which will give
you a speed boost. Windows NT and Workgroup Connection
for DOS also support Direct Hosting over IPX.
----------------------------------------------------------------------
How do I share my hard drive or printer to other NetWare
users? (Avoid if possible)
Depending on whether the clients are Win95 clients or DOS clients,
it can be either really easy or really messy! Complications include
the SAP Advertising bug and the Login bug.
If the clients are other Win95 machines running Client for NetWare,
you merely have to install File & Print Sharing for NetWare
networks, and specify your NetWare server as the security
provider in Access Control. When you re-boot you can share out
drives and printers to specific users in the NetWare server's
Bindery.
Now, if the client runs Win95 there's no real troubles, because
Win95 will perform "Workgroup advertising" which works like the
workgroup naming service (browse master) in WFWG, and this
won't interfere with normal NetWare communication.
Beware if you want to share to non-Win95 clients via FPS for
NetWare; you have to turn on "Service Advertising Protocol"
(SAP). This is how NetWare servers become aware of each other,
and if you turn on SAP for a Win95 machine, it will appear in
SLISTs and SYSCON etc as NetWare servers. You can even get
connection info (Server version: "Windows 95 4.00.950, 250
user") from SYSCON. Problem is, not only would SAP advertising
by a lot of Win95 systems cause a lot of network traffic, it could
possibly kill any routing in an inter-network, and make DOS clients
try to log in (as in Preferred Server login) to Win95 servers, which
won't work. If you really want to screw up your network, share out
your hard drive with the share name SYS and make a directory
called LOGIN, and watch what happens. NOTE: Please don't do
this, unless you LIKE getting beaten up by your network
administrator.
A better solution is to install FPS for MS networks and put either
WFWG on the non-Win95 clients, or if they can't run Windows,
Workgroup Connection for DOS. Both of these can run alongside
Novell's NETX and VLM client software. OS/2 Warp Connect
can load Windows and NetWare clients simultaneously as well. To
save on memory on the DOS computers, consider using "Direct
Hosting over IPX", which will remove the need to use NetBEUI
and save 40 KB of memory or so. The absolute smartest way,
however, is to use a common space on the server.
Now printer sharing is another story...
----------------------------------------------------------------------
How do I make RPRINTER work?
Oh no... you can't run RPRINTER.EXE on a Win95 station
because you have to run it before Windows loads! Well, you could
use VLM and RPRINTER together but what's the point of real
mode network software on Win95? There is a better way. And no,
running it from WINSTART.BAT doesn't work.
Download and Install Microsoft Print Agent for NetWare. Add a
Service from Network control panel and hit "Have disk", then tell it
to look in ADMIN\NETTOOLS\PRTAGENT on the Win95
CD-ROM, or wherever you extracted that download. Note that
Print Agent will only work if you run Client for NetWare; it won't
run with VLM or Novell's Client32. BE WARNED: MSPSRV was
a last minute hack by Microsoft and doesn't have the
re-connect features, etc of Client for NetWare. In addition, it
requires a Bindery print server object. NetWare 4.x
Administrators: Use PCONSOLE to make Bindery mode print
server objects.
Just before you re-boot, change your IPX properties so you have
Maximum Sockets and Maximum Connections set to at least 70,
like RPRINTER/PSERVER's recommended setting of
SPX CONENCTIONS=60
I suggest 70 instead of 60 because FPS for NetWare and Remote
Registry require additional free sockets. And speaking of Sockets,
you can't use a third party TCP/IP dialer if you plan to use
MSPSRV, because it uses the Winsock interface over IPX.
Now, also just before you re-boot, run PCONSOLE and create a
new print server object. Add one printer to it named "Printer 0", set
for Remote Parallel, LPT1 (Or just Parallel on NW 4.x servers).
Attach it to a print queue on the NetWare server, if necessary,
detaching the queue from any other print server object it was
attached to. If you did detach it from an existing print server object,
you will have to re-start that PSERVER, which usually means
typing "unload pserver" and "load pserver xxxxxxxx" (whatever the
print server object's name was) from the NetWare console.
Now finally, re-boot the Win95 station and log in. Local printers on
this station will now have a "Print Server" tab in their properties
sheets. Be warned: This tab has bugs, so follow these six steps
precisely!
Select the Print Server tab and turn on "Enable print server for
NetWare". If you get any evil error message just ignore it.
Select the NetWare server with your new pserver object, from
the DROP DOWN LIST, even if it was already selected.
Select the pserver object you just created from the print server
drop down list.
Select how often you want this computer to check the queue for
print jobs. The 30 second default is fine.
Hit OK.
Hit Start Menu/Shut Down, close all programs and log in as
different user, and re-log in. Now all jobs in that NetWare
queue will find their way to this printer.
The reason you have to re-log in, is you will lose your drive
mappings as soon as you OK those settings! MSPSRV is riddled
with many dumb bugs, but Microsoft seems to swear by it. Check
out KB article Q134747 for all the gory details. Every time you
view this "Print Server" tab, it seems you will lose all your drive
mappings. Re-logging in will restore them.
You will also have to create a print server object for EVERY
Win95 computer sharing a printer this way, because each system
becomes a PSERVER look-alike, with all the requirements of a
stand alone PSERVER.EXE or PSERVER.NLM; the only
difference is that it multi-tasks. You will also have to remain logged
in to keep MSPSRV running, as logging out causes all programs to
close, including MSPSRV. It will re-start when you re-log in, or
cancel the log in. On machines with very active printers, you might
want to consider setting their Default Login to "Windows Logon"
with a blank password, so they automatically log in to NetWare on
power-up, and re-enabling Automatic NetWare Login for those
specific machines, if you disabled it via system policies.
Oh yeah, one more thing: Don't capture LPT1: to a network
queue if you're running MSPSRV to share a printer. This might
have worked in RPRINTER, but it doesn't work here. What will
happen is that MSPSRV will suck the job off the queue and send it
to the printer hooked up to LPT1, then that printer will send the job
to wherever LPT1 was captured to, instead of to the local printer!
I've seen this happen! Create a second printer in Win95 and have it
point to the queue, if you're afraid of cutting in front of other
people's print jobs.
So to recap: Create a print server object with a single printer, for
each Win95 computer sharing a printer through MSPSRV. Attach
a print queue to each of them. Make sure you aren't capturing
LPT1: to a network printer. Install MSPSRV on the Win95
computers sharing printers. Set Max Connections and Max
Sockets to at least 70 in IPX/SPX properties. Re-boot to activate.
Select the "Print Server" tab in the printer you want to share. Select
the file server from the drop-down list and the print server object
from its drop down list. Hit OK. Re-log in. And Pray. Heh heh...
...on a NetWare network using NDS?
I managed to get MSPSRV running on an NDS network just
recently. Originally, I thought switching the NetWare 4.1 version of
PCONSOLE to Bindery mode, and creating Bindery queues and
print server objects, would do the job. Apparently not. NDS clients
can't readily print to Bindery print queues.
So, after a lot of fiddling I realized that Novell's Quick Setup option
in PCONSOLE does the job almost perfectly! Quick Setup creates
a new NDS queue, NDS printer, and NDS print server object, and
makes a Bindery version of the queue and print server object,
granting printing rights to everyone in the NDS tree. A little extra
fine tuning and it works straight away with MSPSRV. Here's what I
did, with my example object names in (parenthesies):
Use PCONSOLE's Quick Setup option, in NDS mode, to
create an NDS queue (Q1), printer (P1), and print server object
(PS-INLINE). If you already have an NDS print server object,
be sure to specify a NEW print server object and not use any
existing ones.
Change the new printer object (P1) so it uses LPT1, IRQ 7,
"Change forms as needed", and have it service the NDS queue
(Q1).
Switch PCONSOLE to Bindery mode (Press F4), edit the
Bindery queue (Q1) so its settings match the NDS queue. Add
the Bindery print server object (PS-INLINE) to the list of print
servers for this queue.
Edit the Bindery print server object (PS-INLINE) so its settings
match the NDS print server object, and create a Bindery printer
within this object with the same name as the NDS printer object
(P1), and the same settings (printer number 0, LPT1, IRQ 7,
Change forms as needed). Have this Bindery printer service the
Bindery queue (Q1). The big catch is that Bindery
configurations aren't accessed by NDS objects, or vice
versa, as PCONSOLE's warning tells you. Heed that
warning.
With all that accomplished, the NDS objects and Bindery
equivelants will work together as if they were one set of objects.
Now, go to the Win95 station running MSPSRV and have it
service this print server object (PS-INLINE) as per the regular
instructions. If you're switching an existing queue to this new
print server, you'll need to stop and re-start PSERVER.NLM
on the server so it won't try to service that queue anymore.
All this fiddling may take a while, but it's the quickest way I could
get it working, so that both NDS and Bindery clients can print to
the printer shared via MSPSRV. And surprisingly, many of the bugs
Microsoft mentioned in KB article Q134747 above, don't show up
this time. Not bad at all! Yes, you have to do this for each Win95
station sharing a printer this way.
Best of all, MSPSRV takes far less memory (a mere 64 KB on the
workstation) than Novell's NPRINTER Open Beta.
----------------------------------------------------------------------
How do I share my hard drive or printer to Macintosh (tm)
users?
Miramar Systems will include an AFP and ASDP print service with
their MacLAN product, which they plan to release in June 1996. In
the meantime, they managed to hack in their Win 3.1 Personal
MacLAN into Win95.
----------------------------------------------------------------------
How do I share my hard drive or printer to other computers'
users? (SAMBA network clients)
MS Windows Network has a short name: SMB, or "Server
Message Blocks". SAMBA is a GNU public-license SMB client
for Unix machines, with versions available for The Amiga and
several other smaller systems. Visit one of many SAMBA FAQs,
or visit the newsgroup comp.protocols.smb, or if you want to
connect to Amigas, visit AMINET. If anyone of you fellow
Amigans have ported the SAMBA client (Not the SERVER) to
Amiga yet, please E-MAIL ME!
SAMBA clients exploit a nasty file sharing bug in Win95 and
WFWG; if the Win95 server shared out a directory, it will
inadvertently share the entire hard drive with the same restrictions!
Ack! Microsoft fixed this in Service Pack 1.
----------------------------------------------------------------------
How do I run DOS TCP/IP or packet-driver apps in DOS
sessions?
Originally I thought MS's TCP/IP would allow for DOS apps to
use 32-bit TCP/IP in the same way IPX apps would (such as
NetDOOM or Descent), but some TCP/IP apps provide their own
complete TCP/IP stack, and use the pure packet interface
(characterized by Packet Drivers that leave transport protocols to
the apps themselves).
There's an NDIS 3.0 packet driver you can install as a Win95
"protocol" at http://ndtl.harvard.edu/ndis3pkt which provides the
packet driver interface for any network card. The driver is
re-entrant so multiple DOS sessions can access it. The big catch is,
if you use MS's TCP/IP Protocol at the same time, AND you have
DOS packet apps that provide their own TCP/IP stack, you
cannot have MSTCP and the packet app use the same IP
address. You are effectively running two TCP/IP stacks (one for
Winsock apps and the one provided by the packet app) and these
can't have the same IP address.
However, multiple DOS sessions running TCP/IP packet apps can
use the same IP address. This packet driver can interpret TCP/IP
packets from DOS packet apps and multiplex them. This is a
special case which a packet driver would not normally handle.
So with this aside, to install the virtual packet driver for Win95:
Download the ndis3pkt "protocol" from the above address
Install a net card driver for Win95
Install the packet driver as a Protocol
Check the Bindings tab for each net card you have, and make
sure you enable the Virtual Packet Driver only for the cards you
want to use it for (turn it OFF for the Dial-up Adapter).
Re-start the computer. Use your packet apps as normally in
DOS sessions.
----------------------------------------------------------------------
How do I print to HP JetDirect (tm) printers on the network?
Win95 includes a JetDirect service, which allows you to control and
attach to printers with JetDirect cards installed. HP JetAdmin
depends on IPX protocol, so install that as well.
Once you install the JetAdmin service, you can print to the JetDirect
printers like you could to any network print queue, but you cannot
map a DOS LPT port to one. Read below, to learn how to create
new DOS ports instead.
----------------------------------------------------------------------
JetDirect Port Aliasing, or How do I print from DOS
programs to JetDirect Printers?
Originally I thought that MS's DLC protocol would allow for
JetDirect access, as it did in Windows NT. Nope. I had the chance
to attempt it myself and had to struggle with HP's Aliasing Port
Monitor to make it work.
Once you set up your JetDirect printer objects, install this dummy
printer driver. This will install the capability to add "Alias Monitor"
ports from printer properties. If you actually try to install the dummy
printer to the end though, it will fail. The port capability will install
correctly, however.
Then, install a new Windows printer, identical to your existing
JetDirect printer, except after you finish, change its port. From the
new printer's properties, in its Details tab, select "Add Port".
Among the Local Port choices, select "Alias Monitor". Type in a
valid DOS port name (such as LPT3:), a descriptor for it, and the
name of the existing JetDirect printer object (like "HP DeskJet
1200C (MS)", exactly as it appears in the Printers window). Once
this is done, whenever you print to this port, it will print to the
Windows printer it points to. You can change this port's target or
other properties from "Port Settings".
One advantage of this, is you can make your computer the print
spooler for it, and use a shorter share name (the sharename
\\HP_Network_Printers won't work with Win 3.1 apps or Win 3.1
printer drivers). Another advantage is you don't have to install
JetAdmin on each and every computer, if you do re-share it.
NOTE: This is only the beginning of HP's apathy towards
Win95. Notice how they supply ONE driver set for Win 3.1 and
for Win95? Notice how "You must use the SETUP program!"
when you try to add the driver with Add Printer? Just what the
hell is HP trying to do here? Of course, HP's newest DeskJet
1600 drivers don't work with JetDirect printers this way 'coz
they're written for Win 3.1 and don't recognize this long
\\HP_Network_Printers share name. I suggest getting a
Lexmark PS4079 if you want good colour printing AND Win95
performance.
----------------------------------------------------------------------
I heard that Win95 has System policies. How do I set it up?
System Policies let you enforce a bunch of settings for Win95
computers on a network. This is real handy to disable long filename
support for NetWare, or disable password caching, for example,
without going to each and every computer on the network and
editing SYSTEM.INI or the Registry.
Copy the contents of ADMIN\APPTOOLS\POLEDIT from the
CD-ROM, to a convenient directory that only you (the
Administrator) have access to. The first time you run POLEDIT, it
will ask you for a policy template. Choose ADMIN.ADM. There
are other policy templates for other networks (including NDS), but
ADMIN covers most of the stuff for now.
Have a nice look at all the settings you can enforce on, enforce off,
or not enforce. Notice you have three choices; an "On", "Off", and
"Don't Care"; the "Don't Care" state means that the computer will
use the setting it already has. "Default User" refers to people, and
you can add unique policies for unique users if you have a central
security provider (like an NT domain controller or NetWare server)
by adding users to this policy file. "Default Computer" refers to
computers, and you can add computers here as well, named by the
"Identification" tab back in Network Control Panel.
Definitely set these policies up at a bare minimum:
Network path for Windows 95 files
Remote Update: Automatic (Use Default Path). Remote Update
refers to updating local settings from the policy file, and Default
Path refers to the location of the policy file itself. The default
path depends on the kind of network client installed (Microsoft
Networks, NetWare, LANtastic, whatever) and this
"Automatic" option only works if you have a Win95 client for a
central server of some kind. You can do non-central policies
too, but I'll cover that later.
Save this policy file with the name CONFIG.POL and copy it to
the path your client expects to find it.
POLEDIT also works directly on a local Registry, which is really
convenient if you don't trust yourself with REGEDIT.
...on a NetWare network?
Prepare the CONFIG.POL file and copy it to your Preferred
Server's SYS:PUBLIC directory. Yes I know, I goofed! Big time!
Auuugh!!!! I finally verified this and sure enough, it reads from
SYS:PUBLIC. Make sure that everyone has read and file scan
rights to this directory, including GUEST if you have such a user.
Additional useful policies for NetWare networks include:
Disable/Enable Long Filename support (You have three choices
here)
Disable Password Caching
Disable File and Print Sharing Controls (Remote Administration
still works)
Disable Automatic NetWare Login
Preferred Server
Disable SAP Advertising
...on a NetWare network using NDS?
Microsoft's Services for NDS has some pretty cool extensions to
this policy logic; you can enforce policies dependent on whatever
level on the NDS tree you log in to (whatever your current context
is), including specific Organizational Units, or the entire
Organization. All this stuff only works if you installed MS's Services
for NDS in addition to the Client for NetWare. Otherwise, for
Bindery logins, it still reads CONFIG.POL from SYS:PUBLIC.
To add NDS policies, change your template to the MAPLE.ADM
template included with Services for NDS. Then load your
previously-made CONFIG.POL file and make the appropriate
NDS policy changes. All other policy settings made from
ADMIN.ADM will stay un-changed.
Bring up your Organization and Organizational Unit icons up in
Network Neighborhood. If you have Admin privileges in these
units, bring up properties for them. You'll see an "NDS
Administration Settings" tab. Here, enable system policies and
specify the volume name (including context, such as
IN-LINE_SYS.INLINE) and file name (including path, such as
PUBLIC\IN-LINE.POL) for the policy file. The name need not be
CONFIG.POL; it can be INLINE.POL or whatever, but you
should make sure that the policy file is in a public place, such as the
good old PUBLIC directory. Do this for each Organizational Unit
and for the whole Organization as you see fit.
NOTE: Policies don't flow down the NDS tree like other
properties do. You will have to re-apply the policy setting to
each Organizational Unit within your master Organization, or
you may use different policies for each Organizational Unit.
In addition, the NDS client will read policies differently,
depending on whether the user performs an NDS login or a
Bindery login. For Bindery logins it reads CONFIG.POL from
SYS:PUBLIC, and for NDS logins it reads it depending on the
system policy settings for that NDS branch.
Two very useful NDS policies (Include these in the Organization's
properties along with other basic policies):
Load NetWare DLLs at Startup (To make dumb NDS apps
work)
Allow only NDS logins (To prevent User Profile and System
Policy screwups)
...on a Windows NT network?
Create the CONFIG.POL and copy it to the NETLOGON share
of your primary domain controller. You can spread the policy file to
all your backup domain controllers as well, in which case, the
"Load Balancing" option can save some server overhead on slow
WAN links.
Useful policies for NT networks:
Log on to Windows NT (Specify domain name here too)
Workgroup (Use same name as the domain to ease browsing
troubles)
Disable Password Caching
Enable Load Balancing (If you use multiple domain controllers
per domain)
...on another network with a 32-bit client?
Other Win95 clients will have their own policy templates and their
own unique location for the policy file. Check with the vendor for
the details. If there's no default path, you can enforce the "Manual
Update" policy and specify a UNC path to the policy file (like
\\SRV\POLICIES\CONFIG.POL), but you will need to run
POLEDIT on each station to set this in each Registry.
...on another network with a DOS client?
You will have to set the "Manual Update" policy and set a DOS
Drive:\DIR\CONFIG.POL path on each station in each Registry.
You will also need to map this network drive before then end of
AUTOEXEC.BAT as well.
...on a peer to peer Win95 network?
If you keep one Win95 station on all the time (Usually the machine
with the printer attached) you can put a policy file there. You will
still have to manually change the Remote Update path in each
station, but this time it can be a UNC path.
----------------------------------------------------------------------
I heard that Win95 has user profiles. How do I set it up?
User Profiles are a really, really, cool feature of Win95. Not only
can you set a personalized desktop for each user and have personal
Start Menus, but you can have personalized settings for MS
Exchange, Word for 95, or pretty much any program that stores
user preferences in HKEY_CURRENT_USER in the Registry!
Profiles will also follow a user around in a centralized network,
copying their program settings to each station as required.
To turn on User Profiles, run the Passwords control panel.
Regardless of whether you installed Networking or not, you turn on
"Users may select their own preferences" on the User Profiles tab.
Custom Desktops and Start Menus are actually one of these user
preferences. You can enable or enforce User Profiles, but it's up to
the users if they want their shortcuts to be unique to them.
Regardless of user profile preferences, Win95 creates a Profiles
folder, and a sub-folder for each user to store a personal copy of
USER.DAT, the user portion of The Registry. If the user chooses
to have custom Desktops and Start Menus, it stores them in that
folder as well. Deleting shortcuts from Win95's default Dekstop and
Start Menu folders will not affect a user's personal Desktop or Start
Menu.
Profiles work best when you have all Win32 apps, and if you keep
copies of the apps in the local hard drives, that you install the apps
in the same place on each computer! The "C:\Program Files"
Directory is a good place for apps in a User Profile environment.
Keep the Windows directory the same name on all your
workstations too.
SOFTWARE DEVELOPERS: Be VERY VERY CAREFUL
where you store your program settings! Hardware settings (like
local cache directories or modem preferences) belong in
HKEY_LOCAL_MACHINE, mobile and user settings (like
bookmarks or spell check preferences) belong in
HKEY_CURRENT_USER or in HKEY_USERS\.Default... Test
your software in a User Profile environment! This includes you,
Netscape Communications!
...on a stand-alone workstation?
The Password Control Panel is always there, whether you have a
network client loaded or not. In here, select the User Profiles tab,
and select "Users can customize their settings". Specific users can
choose to keep a custom Desktop and Start Menu included in their
profile.
When you aren't on a network and you have User Profiles turned
on, you need to have a password for each user, otherwise it will
happily automatically use the last password-less user's profile.
Selecting "Shut Down" and "Close all programs and log on as
different user" will let you enter your own name and password.
...on a NetWare network so it'll follow the user around?
Win95's Client for NetWare stores a user profile in their MAIL
directory, so be sure you give each user one. SYSCON
automatically creates a MAIL directory for each new user. The
Win95 station copies their profile to the MAIL directory on log out,
and reads it in on log in.
You should enforce "Enable User Profiles" as a system policy, to
keep multiple profiles straightened out.
How do I make roving Desktop and Start Menus work on
NetWare?
The Desktop directory and Start Menu directory (which as you
would recall, are just a bunch of .LNK and .PIF files) get copied to
the user's MAIL directory too, if they turned on "Include Desktop"
and "Include Start Menu" in Passwords/User Profiles. Because
Shortcuts have long filenames, you need to enable LFN support on
the SYS: volume. This will only work on patched NW 3.11, NW
3.12, or NW 4.x servers with the OS/2 name space installed.
Enforce LFN support via system policies.
You should also ensure you have enough space on your SYS:
volume for the shortcuts! Microsoft recommended setting aside 150
KB per user, but my own custom profile eats 250 KB easily!
...on a NetWare network using NDS?
Services for NDS stores a user profile in the user's HOME
directory instead of the MAIL directory, so make sure you define a
home directory for each user, but the same rules regarding roving
Desktop and Start Menu (LFN support, space requirements)
apply.
NDS clients can perform Bindery and NDS logins, so it is possible
to have two sets of profiles for each user! You should enforce NDS
logins only, via system policies, to prevent this mix up.
...on a Windows NT network so it'll follow the user
around?
NT clients keep their profiles in their HOME directory, so make
sure you define a home directory for each user, in User Manager.
NT servers 3.5 or later have long filename support built in, even for
FAT file systems, so you have no worries regarding roving
desktops and Start Menus... just the space requirements.
Also, enforce "Enable User Profiles" through system policies, to
keep multiple profiles straightened out.
...on another network?
Roving User Profiles require a central storage space, and are
specific to what network client you run. So the location of user
profiles on that network depend on that client. This won't work with
Client for MS networks without a Windows NT domain to log in to
(So it doesn't work on just a bunch of Win95 machines together),
but you can define a custom Desktop or Start Menu for each user,
with POLEDIT.
In Default User (Or whoever user) Shell settings, you can define a
path for custom folders. The custom folders include Desktop, Start
Menu, Programs, NetHood, and "Hide Start Menu Subfolders". So
for each user (By selecting Edit/Add User) you can insert a custom
path for these items. If you do this in one master CONFIG.POL file
stored in one location, and you have "Remote Update: Manual
Path" turned on, you can enforce a different Desktop and Start
Menu for each user without a central server. Just make sure the
path exists when Win95 starts (Either by using a UNC path, or by
logging in before running Win95, in the case of real mode clients).
If you also enforce user profiles through the central policy file as
well, Win95 will store USER.DAT for each user on the machine,
but it will not follow the user around. If you want the benefit of full
roving user profiles, get a central server with Win95 client support,
and check with the network OS vendor about user profile support,
if it isn't an NT or NetWare server.
Why user profiles is a really cool and useful feature!
One time I read a question on how to make Netscape 2.0 work
with more than one user's E-MAIL settings, so it would work with
more than one provider. The answer was simply: Turn on User
Profiles in the Passwords Control Panel. With that, Netscape had
different settings for each user, and what was better, each user had
their own dial-up networking preferences stored under their own
profile!
User Profiles is cool because it offers a central control for
personalized settings, regardless of whose program you run! The
software developer doesn't have to account for multiple users for a
given program; they need only store personal settings in the
USER.DAT portion of The Registry, and let the OS take care of
the rest. I know this works with these programs:
MS Office 95 suite
Corel Graphics suite 6.0
MS Exchange
Netscape 1.2N up to 2.0 (You will need to fix the cache path
for each user though)
NCSA Mosaic
Other programs Designed for Windows 95 had better work with
this.
----------------------------------------------------------------------
I heard that Win95 has remote administration. How do I set it
up?
The Passwords Control Panel has a "Remote Administration" tab
that works only if you have networking installed. If you use a central
server, you can assign administrative privilege to a SUPERVISOR
or Domain Admin.
First, install File & Print Sharing for either MS networks (for a pure
Win95 or NT domain network) or NetWare (For NetWare
networks). If you use FPS for NetWare, keep SAP advertising
OFF. In addition, install the Remote Registry service from Network
Control Panel, as a Service (in
ADMIN\NETTOOLS\REMOTREG on the CD-ROM) on the
remote machines. You can do this (and even enforce this) when you
install Win95 as well.
Now, if the workstations use User level security (highly advisable
on NT Domains and NetWare networks), Setup will automatically
enable remote administration for ADMIN and SUPERVISOR
(NetWare) or DOMAIN ADMINS (NT Domain). If the stations
use passwords instead of user lists (Share level security), or you
don't have a central server, you will need to manually enable
Remote Administration and supply a password to each station.
Remote Administration settings will differ with each type of network
client installed.
Once done, you (the administrator) can control computers via
Network Neighborhood. Right-click on any Win95 station and
select "Properties". You will see a "Tools" tab that lets you edit the
Registry, view network activity, or even browse the hard drives, on
the remote computer. REGEDIT and POLEDIT also works on
these stations.
NOTE: The Remote Admin tools only work if someone's logged
in to the machine you're trying to administer. Most likely this
will be the machine's user asking you to have a look, but on a
rare occasion you might need to administer a machine not
logged in to. You're out of luck unless someone can log in to
the computer you're trying to administer.
Of the tools listed, Remote Registry service is the biggest
program (250 KB). To free up memory so you don't slow down
the machines, check out How to Prevent Random Hard Drive
Access, which also frees lots of memory for these services.
...on a NetWare network?
Install FPS for NetWare or FPS for MS networks, install Remote
Registry service, and enable User level security (No choice really
for FPS for NetWare). Keep SAP advertising OFF. Edit the IPX
Protocol properties so you have at least Maximum Sockets and
Maximum Connections set to 32. Re-boot. Then, from any other
Win95 station, log in as SUPERVISOR or ADMIN and get
properties on the Win95 station from Network Neighborhood. The
remote stations automatically assign remote admin privileges to
SUPERVISOR and ADMIN.
Of the available remote admin tools, Net Watcher will also work
for viewing activity on the NetWare server, as well as the Win95
machines. Net Watcher grabs the same information made available
via SYSCON.
There is one bug in Remote Administration, that makes the remote
system keep sharing its hard drive, even when you end the Remote
Admin session. Install Service Pack 1 on the remote station to
correct this. This bug does not happen if you use FPS for MS
networks instead of FPS for NetWare, but then you need to install
Client for MS networks on the station you're administering from.
There's no need to install two clients on the stations, really, so use
FPS for NetWare, disable File & Print sharing controls (but not
File Sharing itself) and SAP advertising via system policies, and
install Service Pack 1.
...on a NetWare network using NDS?
NOTE: Remote Administration (and many of Win95's NetWare
add-ons) depend on Bindery services running on your preferred
server. To make Remote Registry services work in an NDS
network, you will need a separate server with a Bindery (which
isn't part of the NDS tree you're logged in to) running as a
security provider. Ack. I know this sucks; the details are in KB
article Q143398. As far as I know, Remote Registry Service is
the ONLY NetWare-related service that won't work with a
security provider which is part of the NDS tree (running
Bindery emulation). Net Watcher and Administer both work
regeardless.
With that aside, I did manage to get Remote Registry running on an
NDS network about the same time I got MSPSRV working.
Remember where MS said you needed to have a separate Bindery
server to provide security? Well... Win95 with FPS for NetWare
acts as a Bindery server, so why not use another Win95 station as a
security provider? It does work! And I was able to log in to the
NDS tree and run Remote Registry on other stations with users
logged into the NDS tree, and FPS for NetWare worked normally
too.
Remember: You only need to do this if you want to use Remote
Registry service on an NDS network, and you're using
Microsoft's Services for NDS on the machine you're
administering from. Net Watcher and Administer both work
without this nonsense, and the standard Client for NetWare
works with Remote Registry straight away.
So here's what I did:
Set aside one Win95 computer (a '386 with 4 MB of memory
will do) and install Client for NetWare and FPS for NetWare.
No other clients or services. Have its User Level Security
settings point to your NDS server. Check that server's Bindery
context so it at least has your Administrators' usernames
available. On that one machine ONLY, turn on SAP advertising
and turn off Workgroup advertising. You might want to get the
latest patches for NetWare 4.1, to prevent SAP traffic from
killing any routing in your network. This machine won't work
with Remote Registry, so don't bother installing it.
On all the other Win95 machines running NDS, change their
User Level Security settings to point to this one Win95 machine.
They can still have their original Preferred Server and Preferred
Tree defaults the way they were. See that all these machines
have Remote Registry service and FPS for NetWare, and they
have SAP turned OFF.
After rebooting the other Win95 machines, change their Remote
Administration settings so they include users from the emulated
Bindery on the security-providing Win95 machine (that '386).
You can even specify this machine, if you wish, in
MSBATCH.INF during a Win95 installation.
At this point, all Win95 stations except one are using that one
Win95 machine for a security provider. That one machine is
using the NetWare 4.1 server as a security provider. Remote
Registry services will work as they did for the original Client for
NetWare. If it prompts you for a password, use your login name
and password.
(Optional) You can even enforce this via System Policies; you
can add the single machine to the CONFIG.POL file and have it
use the NetWare 4.1 server for security and turn on SAP. The
Default Computer settings will use that one machine as provider,
and turn OFF SAP. This way you don't have to go to each
machine to change their security provider settings.
...on a Windows NT network?
Install FPS for MS networks, install Remote Registry service, and
enable User level security. Remote Admin privileges are
automatically given to anyone in the Domain Admins group on the
domain controller. Re-boot. Then, go to another Win95 station, log
in as Administrator (or anyone else in Domain Admins) and get
properties on the remote station from Network Neighborhood.
WARNING: Apparently, this service will allow you to remotely
edit an NT Server's Registry! I was able to get in to several (but
not all) Registry keys on my own NT server by logging in as a
member of Domain Admins. I'd hate to think what could
happen to my poor server if someone ran REGEDIT on this
network with malicious intent!
WARNING: Remember the NetWare C$ bug? It's back, this
time in FPS for Microsoft networks! Now if you perform a
Remote Admin session on a Win95 station and view its hard
drives, the Admin shares (\\machine\c$) remain active,
available for read-only viewing when a user types \\machine\c$
from Start Menu/Run. This bug may have always been around,
but I suspect it emerged with Service Pack 1.
...on a Peer Win95 network?
NOTE: According to the Remote Registry readme files, Remote
Registry service only works if you use User Level Security from
a central server. This makes absolutely NO SENSE, with the
possible exception that Microsoft wanted to prevent malicious
editing of other people's Registries. How thoughtful of them,
huh? No matter; the other Remote Admin tools (Net Watcher
and Administer) work on Share Level security.
----------------------------------------------------------------------
I heard that Win95 has user level access. How do I set it up?
User Level access spares us the potential of lost passwords and
multiple, security-killing, cached passwords, because the
passwords remain on the central security provider. You need only
log in once and type your password once, and you have access to
any resources shared on the network that have you on their access
list.
Enable User Level security from Network Control Panel, in Access
Control. Pick a security provider (the name of an NT domain,
NetWare server, or other central server if your client/service
software allows for it). The next time you re-boot, all your share
requesters and password requesters will have user list requesters in
their place. You could also enforce user level security via system
policies.
If the server is a NetWare 4.x server, you will need to set a Bindery
context on it. This will allow all NDS clients access to any Win95
stations sharing resources via FPS for NetWare.
Unusual combinations to avoid:
FPS for MS networks, using a NetWare server as security
provider (WFWG stations can't get access then!)
FPS for NetWare, using an NT server as a security provider
(Quite impossible)
FPS for NetWare, using Share level security (It won't let you)
----------------------------------------------------------------------
Win95 lets me cancel the log in and still use Windows. How
do I fix it?
You can demand log in for Win95 access, through system policies,
if you use a central security provider with a Win95 client. This way,
a failed log in or a canceled log in will give "Unable to log you in"
errors. Be warned: CTRL-ESC at a login prompt will bring up the
task manager, so you will also want to remove TASKMAN.EXE
from that computer.
Win95 is not as secure as Windows NT, but some other security
measures will prove useful enough to keep the bad guys out. These
include:
Remove the floppy drive from the computer once you install
Win95
Disable REGEDIT.EXE via system policies, and rely on Remote
Administration
Remove TASKMAN.EXE from the system; the task bar
replaces it anyways
If you insist on keeping the floppy drive in the computer, force it
(through BIOS setup) to always boot from Drive C.
Password-protect your BIOS setup too.
Edit MSDOS.SYS to prevent Safe Mode booting, force the
system to always boot into Win95 on power-up, and to set the
boot delay to zero.
Hide components of the Control Panel, such as Network, via
system policies. You can hide quite a few Desktop components
via system policies too. Check them out.
----------------------------------------------------------------------
Win95 has this Samba bug. How do I fix it?
Install Service Pack 1. Or just disable the binding to File & Print
Sharing for MS Networks to TCP/IP. Bring up TCP/IP properties
for each net card, hit "Bindings", and turn off the binding to FPS for
MS networks.
Microsoft claims this bug happens when Samba clients issue "Illegal
network commands" to the computer acting as a server. Fact is, this
bug was in WFWG originally, and I suspect it's even in NT Server!
Rich Graves has all the gory details. Microsoft seems to have many
troubles with Samba clients and servers; there was even a Client for
MS networks update in Service Pack 1 that fixed troubles with
Win95 accessing a Samba server.
----------------------------------------------------------------------
Win95 has this NetWare C$ bug I heard about. How do I fix
it?
This bug creeps up when you perform Remote Administration on a
Win95 computer that uses File & Print Sharing for NetWare. The
Admin share (\\machine\C$) remains active, and users can connect
to it by typing that UNC path. Install Service Pack 1, or do without
remote administration.
This was another bug that Microsoft danced around. Again, Rich
has the details.
The C$ bug is apparently in FPS for MS networks too! The same
conditions apply; after a Remote Admin session, the admin shares
remain active!
----------------------------------------------------------------------
Win95 has this password caching bug. How do I fix it?
Install Service Pack 1 or disable password caching via system
policies.
----------------------------------------------------------------------
How do I disable password caching?
Password caching only happens if you have a Win95 network client
installed, OR you have User Profiles enabled on a stand alone
computer.
The clients for NetWare and NT have separate caching restrictions
(such as "Prevent caching of log on password") you can use, or you
can disable password caching entirely, in the Network section of
POLEDIT.
----------------------------------------------------------------------
How do I enable user level access to eliminate the need to
cache passwords?
Read all about it in User level security. You will need a central
security provider (like an NT domain or NetWare server) for this
though.
----------------------------------------------------------------------
Visiting Rich Graves' Win95NetBugs site for details
He's at
http://www-leland.stanford.edu/~llurch/win95netbugs/faq.html and
while he's very anti-Microsoft, he does present the facts.
----------------------------------------------------------------------
Cool software for Win95 dial up networking, and other
Winsock and network apps
Visit http://www.windows95.com for a lot of 32-bit apps, utilities,
hacks, whatever, that will make your networking life easier.
Also visit http://www.cwsapps.com for the Consummate Winsock
Apps list; the original.
----------------------------------------------------------------------
[Back to Table of Contents]
--
============================================================// //========
= "I am Gordon of Winterpeg. Windows WAS futile." // // =
= Find out why: http://www.intouch.bc.ca/win95 // // =
= Personal E-MAIL: gordonf@vcn.bc.ca \\ \\// // =
= Home Phone: +1-604-526-8724 \\ XX // =
= \X/\X/ =
= "I am Hitler of BorgSoft. I am the middle inital of William H. Gates. =
= Your work will be Microsofted. Resistance is futile. Heil Windows. =
=========================================================================
Yeah I use an Amiga at home. If you don't like my computer, dial
1-800-DIE-BILL and tell someone who cares.
----------------------------------------------------------------------
Path: news1.ucsd.edu!ihnp4.ucsd.edu!swrinde!cs.utexas.edu!uwm.edu!news.cse.psu.edu!news.ecn.bgu.edu!vixen.cso.uiuc.edu!newsfeed.internetmci.com!info.ucla.edu!news.bc.net!news.mindlink.net!van-bc!unixg.ubc.ca!freenet.vancouver.bc.ca!gordonf
From: gordonf@vcn.bc.ca (Gordon Fecyk)
Newsgroups: comp.os.ms-windows.win95.misc,comp.os.ms-windows.setup.win95,comp.os.ms-windows.networking.win95,comp.os.ms-windows.apps.compatibility.win95,comp.answers,news.answers
Subject: Win95 FAQs and Answers Part 8 of 14: Dial-up Networking
Followup-To: comp.os.ms-windows.win95.misc,comp.os.ms-windows.setup.win95,comp.os.ms-windows.networking.win95,comp.os.ms-windows.apps.compatibility.win95
Date: 30 Jun 1996 16:32:27 GMT
Organization: Vancouver Regional FreeNet
Lines: 596
Approved: news-answers-request@MIT.EDU
Message-ID: <4r6a6r$80p@milo.vcn.bc.ca>
NNTP-Posting-Host: opus.vcn.bc.ca
Summary: These postings list many questions asked in said newsgroups,
and answers them as best as I can. I make references to other
Web sites and FAQs when appropriate. Visit the WWW home of
this FAQ (http://www.intouch.bc.ca/win95) for the appropriate
links. This section is the 8th: Dial-up networking & Internet
This section should include TAPI questions & answers in
the next update.
X-Newsreader: TIN [version 1.2 PL2]
Xref: news1.ucsd.edu comp.os.ms-windows.win95.misc:111605 comp.os.ms-windows.setup.win95:10982 comp.os.ms-windows.networking.win95:7516 comp.os.ms-windows.apps.compatibility.win95:3581 comp.answers:15520 news.answers:61921
Archive-name: windows/win95/faq/part08
Last-Modified: 1996/07/01
Posting-Frequency: Every two months
URL: http://www.intouch.bc.ca/win95/faq8.htm
8) How do I connect to The
Internet? And other dial-up
networking questions
TCP/IP under Windows 95 in a nutshell
How do I set up TCP/IP through a network card?
How do I set up TCP/IP through a modem? (Follow exactly
to the letter, or else!)
How come I have to dis-connect from my NetWare server
when just dialing to The Internet?
How do I run my Winsock program?
Using Trumpet (tm) and other TCP/IP stacks (Just don't!)
How do I get dial up networking to work with other stuff
besides The Internet?
How do I get auto-dial to work?
How do I set up auto-disconnect?
How do I DISABLE auto-disconnect?
My provider only has SLIP. Can I use that? (yes.)
Dial-up networking won't save my password! How do I fix it?
My computer hangs in the task "RNAAPP". How can I fix it?
(NEW)
How can I track my time and costs on my connections?
How do I use dial-up networking on a null modem cable?
How do I write a dial-up script?
How do I set up a dial-up server?
Top five reasons to use Win95 as a dial-up server
Top ten Dial-up Server mis-conceptions
Top ten Internet/Dial-up mistakes
----------------------------------------------------------------------
TCP/IP under Windows 95 (Next five section fer Experten
only; is nicht fer gerverken by das dumbkoffen)
So you don't trust the Internet Setup Wizard, eh? OK, here's
TCP/IP in a nutshell.
Transmission Control Protocol/Internet Protocol (TCP/IP) comes
with Win95 as an NDIS 3.1 protocol. So, aside from connecting to
The Internet, you can use any other Win95 clients or services over
TCP/IP as well, or at least, those that don't depend on a particular
protocol. Now that's pretty cool, but we want to connect to The
Internet, right?
Win95's network setup also copies the Windows Sockets libraries,
based on Berkeley University's UNIX Sockets interface. Winsock
works over any protocol really, which is why Win95 Setup must
replace any other WINSOCK.DLL with its own, but for The
Internet we're primarily concerned with Winsock over TCP/IP. All
Windows Internet apps use the Winsock interface, in one form or
another.
----------------------------------------------------------------------
How do I set up TCP/IP through a network card?
If you don't already have a network card installed, install it and load
its Win95 driver. Then add TCP/IP protocol. TCP/IP has six
property sheets, some of which affect all of TCP/IP, and others
only affect the net card they're bound to:
IP address: Either have it select an IP address automatically, or
give it an IP address and subnet mask directly. To perform
automatic IP selection you need a BOOTP server or DHCP
server operating within your local network. This is unique for
each card using TCP/IP. NOTE: While I haven't seen a
BOOTP server assign addresses to Win95 clients yet, it is
theoretically possible. BOOTP only assigns IP addresses and
Subnet masks; you need a DHCP server to auto-configure
other Win95 TCP/IP settings.
WINS configuration: To use Client for MS networks or any
other NetBIOS apps over TCP/IP, you should have a Windows
Internet Name Service (WINS) server accessible to you. Feed
its IP address here, or if you have a DHCP server you can let it
fetch WINS information from there. For regular Internet
connections, select "Disable WINS Resolution". These settings
affect all net cards using TCP/IP.
Gateway: To get to the rest of the Net, feed your router's IP
address here. I don't believe Win95 will grab Gateway info from
a DHCP server so ask your administrator for this value. This is
unique for each card using TCP/IP.
DNS Config: This tab not only enables Domain Name Service
for Winsock apps, it also enables NetBIOS name resolution
over DNS. Select "Enable DNS" and feed it up to three
addresses of DNS servers. If you have a local DNS and an
Internet provider's DNS, you can enter both of them here. Yes,
it does work. Also, if you wish, enter the domains you wish to
enable NetBIOS naming for. For example, if you want to look
for a server named \\JOE in the domain my-domain.com, insert
my-domain.com into the domain search order list. For regular
Internet access you can leave the search order fields blank. This
tab affects all net cards using TCP/IP. NOTE: Supposedly, if
you provide DNS info on a DHCP server and you leave
DNS disabled here, Win95 will grab DNS info from the
DHCP server.
Advanced: This is a useless tab, probably inserted to provide
controls like TTL and hop count limits and such, but Microsoft
chose to omit it. Too bad, because enough people complain
about not being able to control them. Here are the settings I'm
talking about.
Bindings: Very important tab if you don't want someone on The
Internet poking in your computer. If you have File & Print
Sharing for MS networks installed, turn off the checkmark to
that service in this Bindings tab. This way, FPS won't work over
TCP/IP, and no one on The Internet can get to your computer.
This is unique for each net card using TCP/IP.
----------------------------------------------------------------------
How do I set up TCP/IP through a modem? (Follow exactly to
the letter, or else!)
Make sure you installed Dial-up Networking from Add/Remove
Programs/Windows Setup. Then make sure you have the Dial-up
Adapter installed in your Network setup. Then add TCP/IP.
Follow the guidelines for net cards, except use these settings:
IP address: Obtain IP address automatically
WINS Resolution: Disable WINS resolution
Gateway: leave blank unless your provider gave you a
Gateway address, if so put it here
DNS: Disable DNS Resolution (We insert DNS addresses
later!)
Advanced: Nothing, but turn off "Use this as default protocol".
Bindings: Definitely turn off the FPS for MS networks binding if
you have it.
Then re-boot, double-click on your Dial-up Networking folder and
make a new connection. The modem configuration may be
whatever you like, but your Server type must have these settings:
Server type: PPP (Win95, Win NT 3.5, Internet) (You can do
SLIP too, contrary to popular belief)
Log on to network: OFF (This prevents disconnects if you're
logged into a NetWare network)
Enable Software Compression: OFF (Unless you're dialing
into an NT dial up server, in which case this will really speed
things up!)
Require Encrypted password: OFF (Again, only useful if
you're dialing into an NT dial up server)
Protocols supported: Only have TCP/IP turned on and the
others OFF!
Then in TCP/IP Settings:
Server assigned IP address: turned on unless your provider
handed you one, in which case feed it here. It will automatically
use Subnet mask 255.255.255.0.
Specify Name server addresses: Here's where you feed the
DNS server addresses! Leave the WINS server addresses at
0.0.0.0 to disable WINS over the dial-up connection.
IP header compression: Turn ON unless your provider tells
you not to.
Use Default Gateway: Turn ON unless your provider gave
you a specific gateway address, and you put in your TCP/IP
properties back in Network Setup.
Finally hit OK.
The above settings work with 99% of all UNIX and NT dial up
servers known to me. By hard-coding the DNS addresses here and
specifying only TCP/IP, you prevent Win95 from sending unusual
PPP requests to the dial up server, some of which can CRASH
some UNIX dial-up servers. The Internet Setup Wizard
automatically prepares a dial-up connection with all the proper
switches set, except it turns on "Enable Software Compression",
which you can turn off if you have troubles connecting. The next
thing to turn off would be "Enable IP header compression" if you
still have troubles connecting.
If your provider requires a special login procedure, bring up
properties for the dial up connection again, select "Configure...",
and in the Options tab, turn on "Bring up terminal window after
dialing". This will let you manually login to the dial up server. When
you connect, log in manually, and activate PPP, however you're
supposed to do it, then hit "Continue" or press F7, which continues
the PPP negotiation. Learn your provider's login procedure, then
read on to learn how to write an automated dial up script.
----------------------------------------------------------------------
How come I have to dis-connect from my NetWare server
when just dialing to The Internet?
Win95's dial up networking uses a generic (OK, so Shiva wrote it,
whatever) Point-to-Point Protocol (PPP) that works with pretty
much any network transport. In particular, Microsoft directly
supports NetBEUI, IPX, and TCP/IP over PPP.
The one complication that rises over this, is when you try to dial out
to The Internet while logged into a NetWare network, it will warn
you that it must disconnect from the NetWare server, since the
Client for NetWare can only log in to one NetWare server at a
time. To avoid this, have "Log on to network" turned off in your dial
up connection's Server Type.
Rich Graves claims this is because of Microsoft's PPP "Extensions",
but I think it's just because Client for NetWare can't log in to more
than one server. LOGIN and ATTACH are two different actions;
you can ATTACH to a NetWare server remotely after you logged
in to a LAN NetWare server. Client for MS networks does not
have this limitation.
----------------------------------------------------------------------
How do I run my Winsock program?
Make your connection, however you do it, then run your apps.
Simple.
Win95's WINSOCK.DLL and WSOCK32.DLL include a
"standard" Windows Sockets API that works with ANY properly
written Winsock program. All of the Public Domain, Freeware,
Shareware, and a surprisingly large number of Commercial apps,
run with these libraries.
If you installed Internet Explorer, you'll find that your dial-up
connection requester will pop up when you run a Winsock app, if
you aren't already connected. This is pretty nifty, and you can
control this auto-dialer from the new Internet control panel that
shows up. Of course, Auto-dial is pretty useless if you use TCP/IP
over a network card.
Be VERY VERY CAREFUL if you install any one-shot packages
which include their own dialers. These will often replace the OS
standard WINSOCK.DLL with their own to accommodate their
dialer. When you shop for such programs, make sure they have an
option to use any existing TCP/IP and dialer you already installed.
One such evil program is Netscape Navigator Personal Edition.
Make sure you tell this program to "Use existing Winsock and
dialer".
A really good tip, regardless of whose TCP/IP stack you use, is to
write-protect WINSOCK.DLL and WSOCK32.DLL. Bring up a
DOS prompt, type
CD \
DIR WINSOCK.DLL /S
and note what directory the file is in. You'll probably find multiple
WINSOCK.DLL files if you installed any "All in one" apps.
Change to that directory then type
ATTRIB +R WINSOCK.DLL
Do this for WSOCK32.DLL as well.
----------------------------------------------------------------------
Using Trumpet (tm) and other TCP/IP stacks (Just don't!)
Yes they do work, as long as you don't have any Win95
networking components installed. Problem is, when you make a
networking change, Setup might decide to re-copy the files over,
and when it does it will happily over-write WINSOCK.DLL.
Remember: Winsock was designed for other protocols too, not just
TCP/IP, and it's a standard OS component now! So, either use
Win95's networking and Win95's dialer, or use no Win95
networking and someone else's dialer.
And yes, you can make 32-bit Winsock apps work with older
stacks. There's a _WSOCK32 "thunk"_ available that works with
an existing Win 3.1 dialer and their own WINSOCK.DLL.
You could also check out Trumpet's own 32-bit TCPMAN or
TGV's replacement TCP/IP stack.
----------------------------------------------------------------------
How do I get dial-up networking to work with other stuff
besides The Internet? Like a NetWare server?
The one really cool feature that allowed Win95 to devastate OS/2
Warp Connect; general dial-up networking. MS included a
Shiva-written PPP/RAS dial-up stack that works with pretty much
any transport protocol, though there's only direct support for
NetBEUI, IPX, and TCP/IP. Clients can bind to these protocols to
work over a dial-up connection.
Install Dial-up Networking in Add/Remove Programs/Windows
Setup. Then re-boot. A Dial-up Networking folder appears in "My
Computer". You will also find a Dial-up Adapter in your Network
control panel; you will have to add protocols for this adapter as
needed.
If you're connecting to a Win95, Windows NT, or WFWG dial-up
server, you can make a connection right from the "Make new
connection" wizard. This will also work if you're connecting to a
NetWare network through a Win95 or Windows NT dial-up
server. If you log into an NT domain this way, you need "Log on to
network" turned on, otherwise you can leave it turned off to save
some time. Old WFWG or NT 3.1 dial-up servers only work with
the RAS server type; NT 3.5 and Win95 servers work with the
PPP server type.
If you're connecting to a NetWare network using NetWare
Connect (NRN), Install IPX/SPX Protocol, bring up properties for
your connection, and change the Server Type to NRN: NetWare
Connect. This disables all other protocols but IPX over that
connection. You will need "Log on to network" turned on; this will
have Win95 search for a NetWare server (Or the preferred server)
and bring up the NetWare log in requester.
NOTE: You can also use PPP to connect to a NetWare server
remotely, if your NetWare network has a Windows NT or
Win95 dial-up server running. This is a less expensive option than
Novell's NetWare Connect software.
----------------------------------------------------------------------
How do I set up auto-dial when I run my Winsock program?
Auto-dial only works if you installed Microsoft Plus! or Internet
Explorer. Once installed, your computer will bring up the dial-up
requester when any program accesses WSOCK32.DLL. Pretty
cool. For some reason this won't work with 16-bit Winsock
programs though. Dumb.
There's a new Internet control panel when you install either of
those, and you can control auto-dial and auto-disconnect from
there.
----------------------------------------------------------------------
How do I set up auto-disconnect?
As per auto-dial; install MS Plus! or Internet Explorer, and check
out the Internet control panel. You then tell it to disconnect after
some amount of in-activity (20 minutes by default).
----------------------------------------------------------------------
How do I DISABLE auto-disconnect?
Auto-disconnect does have one dumb bug; unless you're
performing active surfing in Internet Explorer (Other apps it just
ignores), the dis-connect timer will activate. This includes when
you're downloading large files via FTP, and not doing any other
mouse clicking. Pretty dumb.
Turn it off in the new Internet control panel, that shows up when
you install Internet Explorer, or MS Plus.
----------------------------------------------------------------------
My Internet provider only has SLIP. Can I use that? (yes.)
Install DSCRPT.EXE or install MS Plus. The dial-up scripter
includes a SLIP server type for dial-up networking. When you
select SLIP: Unix Connection, or CSLIP: Unix Connection, from
the server type options, you will only be able to use TCP/IP.
There are additional scripting commands for using SLIP; be sure to
check out dial-up scripting help for the details. You may need to
use the script to obtain an IP address.
----------------------------------------------------------------------
Why can't the dial up connection save my password?
Password caching only happens if you install a Win95 network
client, or enable User Profiles on a stand alone computer. By
default, the Internet Setup Wizard only installs TCP/IP protocol and
the dial-up networking components, which is all you really need.
However, MS Exchange will do login password caching
independent of the dial-up settings. In the Internet Mail properties,
select "Connection" and "Login As...", then type the username and
password. If you leave these blank, it will use the defaults for the
dial-up connection. Other utilities like RoboDUN and DUNCE will
not only save your password, but instantly dial-up without asking
you for an "OK".
----------------------------------------------------------------------
Why does my computer hang in task "RNAAPP" when I dial
out to The Internet?
A Message from William Hunt (E-MAIL address unknown) says
that sometimes the computer hangs with "RNAAPP (Not
Responding)" when you press CTRL-ALT-DEL to bring up the
task list. His fix was to hide the file named VNBT.386 which is not
needed for an Internet session.
Well this is correct; VNBT is a virtual device for NetBIOS over
TCP/IP, not needed for connecting to The Internet and using
Winsock apps. You will need this file back, however, if you run
Client for MS networks over TCP/IP or otherwise want to use
NetBIOS apps over it.
A better solution, which would prevent this VxD from being
invoked, is to set "Disable DNS" and "Disable WINS Resolution"
in TCP/IP properties, and specify the DNS address in the dial-up
connection's properties directly.
----------------------------------------------------------------------
How can I track time and costs for my dial-up connection?
Many providers have different costing schemes, so MS didn't
bother. However, check out RAS Plus 95 which monitors dial-up
connection times, and lets you define your billing scheme.
----------------------------------------------------------------------
How can I get dial-up networking to work with a null modem
cable?
MS didn't include a null modem driver for the Telephony Interface
(TAPI). However, check out this bogus MODEM.INF file, which
serves the purpose. One installed, you can treat the null modem like
any other modem in Win95.
----------------------------------------------------------------------
How do I write a dial-up script?
Download DSCRPT.EXE from Microsoft's Win95 site, or grab it
off your CD-ROM in ADMIN\APPTOOLS\DSCRIPT, and install
it from Add/Remove Programs/Windows Setup/Have Disk. Or
install Microsoft Plus! This adds a Dial-up scripting tool to your
Accessories group. If you re-install Win95, you will have to
re-install this tool; Setup will over-write the Registry keys that hook
DSCRPT into dial-up networking.
NOTE: This will also add SLIP and CSLIP to the list of dial up
server choices! However, you can only use TCP/IP over SLIP and
no other protocol.
Run the tool to list all of your dial up connections. Select your
connection, then type a path/filename to a script. The script doesn't
have to exist yet. Then hit "Edit", and you'll see Notepad. It'll ask
you if you want to create a new file; do so. Here's a sample script:
proc main
waitfor "Username:"
transmit $USERID
transmit "<cr>"
waitfor "Password:"
transmit $PASSWORD
transmit "<cr>"
delay 1
transmit "ppp default<cr>"
delay 1
endproc
The $USERID and $PASSWORD come from whatever you fed
the dial-up connection. I feed "ppp default" to the provider because
a successful log in only gives me a Unix prompt. "ppp default" runs
a program at the dial-up server which starts a PPP session, but it
isn't necessary for all dial-up servers. I even know of one public
dial-up server in Taiwan that doesn't even ask for a username and
password! This is why you should perform one manual login ("Bring
up terminal window after dialing") and learn how your provider
prompts you for this info, and then write the script based on that.
Microsoft Plus! includes an improved scripter which allows some
branching and IF/THEN programming, but it isn't necessary for all
providers. The above example works with both Plus! scripting and
the basic scripter on MS's web site.
And finally, save this script and hit "Apply" to attach the script to
the dial-up connection. You can turn on "Step through script" to test
and debug the script, then turn it off when you know it works. Hit
"Apply" to save any changes you make to a script attachment or
settings.
----------------------------------------------------------------------
How do I set up a dial-up server?
Install MS Plus. If you chose the Dial-up networking server, it will
add a new Dial-up server... menu to the Dial-up networking
window. The Win95 dial-up server is really a NetBIOS router,
meaning it doesn't actually perform WAN routing of a low level
protocol (though they did hack IPX routing in there for NetWare
clients).
In Dial-up Networking, you have a new menu:
Connections/Dial-Up Server. You can choose ONE modem to
receive calls on (Not more than one, sorry), and you can pick what
kind of dial up server it is (either PPP, WFWG RAS, or Default,
which allows for both). You can also enter a dial up password, or
pick users from a user list if you have User Level security enabled.
Now I wrote above that it's a NetBIOS router. That means it's
designed to route MS Network style traffic to a network.
Normally, a dial-up client will have Client for MS networks and
NetBEUI installed (or for WFWG clients, they just use the Remote
Access software included), because NetBEUI's the fastest
NetBIOS compatible protocol for slow links. NetBEUI isn't
route-able, but that doesn't matter; the network itself could use IPX
or TCP/IP instead, as long as it's an MS Windows style network.
...for NetWare dial-in?
NetWare dial-in works too, because Microsoft hacked a simple
IPX router in there. To do NetWare dial-up access, make sure you
install IPX protocol and bind it to the Dial-up Adapter in Network
Control Panel. The clients can be Win95 or Windows NT clients,
but they need to have IPX protocol and Client for NetWare
installed. When the user dials in, a NetWare login prompt will come
up, login scripts will execute, and connections will appear.
WARNING: IPX over PPP is quite slow! Some tips for the client,
to speed up performance:
Allow only IPX protocol for dial-out to the dial-up server (turn
NetBEUI and TCP/IP OFF in Server Type)
Keep local copies of MAP.EXE and CAPTURE.EXE on the
remote computer, in the WINDOWS\COMMAND directory
Turn Software Compression ON
Pick a frame type in IPX properties (Don't use Auto-Detect)
Don't run NetBIOS apps over the dial-up connection through
IPX
----------------------------------------------------------------------
Top five reasons to use a Win95 machine as a dial-up server
5) Cheap NetWare dial-in access (A LOT cheaper than NetWare
Connect!)
4) Cheap Windows Network dial-in access
3) Effortless (almost) connection to your network from home
2) Works with non-Win95 MS Network clients (like an Amiga
using SAMBA!)
1) User-Level security works here (Not like NT RAS Server)
----------------------------------------------------------------------
Top ten mis-conceptions about Win95 dial-up servers
10) Fast connection speeds (NOT!)
9) It routes TCP/IP (This is a Resource Kit error.)
8) It does MS-Mail Remote (Sorry, it doesn't)
7) It routes NetBEUI (It's a NetBIOS router; NetBEUI isn't
route-able)
6) You need NetBEUI on the net card to route (It's a NetBIOS
router; it doesn't matter)
5) You need NetBEUI on the Dial-up Adapter to use it (It's faster,
but it doesn't matter)
4) It won't work with non-Win95 dial-up clients (Bull... I've used
my Amiga to dial in! Couldn't transfer any files though... heh heh)
3) It doesn't work with null modem cables (check out this bogus
modem.inf file if you want to use a null modem)
2) It's a security risk to my network! (Geez, you can disable the
dial-up server in system policies for the default computer, then
enable it for the computers you want it to work on.)
1)
----------------------------------------------------------------------
Top ten Internet/dial-up mistakes
10) Using a Win 3.1 TCP/IP protocol
9) Installing Netscape Navigator Personal Edition and using its
dialer instead of Win95's
8) Buying lots of Winsock software before checking out
www.windows95.com
7) Using default dial-up connection settings and crashing your
provider's server
6) Telling your provider you have Win95 (Many of them cringe
upon hearing that)
5) Buying Microsoft Plus! JUST for dial up scripting, before trying
the free DSCRPT tool
4) Installing a provider's setup disk for Win 3.1 (dumb mistake;
many providers do that!)
3) Leaving "File & Print Sharing for MS networks" turned on over
TCP/IP
2) Not getting connection and server information from your
provider
1) Not reading the Modem section of this FAQ page
----------------------------------------------------------------------
[Back to Table of Contents]
--
============================================================// //========
= "I am Gordon of Winterpeg. Windows WAS futile." // // =
= Find out why: http://www.intouch.bc.ca/win95 // // =
= Personal E-MAIL: gordonf@vcn.bc.ca \\ \\// // =
= Home Phone: +1-604-526-8724 \\ XX // =
= \X/\X/ =
= "I am Hitler of BorgSoft. I am the middle inital of William H. Gates. =
= Your work will be Microsofted. Resistance is futile. Heil Windows. =
=========================================================================
Yeah I use an Amiga at home. If you don't like my computer, dial
1-800-DIE-BILL and tell someone who cares.
----------------------------------------------------------------------
Path: news1.ucsd.edu!ihnp4.ucsd.edu!swrinde!cs.utexas.edu!howland.reston.ans.net!nntp.coast.net!news.kei.com!news.mathworks.com!nntp.primenet.com!news.cais.net!van-bc!unixg.ubc.ca!freenet.vancouver.bc.ca!gordonf
From: gordonf@vcn.bc.ca (Gordon Fecyk)
Newsgroups: comp.os.ms-windows.win95.misc,comp.os.ms-windows.setup.win95,comp.os.ms-windows.networking.win95,comp.os.ms-windows.apps.compatibility.win95,comp.answers,news.answers
Subject: Win95 FAQs and Answers Part 9 of 14: Annoyances
Followup-To: comp.os.ms-windows.win95.misc,comp.os.ms-windows.setup.win95,comp.os.ms-windows.networking.win95,comp.os.ms-windows.apps.compatibility.win95
Date: 30 Jun 1996 16:33:04 GMT
Organization: Vancouver Regional FreeNet
Lines: 616
Approved: news-answers-request@MIT.EDU
Message-ID: <4r6a80$80p@milo.vcn.bc.ca>
NNTP-Posting-Host: opus.vcn.bc.ca
Summary: These postings list many questions asked in said newsgroups,
and answers them as best as I can. I make references to other
Web sites and FAQs when appropriate. Visit the WWW home of
this FAQ (http://www.intouch.bc.ca/win95) for the appropriate
links. This section is the 9th: Maintanence
X-Newsreader: TIN [version 1.2 PL2]
Xref: news1.ucsd.edu comp.os.ms-windows.win95.misc:111602 comp.os.ms-windows.setup.win95:10979 comp.os.ms-windows.networking.win95:7513 comp.os.ms-windows.apps.compatibility.win95:3578 comp.answers:15517 news.answers:61918
Archive-name: windows/win95/faq/part09
Last-Modified: 1996/07/01
Posting-Frequency: Every two months
URL: http://www.intouch.bc.ca/win95/faq9.htm
9) Maintaining a clean installation
of Windows 95, and annoyances
(Details at the Win95 Annoyances FAQ)
How do I remove (this desktop item)...
...Inbox?
...Network Neighborhood?
...My Computer?
How do I rename My Computer?
...Recycle Bin?
How do I rename the Recycle Bin?
...The Microsoft Network (tm) ?
How do I remove (this annoying startup program)...
...programs in the StartUp group in the Start Menu?
...programs that don't seem to be in the StartUp group?
...programs that aren't even listed in WIN.INI or The
Registry! (IE: Norton Anti-Virus)
How do I remove Start Menu entries?
...on computers using User Profiles on networks? (They
keep coming back!)
How do I de-activate that dumb "Documents" menu?
How do I completely remove...
...Windows 95 components?
...programs "Designed for Windows 95"?
...drivers for unused hardware and printers?
...Internet Explorer (tm) ?
...The Microsoft Network?
...dumb Windows 3.x programs? (How to use third party
un-installers)
...old DOS and Windows 3.x files?
...Windows 95?
How do I stop the constant hard drive access?
Why should I let Win95 manage virtual memory?
Does RAM compression really work? (No.)
How do I stop the constant floppy drive access?
How do I stop the constant CD-ROM access when there's no
disk in the drive?
How do I set up user profiles so I can keep my own desktop
clean?
Why user profiles is a really cool and useful feature, even for
stand alone computers!
What are .gid files? Are they safe to remove?
What are "mscreate.dir" files? Are they safe to remove?
Can I remove the "failsafe.drv" directory?
Can I remove the "~mssetup.qt" directory"
Top ten mis-conceptions about removing annoying items
How to back up your Registry before you goof it up
OK, so you don't want the Net Neighborhood cluttering your
desktop because you only have a 'Net connection, or your Win95
takes up too much hard drive space, or whatever. Maybe your
system runs too slow and you want to speed it up. Maybe you
heard about some cool utility that'll speed up your computer. Read
about it here.
More important, read the Win95 Annoyances FAQ for more
details, if you think I'm missing something. This is where most of this
info came from. BE WARNED: I do not recommend Registry
hacking via REGEDIT to clean up your system! All my tips here
demonstrate methods without using REGEDIT; rather they use
Policy Editor. POLEDIT works with stand alone computers to
directly edit the Registry, as well as creating policy files.
----------------------------------------------------------------------
How do I remove The Inbox?
If you don't have MS Exchange installed, you can remove this icon
by just right-clicking it and selecting "Delete". If you don't use it and
you want to get rid of it, run Add/Remove Programs/Windows
Setup, and de-select all the MS Exchange and MS Fax
components. The next time you re-start the Inbox icon will not be
there.
If you want to keep Exchange but still remove the Inbox, you'll have
to resort to this Registry Hack.
----------------------------------------------------------------------
How do I remove Network Neighborhood?
If all you use is Internet access and don't use any other Win95
networking, you can run Network Control Panel, and remove all
network components but the Dial-up Adapter and TCP/IP. This
will remove the Net Neighborhood and all other Win95 clients from
your system. NOTE: This will also disable password caching!
If you use Win95 clients as well, you can hide it with Policy Editor
in Default User/Shell/Hide Network Neighborhood. You can also
hide individual components of Net Hood. NetWare NDS networks
have additional Net Hood restrictions you can enforce as well.
----------------------------------------------------------------------
How do I remove My Computer?
You can't hide the icon itself, because it still points to Control Panel,
Printers, and Dial-up networking. You can hide the drives
themselves, however, from Policy Editor; Default User/Shell/Hide
drives in My Computer.
Apparently according to Annoyances, you can also make up a
"blank" icon (using any freeware icon editor) and use MS Plus to
change the icon to it. Also, rename the "My Computer" to a single
space. The icon's still there, but no one will see it. You might also
want to drag this invisible icon to an inconspicuous place on your
desktop.
----------------------------------------------------------------------
How do I rename My Computer?
Right-click on it and hit "Rename".
----------------------------------------------------------------------
How do I remove the Recycle Bin?
This requires a Registry Hack.
----------------------------------------------------------------------
How do I rename the Recycle Bin?
This also requires a Registry Hack but Norton Utilities for Win95
allows you to rename it. Other Recycle Bin hacks (such as Desktop
Toilet) do the job as well.
----------------------------------------------------------------------
How do I remove The Microsoft Network (tm) icon?
I would just say Don't Use MSN, but you can right-click on the
icon and delete it; it's just it will re-appear whenever you log in to
MSN. If you choose not to use MSN (Good for you!) you must
delete the icon BEFORE you de-install MSN or the Delete option
goes away.
Oops... I was wrong. The Delete option does go away, but the icon
will disappear the next time you re-start Win95.
----------------------------------------------------------------------
How do I remove programs in the StartUp group in the Start
Menu?
The Start Menu (And desktop as well) are just directories with
shortcuts inside. You can right-click on the Start Menu and hit
Open, then find the startup folder and delete the shortcuts in it. You
can also right-click on the taskbar, get Properties, and in Start
Menu Items tab, hit "Remove".
----------------------------------------------------------------------
How do I remove programs that don't seem to be in the
StartUp group?
Some Win 3.1 thinking programmers (like at ATI) put their
programs in SYSTEM.INI's load= line in the [boot] section. Don't
they trust themselves with the Registry yet? You can run
SYSEDIT.EXE and delete the offending load= line from
SYSTEM.INI.
Programs that insert themselves in the Registry run before
SYSTEM.INI gets touched. You can remove these using Policy
Editor; Default Computer/System/Run.
Interesting note: "Run Services" shows programs that run even
before you get a log in prompt. Some anti-virus software may insert
themselves here (Some viruses could insert themselves here too!)
----------------------------------------------------------------------
How do I remove programs that aren't even listed in
SYSTEM.INI or The Registry! (IE: Norton Anti-Virus)
I haven't figured Norton Anti-Virus out yet! That's so weird; they
aren't in the load=, or in the Registry, or even in
AUTOEXEC.BAT; yet the anti-virus monitor can still load! I think
they hack into one of the Win95 core system files somehow.
The best bet is to un-install the offending program with its
un-installer. All "Designed for Win95" programs have an
un-installer.
----------------------------------------------------------------------
How do I remove Start Menu entries?
Right-click on the Taskbar and get Properties, get Start Menu
Programs, and hit "Remove". Then pick and choose.
You can also right-click on the Start button and hit Open. Then
pick and choose the shortcuts you want to delete.
...on computers using User Profiles on networks? (They
keep coming back!)
Yes I know. Win95's supposed to update the network copy of the
shortcuts on log-out, but sometimes they just keep coming back.
Delete them from your Home directory or MAIL directory as well
to keep them from coming back.
----------------------------------------------------------------------
How do I de-activate that dumb "Documents" menu?
Normally you can right-click on the Taskbar, hit "Start Menu
Programs", and hit "Clear Documents Menu" to clear it. But it will
just fill up as you work with Win95.
There's a Registry Hack that relocates the Documents menu (the
RECENT folder) to the Recycle Bin, and if you have "Remove
immediately" turned on it will keep that menu clean, but there IS a
safer way.
In AUTOEXEC.BAT include this line:
DEL %WINDIR%\RECENT\*.*
An even more effective way to keep the documents menu clean,
and still enjoy its functionality during a single Win95 session, is to
insert a command into System Agent, if you have MS Plus!
installed. Write a batch file with the above command in it, then add
it into System Agent. Schedule it to run "On Startup". This method
won't work if you use User Profiles, but there's a work-around for
that if you used WINSET to copy the %USERNAME% variable.
Use this style of batch file instead:
DEL %WINDIR%\PROFILES\%USERNAME%\RECENT\*.*
NOTE: DOS programs run from System Agent should have
"Background: Always Suspend" turned OFF! Also, instead of
inserting the program itself into System Agent, insert its PIF file
instead.
Additional NOTE: You can run PIF files from the Registry, from
load= in SYSTEM.INI, or in the StartUp group as well, in case
you don't have System Agent.
----------------------------------------------------------------------
How do I completely remove Windows 95 components?
All the OS components are in Add/Remove Programs/Windows
Setup. You can add and remove them from there, and Win95
deletes the required files from your hard disk as well.
Other additional components you add in this requester (like dial-up
scripting) are removable from the main Install/Un-install tab.
----------------------------------------------------------------------
How do I completely remove programs "Designed for
Windows 95"?
All programs Designed for Win95 have an un-installer you can
access from Add/Remove Programs/Install/Un-install. If not,
complain to the publisher of the program. If that doesn't work,
complain to Microsoft, who awarded the logo to them.
A program's un-installer will remove its components and Registry
entries, if properly written.
----------------------------------------------------------------------
How do I completely remove drivers for unused hardware
and printers?
Printers are rather conveniently removed; if Explorer realizes you
removed a printer and no other printer uses its drivers, it will offer
to delete the offending files.
Other hardware drivers will remain, however. So, if you want to
remove files used by a given piece of hardware, run Device
Manager and bring up that device's properties. Bring up the
"Driver" tab, copy this list where the driver files are, and delete
them after you remove that device. You have to look BEFORE you
remove the device, and not AFTER, or the list disappears with the
device entry.
----------------------------------------------------------------------
How do I completely remove Internet Explorer (tm) ?
If you use MS-Plus you need to remove Internet Explorer from
Plus' un-installer. IEXPLORE 2.0 will have its own un-installer, but
the un-installer will keep the Internet Setup Wizard and its control
panel entry in tact. You can always re-run the setup wizard even if
you installed a different browser to replace IEXPLORE. It also
keeps the Internet Mail client for MS-Exchange installed, which
won't disappear unless you remove Exchange.
NOTE: According to Win95 Annoyances, IEXPLORE will keep
many pieces of itself in the system after you un-install it this way.
IEXPLORE 2.0 does a better job of un-installing itself, but it still
keeps the Setup Wizard, mail client for Exchange, and auto-dialer
in tact. You should keep these really, but you can delete the
"Program Files/Plus!/Microsoft Internet" folder afterwards.
To keep the file type registrations in tact, you should re-install your
browser of choice after you un-install Internet Explorer.
IEXPLORE's un-installer will destroy any changes you made to
.HTM and .HTML file type entries.
----------------------------------------------------------------------
How do I completely remove The Microsoft Network?
Remove the BillNet icon from the Desktop, then remove BillNet
from Add/Remove Programs/Windows Setup,. This will remove
the main MSN control program and the Exchange mail client, but it
will install a "Set up the Microsoft Network" installer in its place.
You can simply delete the Program Files/The Microsoft Network
folder completely afterwards, even though it says "This will impact
one or more registered programs." Big deal.
Win95 Annoyances says the BillNet icon's Delete option goes
away after you remove it from Add/Remove Programs/Windows
Setup. So, remove the icon first, then un-install BillNet. I found,
however, that the icon will go away by itself, when you re-start.
----------------------------------------------------------------------
How do I completely remove dumb Windows 3.x programs?
(How to use third party un-installers)
Get a decent Designed for Win95 un-installer if you want the
flexibility of removing Win 3.1 apps cleanly.
The only un-installer which actually works (that I saw, anyways) is
CleanSweep 95 from Quarterdeck, but it only works if you install
the Win 3.1 program AFTER you install CleanSweep.
To use CleanSweep, just try running any program called "SETUP"
or "INSTALL" or any number of variants. The CleanSweep
monitor kicks in and asks you if you want to monitor the installation.
Also available now is Remove-IT 95 by Vertisoft. This program
does a great job of completely nuking The Microsoft Network,
including all Registry entries.
My Boss, Jim Farewell, firmly believes you should use a
"Professional Un-Installer" to monitor all app installations, including
Designed for Win95 ones. OK, have it your way. Just be prepared.
----------------------------------------------------------------------
How do I completely remove old DOS and Windows 3.x files?
Win95 Setup will maintain your old DOS and Windows, if you
chose to install on top of your existing Windows setup. Later on,
you can remove the old DOS and Windows files from
Add/Remove Programs/Install/Un-Install.
If you installed Win95 in a different directory, you can also simply
delete the old DOS and Windows folders in Explorer. Win95
Setup would've included your old DOS directory in your path,
however, so maybe leave that one alone until you decide you don't
need the old DOS utilities anymore.
----------------------------------------------------------------------
How do I completely remove Windows 95?
You can also un-install Win95 from Add/Remove
Programs/Install/Un-Install, if you installed on top of your existing
Windows. If you installed in a different directory, however...
Re-boot the computer with your old DOS disk
From the DOS prompt, type SYS C: (This restores the original
DOS system files)
Rename CONFIG.DOS to CONFIG.SYS and
AUTOEXEC.DOS to AUTOEXEC.BAT
Re-boot off the hard drive
Then you can remove your Win95 directory, PROGRA~1
directory, and any hidden or system files you don't recognize. The
easiest way to do this is run Win 3.1 File Manager, and have
"Show Hidden/System Files" turned on in View/File Types".
----------------------------------------------------------------------
How do I stop the constant hard drive access?
Win95 is always swapping between its RAM and the hard drive's
swap file, especially on 8 MB systems or systems with several
programs running at once. To ease the swapping:
1) Edit SYSTEM.INI; add this to the [vcache] section:
maxfilecache=1024 (on 16 MB systems, or 512 on 8 MB systems)
2) Right click on My Computer, hit Properties, hit "Performance",
and go through these settings:
File system/hard disk: read ahead size: 16 KB (Any smaller will
make Win95 un-stable)
File System/CD-ROM caching: reduce to around 250 KB, no
less
Virtual memory: manually manage the swap file, and pick a fixed
swap file size: 20 MB for 8 MB systems, 32 MB for 16 MB
systems
You will find these settings give the quietest hard drives, even with
disk compression used!
NOTE: Norton Navigator will cause additional disk swapping,
because it maintains more shortcuts in the Start Menu which
will verify that their targets exist.
----------------------------------------------------------------------
Why should I let Win95 manage virtual memory?
Only if you're low on disk space should you let Windows manage
virtual memory, otherwise a fragmented swap file will slow down
program swapping. Specify a fixed swap file size as per the
suggestions above.
Win95 will try to grow/shrink the swap file as required. On systems
with low disk space this is actually a GOOD thing, because it
doesn't instantly eat hard drive space. On systems with large hard
drives this will become an annoyance, and the swap file will
fragment, slowing down swapping.
Others (many others) suggest letting the swap file grow is a GOOD
thing on big systems, because large programs can "Bottom-out" on
fixed swap files. If you choose to let Win95 manage virtual
memory, include this line somewhere in AUTOEXEC.BAT:
DEL C:\WIN95\WIN386.SWP
So when your computer re-starts Win95 will re-build the swap file
un-fragmented. While you're at it, you can kill the contents of the
TEMP directory the same way (C:\WIN95\TEMP).
----------------------------------------------------------------------
Does RAM compression really work? (No.)
Those programs were for Win 3.1 apps that ate ridiculous amounts
of GDI memory (System Resources), where they fixed
inadequacies in the operating system. Win95 has larger resource
limits, and properly written Win32 programs won't use them... as
much.
Please save your money and effort, and stay away from this bogus
software. If you really need to run 500 programs at once, get
Windows NT Workstation. Or get an Amiga.
----------------------------------------------------------------------
How do I stop the constant floppy drive access?
This is evident of shortcuts and PIF files pointing to files on floppy
disks.
When Win95 builds its Start Menu, it checks all the shortcuts to see
that they point to something intelligent. This will lead to floppy
access when you view the Documents menu, for example.
Whenever you run a DOS program, Win95 builds a PIF file for it.
If the program ran from a removable disk (like a floppy or
CD-ROM) it will store the PIF in %WINDIR%\PIF.
To stop the constant floppy access from these shortcuts, right-click
on the hard drive with Win95 in it and hit "Find...", then in the
search space, type "*.lnk;*.pif", then hit the Advanced tab and in
the "Containing Text" box, type "A:". Hit Find.
That search should generate a list of shortcuts pointing to drive A,
including those in your RECENT, and PIF folders. Delete them
from this window. Don't delete any shortcuts in the "SendTo"
folder, but you should be able to safely delete the rest. The random
floppy access will stop once you do.
To avoid getting this random disk access again, avoid launching
documents and programs off floppy disks. Instead, open
documents from the program they came from, and run DOS
programs by opening a DOS prompt first, then switching to A: and
running it from there.
Also see how to Delete the Documents menu on startup.
NOTE: Norton Navigator will cause even more floppy access,
because it maintains more shortcuts at a time, especially floppy
file shortcuts!
----------------------------------------------------------------------
How do I stop the constant CD-ROM access when there's no
disk in the drive?
Win95's CDFS auto-detects disks when inserted, so Explorer can
properly update the drive and folder windows. It also looks for an
AutoPlayer on the disk (autoplay.inf) and will launch it. Because of
this continuous checking, the CD-ROM drive light will flash. If it's
an IDE drive, your HD light will flash along with it.
You could use real mode CD-ROM drivers and MSCDEX
instead, but this leads to very pathetic performance. I would say
ignore it and don't worry, because this auto-detect takes about 0%
processor time. But if you insist on being annoyed by it:
Bring up My Computer/Properties and select Device Manager.
Bring up properties for the CD-ROM drive, and turn off
"Auto-Insert Notification". This is also advisable for CD-ROM
changer owners, otherwise it will scan all of your platters when you
insert the cartridge. Maybe turn it on for the first platter and leave it
off for the rest; CD-ROM changers show up as multiple drives,
because each platter has its own SCSI LUN ID.
----------------------------------------------------------------------
How do I set up user profiles so I can keep my own desktop
clean?
User Profiles go a long way in keeping your computer clean, if you
have several users using it.
Go to Passwords Control Panel (which is always there even for
non-networked machines) and in the User Profiles tab, select "Each
user has their own settings". Also turn on the Custom Desktop and
Custom Start Menu.
Why user profiles is a really cool and useful feature, even
for stand alone computers!
Read all about it here. You can keep custom settings for every
Win32 app, not just for the desktop and start menu. It's also good
if you destroy your Registry by accident; at least half of it is saved.
----------------------------------------------------------------------
What are .gid files? Are they safe to remove?
.GID files are help index files. They include word lists for the
matching help file.
Yes they're safe to remove, but when you access the help file next
time, WINHLP32 will re-build the .GID file. Also, some Win32
programs require the .GID file be present. To re-build a deleted
.GID file, open the help file from Explorer.
----------------------------------------------------------------------
What are "mscreate.dir" files? Are they safe to remove?
These are directory index files that MS Office "Fast Find" makes
when you first access a directory. You can remove these, but
FastFind will re-create them when you access the folder again. To
keep them from coming back, remove the Fast Find shortcuts in
your Startup group.
----------------------------------------------------------------------
Can I remove the "failsafe.drv" directory?
If you don't use disk compression you can remove this. Otherwise
don't. Win95 uses the programs here to undo interrupted
compression tasks. The programs in here are actually Win 3.1
programs, that run in the special DOSX environment, to do
compressed drive conversions and such.
----------------------------------------------------------------------
Can I remove the "~mssetup.qt" directory"
I don't know why MS Office 95 leaves this thing there, but yes, you
can remove it. It only contains another directory called ~pp.t which
is equally useless.
----------------------------------------------------------------------
Top ten mis-conceptions about annoying items
10) Microsoft blatantly put them there as ads
9) Microsoft blatantly put them there to take up disk space
8) You have to use REGEDIT to remove them
7) You need a RAM compression program to run Win95 (NOT!)
6) Letting Win95 manage virtual memory is a good thing (heh
heh...)
5) Win95 removes competing programs (nonsense! I use WP 6.1
and it doesn't disappear, though Win95 Annoyances claims that
programs can disappear)
4) You need third-party un-installers for Win95 programs (Get the
Win95 programs fixed!)
3) You can happily delete DLLs etc not listed in WIN.INI or
SYSTEM.INI (But what about the Registry?)
2) You can delete SYSTEM.DAT (Not unless you want to
re-install Win95... heh heh)
1) Win95 scans your hard drive and reports its contents to
Microsoft (Big Brother is watching you... not)
----------------------------------------------------------------------
How to back up your Registry before you goof it up
Yes, you will probably try one of the registry hacks you read about
in Win95 Annoyances. Well, before you do so, boot to "Command
prompt only", and do this:
CD %WINDIR%
COPY SYSTEM.DAT SYSTEM.BAK
COPY USER.DAT USER.BAK
Then you can re-boot and happily tweak away using REGEDIT
and POLEDIT. If you do screw up and you can't re-start Win95,
then go back into command prompt only and re-copy
SYSTEM.DAT and USER.DAT.
SYSTEM.DAT is more critical than USER.DAT; the distinction is
more important when you use User Profiles, because each user has
their own USER.DAT.
----------------------------------------------------------------------
[Back to Table of Contents]
--
============================================================// //========
= "I am Gordon of Winterpeg. Windows WAS futile." // // =
= Find out why: http://www.intouch.bc.ca/win95 // // =
= Personal E-MAIL: gordonf@vcn.bc.ca \\ \\// // =
= Home Phone: +1-604-526-8724 \\ XX // =
= \X/\X/ =
= "I am Hitler of BorgSoft. I am the middle inital of William H. Gates. =
= Your work will be Microsofted. Resistance is futile. Heil Windows. =
=========================================================================
Yeah I use an Amiga at home. If you don't like my computer, dial
1-800-DIE-BILL and tell someone who cares.
----------------------------------------------------------------------
Path: news1.ucsd.edu!ihnp4.ucsd.edu!swrinde!howland.reston.ans.net!nntp.coast.net!news.kei.com!news.mathworks.com!nntp.primenet.com!news.cais.net!van-bc!unixg.ubc.ca!freenet.vancouver.bc.ca!gordonf
From: gordonf@vcn.bc.ca (Gordon Fecyk)
Newsgroups: comp.os.ms-windows.win95.misc,comp.os.ms-windows.setup.win95,comp.os.ms-windows.networking.win95,comp.os.ms-windows.apps.compatibility.win95,comp.answers,news.answers
Subject: Win95 FAQs and Answers Part 10 of 14: MS Exchange
Followup-To: comp.os.ms-windows.win95.misc,comp.os.ms-windows.setup.win95,comp.os.ms-windows.networking.win95,comp.os.ms-windows.apps.compatibility.win95
Date: 30 Jun 1996 16:33:53 GMT
Organization: Vancouver Regional FreeNet
Lines: 628
Approved: news-answers-request@MIT.EDU
Message-ID: <4r6a9h$80p@milo.vcn.bc.ca>
NNTP-Posting-Host: opus.vcn.bc.ca
Summary: These postings list many questions asked in said newsgroups,
and answers them as best as I can. I make references to other
Web sites and FAQs when appropriate. Visit the WWW home of
this FAQ (http://www.intouch.bc.ca/win95) for the appropriate
links. This section is the 10th: MS Exchange
X-Newsreader: TIN [version 1.2 PL2]
Xref: news1.ucsd.edu comp.os.ms-windows.win95.misc:111606 comp.os.ms-windows.setup.win95:10983 comp.os.ms-windows.networking.win95:7517 comp.os.ms-windows.apps.compatibility.win95:3582 comp.answers:15521 news.answers:61922
Archive-name: windows/win95/faq/part10
Last-Modified: 1996/07/01
Posting-Frequency: Every two months
URL: http://www.intouch.bc.ca/win95/faq10.htm
10) Microsoft Exchange (tm): Their
"Universal Inbox"
Exchange basics, and why I recommend Exchange for first time
E-MAIL users
How do I send and receive...
...Internet mail?
How do I make Exchange behave like a "normal" mail
client?
Top ten Internet Mail annoyances
...MS Mail?
How do I view shared folders on an MS Mail server?
...Comp-U-Serve (tm) mail?
...Faxes? (UPDATE)
How do I share fax modems between Windows 95
machines?
How do I share fax modems between Windows 95
and WFWG machines?
Top ten Microsoft Fax annoyances
What about WinFax PRO (tm) for Win95?
...MHS mail?
...cc:Mail?
...Microsoft Network mail?
Remote Mail basics for MS Mail, Internet Mail, CIS Mail, and
Microsoft Network Mail users
How can I keep mail on the server?
How can I keep a separate inbox or address book for each
user? (Exchange Profiles)
Address Book basics
Top ten mis-conceptions about Exchange
Wish List
----------------------------------------------------------------------
Exchange basics, and why I recommend Exchange for first
time E-MAIL users
The bloody thing comes with the operating system, for one, so it's
free!
Exchange acts as a front end for pretty much any mail client, so it
lets the developers worry about mail delivery, while it worries about
the interface. Basically, you start with four folders, and all your
personal mail comes in your Inbox folder. Stuff you send stays in
your Outbox folder until a "Delivery" happens, either when you
select "Deliver now" or one of the Exchange clients (such as
Internet Mail) decides it's time to deliver mail, scheduled in time
intervals you can control.
Within the Exchange window you can drag messages between
folders, shared folders if available, or directories in Explorer.
Another big reason: it's interface matches the Windows Explorer so
closely. You can copy & paste messages between it and other
Explorer windows. You don't need to learn a whole new interface
just to use a second, or third mail system.
Yet another big reason: You get all your mail in one place! Internet
mail, CompuServe mail, faxes, MSN, MS-Mail, and whatever
anyone else decides to make for it. All big apps that support MAPI
(those with a "Send Mail..." menu in their File menus), even Win 3.1
apps, work with it. Send a Word document to your buddy at
nowhere.com, without fussing with saving, running your other mail
program, and attaching. Exchange also stores mail on the user's
hard drive or Home directory, so the mail server need not be
running to view mail.
Many users and developers are just beginning to grasp what
Exchange is capable of, and most of us make many, many,
mistakes, and abandon it in favor of "standard" mail apps. Please
don't give up; Exchange has serious potential, and many of the
features you think are missing, might just be in there... maybe even
improved on!
----------------------------------------------------------------------
How do I send and receive Internet mail?
Easiest way, is download Microsoft's Internet Explorer and install
it, then run the Internet Setup Wizard. Feed the wizard all the info it
needs; get it from your provider. Alternately, download MS's
stand-alone Internet Mail Client for Exchange, if you don't want to
use Internet Explorer. Then add Internet Mail to your Exchange
Profile, or let the setup wizard do it.
If you use a dial-up connection, be sure to enable Remote Mail
otherwise it will dial up your provider every 15 minutes. The
Internet Setup Wizard automatically turns on Remote Mail.
When you write your messages, enter addresses as you would for
any other Internet mail program, in the To: Box of the Send
Message requester. Separate multiple addresses with semicolons
(a ";") instead of commas. Hit File/Properties to change the sending
options of this message if you wish; you can send attachments
MIME or UUEncoded, use a different character set if you're
sending messages overseas, and such. Finally hit the "Send" button.
Notice, however, it does not deliver the message immediately. It
will not deliver the message until you run a Remote Mail session, or
you hit Tools/Deliver Now Using/Internet Mail. Automatic sending
doesn't happen unless you turn off Remote Mail.
Microsoft's Internet Mail client only works with a POP3 server and
an SMTP server for outgoing mail. In Internet Mail properties, you
can specify a different server for outbound mail by hitting
"Advanced", and typing in the name of the outgoing mail server. I'm
hoping for an IMAP4 client some time soon, but 90% of providers
don't use IMAP4. Sad. There are also many more replacement
Internet mail clients poping up, including from Netscape, Corel, and
Delrina.
----------------------------------------------------------------------
How do I make Exchange behave like a "normal" Internet
Mail client?
Download Internet Idioms from Angry Greycat Designs. This adds
an Idioms tab to the Exchange options requester. You can choose a
default read font (I recommend Courier-New 10), a default Send
Mail font (Again, Courier-New 10), you can add a signature to all
your e-mail (including MS-Mail, Faxes, MSN, whatever), and you
can use a "standard" reply idiom with tabbed text and little ">" all
over the place. His installation is a bit un-friendly, but just keep
bugging him, or grab my copy which includes a nice installation
batch file.
If you use MIME to encode messages and attachments (the
default), set the character set to your appropriate choice. Most of
us should set it to US-ASCII. Select Internet Mail properties, hit
Message Format, hit Character Set, and select US-ASCII. This
will remove equal signs and "=3D" codes in messages. If you turn
off MIME, either in the properties of your message or in the
Character set here, it will send attachments UUEncoded.
Ben Goetter, founder of Angry Greycat Designs, also has an
excellent Exchange FAQ.
----------------------------------------------------------------------
Top ten Internet Mail annoyances
10) WINMAIL.DAT attachment (attaches a "Rich text format"
message; turn off "Use Rich Text Format" in Internet address book
entries, or type in target addresses directly (such as
"gordonf@vcn.bc.ca" rather than "[SMTP:gordonf@vcn.bc.ca]")
9) Can't insert a .signature (get Internet Idioms)
8) Funny codes show up when using MIME encoded messages
(Set the charset to US-ASCII to fix)
7) It insists on deleting mail off my mail server (Use Remote Mail to
transfer mail instead)
6) It keeps dialing up my ISP every 15 minutes (Tell it to work
off-line and use Remote Mail instead)
5) It won't automatically send my mail (You'll have to do a
Tools/Deliver Now or use Remote Mail)
4) I can't set it up for more than one user (Create multiple Exchange
Profiles or User Profiles)
3) It won't do Blind Carbon-copy (Just turn on "BCC Box" in the
View menu of any new message window)
2) It won't do a bulk mailing (Use your Personal Address Book
and make a group up for your bulk mailing. Personally, I don't like
bulk mail (SPAM) anyways!)
1) It won't take commas between multiple receipients (That's an
MS-Mail throwback; use semicolons instead)
----------------------------------------------------------------------
How do I send and receive MS Mail?
Add Microsoft Mail Services, in Add/Remove Programs/Windows
Setup, if it isn't already in there. Then add it to your Exchange
profile. It will ask you for the network path to your MS-Mail
server, either full version or WFWG type server, and will let you
select your name from a list of names. The Mail Administrator has
to add you to the user list before you can pick from here, though.
MS-Mail under Exchange has all the original benefits of MS-Mail's
original 3.2 program, and Exchange will let you import your old
.MMF files and address book into your Personal Folders. Select
File/Import.
How do I view shared folders on an MS Mail server?
Exchange's original MS-Mail client didn't support shared folders,
but download Microsoft's Exchange Update, which includes an
MS-Mail client update, to get them back. Install it through
Add/Remove Programs/Windows Setup/Have Disk.
After you install it, you will need to re-boot, then remove and
re-add MS-Mail to your Exchange Profile. Once you do, the
MS-Mail Shared Folders will show up as a separate folder tree in
your folder view window. You can then copy mail back and forth
between folders on it, and your personal folders, and create new
shared folders.
----------------------------------------------------------------------
How do I send and receive CompuServe (tm) Mail?
This is a big money saver, because it lets you manage your mail off
line, but it requires you already installed the CompuServe
Information Manager on your computer (The Win 3.1 or DOS
version works fine). If you already haven't installed CIM, do so,
and feed it your account information.
First, download the CompuServe Exchange client, or look on your
CD-ROM for DRIVERS\OTHER\EXCHANGE\COMPUSRV.
Next, run the Setup program. That will install the CompuServe mail
client and it will run the Inbox Setup Wizard for that client. Tell it
where your CIM directory is (usually C:\CSERVE), tell it your
access phone number including country code and area code (even if
it's local; this follows TAPI spec), and access type (Direct,
DATAPAC, whatever). I'm not sure why it wants to use your CIM
directory though; maybe for copying its address book perhaps?
When finshed, and after you re-start Exchange, you can send mail
to addresses in CompuServe's format (xxxxx.yyyy) or make
Personal Address Book entries with CIS addresses in them.
Now, to deliver CIS mail, select Tools/Deliver Now
Using/CompuServe Mail. It will dial up your local CIS access
number, prompt you for a password (unless you gave it your
password), then deliver your mail. Regardless of wether you have
mail or not, the CIS client will generate an event log and post it in
your Inbox.. Remote Mail also works with CIS mail, letting you
keep mail on the CIS server, etc, as will Internet Idioms.
----------------------------------------------------------------------
How do I send and receive Faxes?
Add Microsoft Fax services, from Add/Remove
Programs/Windows Setup. Then add Microsoft Fax to your
Exchange profile. It will ask you for your name, fax number, and
other such items that would belong on a fax cover sheet. Of course,
it will ask you what fax modem you want to use.
You can then send faxes like any other kind of E-MAIL, including
.signatures if you installed Internet Idioms. But far more useful than
the regular message requester, is the "New Fax" wizard, which lets
you specify a nice cover page (even let you create a new one from
scratch), a nice short message, and a proper phone number with
area code (following Win95's TAPI spec).
And yes, you can print to a fax (or send mail to a Fax address)
from any Windows app. Fax Setup adds a Win95 printer driver for
faxing. No need to make cover pages in your documents though;
you can use the built-in cover page editor to make new ones, or use
the four built-in ones.
If you want to send a message to both E-MAIL and FAX
addresses, use the Fax Address Wizard to insert a Fax address
while in any Send Mail requester. Select Tools/Fax Address
Wizard. This will let you choose a cover page and insert a proper
TAPI phone number in to the fax address. After the wizard
completes you can continue to add more E-MAIL or FAX
addresses. Attachments will get sent too; Exchange will launch the
attachment's associated program and tell it to print to the Microsoft
Fax driver.
NOTE: MS-Word for Win95 has a mail merge bug though; if
you attempt a mail-merge from Word to multiple fax
addresses. I don't have all the details but this was pointed out
and verified in KB article Q139465. I also forgot who pointed it
out to me, sorry.
----------------------------------------------------------------------
How do I share fax modems between Windows 95 machines?
Set aside one computer to share the fax modem, and see to it that it
runs Exchange all the time (By placing a shortcut to Inbox in its
Startup group).
Get Inbox Properties (Or your Exchange profile properties) and get
Microsoft Fax properties. Select the Modem tab, and select, "Let
me share my modem on the network". All the file sharing rules
apply, including User Level security if you enabled that, and you will
need a file sharing service installed on that computer. You can't
cheat and use a network drive on another server this time, unlike
WFWG FAX let you do; the system will use your C: drive and
create a FAX share on it.
Now, in the Modem tab on everyone else's fax properties, change
the modem type to "Network Fax". Give it the UNC or DOS path
to the shared directory on the fax server. Users can then send (but
not receive... awwww) faxes through the network. Someone will
still have to sit at the fax server to route and print faxes as
necessary. Routing faxes is a simple matter of forwarding the fax
attachment to E-MAIL addresses in the network.
How do I share fax modems between Windows 95 and
WFWG machines?
Win95 fax servers won't work with WFWG clients or vise-versa. I
know, sad. I vaugely remember MS releasing a patch to MS Fax to
let Win95's Fax client access WFWG fax servers, but I can't find
any reference to it on MS's web site anymore.
----------------------------------------------------------------------
Top ten Microsoft Fax annoyances
10) It can't do broadcast faxes (Yes it can; just feed it a bunch of
fax addresses in your personal address book and BCC: them as a
group)
9) It won't automatically print faxes (You like junk faxes wasting
your paper?)
8) It won't dial 1-(area code) for long distance within my area code
(Add that fax number to your personal address book, and turn on
"Dial area code, even though it's the same as mine")
7) It displays a dumb window when it sends a fax (Right-click on
the little Fax icon in the taskbar, then turn off "Display when active")
6) It gives me a junk mail message from SPRINT whenever I install
it (Big deal; delete it, it only happens once)
5) I can't use the modem when Exchange is running (Set answer
mode to "Off" in Fax properties/Modem; you can still send faxes,
but not automatically receive them. Still, auto-answer won't interfere
with other Win95 apps trying to use the modem; you can use
HyperTerminal at the same time, for example)
4) I can't print to the fax modem without changing my default printer
(That's a dumb MS Office 4.x bug; just use "Send..." instead, and
specify a fax address. Yes it does work.)
3) It processes faxes locally and wastes my processing time
2) It keeps trying to make E-MAIL format (Set the fax type to
"Not editable" in Fax Properties/Message)
1) It's cover page editor sucks (But it's functional, isn't it?)
----------------------------------------------------------------------
What about WinFax PRO (tm) for Win95?
Delrina (AKA: Symantec) getting the Designed for Win95 logo for
this program is a miracle.
They claim that WinFax 7.0 integrates with Exchange. Not. It tries
to completely REPLACE Exchange with its own interface (You can
send Exchange E-MAIL from WinFax), it has to launch all of
WinFax PRO if you select "New WinFax" from Exchange, you
can't share the modem on the network without paying big $$$ for
the Server version, it doesn't use TAPI by default (So it locks out
all other Win95 programs using the modem, unless you enable
TAPI through a scary-looking Advanced... button), it takes more
memory than MS Fax, it has ridiculous patches (7 MB) to fix its
bugs, it doesn't work in Windows NT, even though it bypasses the
stuff that exempted it from NT compatibility (TAPI, Exchange)...
Listen. Give up on WinFax and wait until they earn that Win95
logo. For about 99% of us faxing, MS Fax will do all we need to
do, and it's free.
----------------------------------------------------------------------
How do I send and receive MHS mail?
There aren't any Exchange clients for MHS (Futurus Team/Office
Logic) yet. I'm bugging Novell about it on occasion, but MS talks
about stop-gap measures, using MHS to MS-Mail gateways, for
example. No thanks.
Keep bugging people on Novell E-MAIL links, or talk to other
MHS vendors. Please, I want to see this work!
A rumor popped up from the makers of Office-Logic (I don't have
an address... sorry) that they'll have an MHS client for Exchange
sometime soon, but details are sketcy I'm afraid.
----------------------------------------------------------------------
How do I send and receive VIM (cc:Mail) mail?
There's a cc:Mail client for Exchange at
http://www.transendcorp.com under the title ConnectWare for
cc:Mail. They have a 30 day trial version available for download
and a commercial version. You also need updated VIM .DLL files,
which you can get from Lotus via ConnectWare's site. From what I
read about it, ConectWare for cc:Mail is a proper Exchange client,
with Remote Mail support.
----------------------------------------------------------------------
How do I send and receive Microsoft Network mail?
What? You use BillNet (tm)?
MSN Setup automatically adds an MSN mail client for Exchange,
and you can grab user lists off MSN directly, and store local
copies.
If you already have BillNet software installed, you will have a
"Microsoft Network Online Service" client you can add to your
Exchange profile. It grabs your user info from the rest of BillNet, so
there's no additional setup needed. This is pretty much the easiest
client to set up.
BillNet Mail lets you send to BillNet or Internet addresses, so when
you create address book entries and you use both BillNet and
Internet Mail, make sure you select the type of Internet Mail
address you want to use. Your least expensive bet is to always use
direct Internet Mail, rather than Internet Mail via BillNet, if you
have a choice.
----------------------------------------------------------------------
Remote Mail basics for MS Mail, Internet Mail, CIS Mail,
and Microsoft Network Mail users
If an Exchange client supports Remote Mail, it will allow you to
work interactively with your mail server. This means manually
logging in, hand-selecting the messages you want to move, copy, or
delete, and then transferring.
Normally, when you select "Deliver now using..." or if you set up
your client for a LAN or other continuous connection, it runs the
chosen service, logs in, moves all of your mail from the server to
your inbox, transmits anything in your outbox, then dis-connects.
This is quite blatant and quite efficient. Remote Mail however, in the
same Tools menu, lets you fully control mail delivery, provided you
enabled Remote Mail in your clients.
In MS-Mail, using Remote Mail depends on your connection type.
You can set different Remote Mail options for LAN and for
Dial-up networking sessions, so if it's on the LAN it'll work one
way, and if it's on a phone line it will work another. You will only
get a Remote Mail choice for MS-Mail if you enabled it for
whatever your current connection is. Slow machines will benefit if
you enable Remote Mail for LAN connections, as the mail checks
eat up processor time and load down the system.
Internet Mail only has one place for defining the Remote Mail
behavior: The Connection tab in Internet Mail properties. You
either enable Remote Mail, or disable it and check for mail every so
often (15 minutes by default). The latter works best if you have a
POP3 server right on your LAN, otherwise, keep Remote Mail
enabled. You can always do a Deliver Now if you want to do a
batch mail delivery.
CIS Mail always has Remote Mail enabled, but you can instruct it
to dial out and check every so often as well.
BillNet (tm) Remote Mail is also always enabled, and it will log you
in to BillNet when you perform a delivery, either using Remote
Mail, or Deliver Now.
----------------------------------------------------------------------
How can I keep mail on the server?
Enable Remote Mail for whatever client you're using. This will let
you view all the mail in your server by selecting "Update Headers",
and hand-select pieces of mail for copying, moving, or deleting.
Remote Mail always keeps a local copy of the mail list, so you
needn't be attached to the server to maintain your list. It will attach
to the server only if you tell it to, or if you perform any transfers,
and it will update the list whenever a transfer occurs.
----------------------------------------------------------------------
How can I keep a separate inbox or address book for each
user? (Exchange Profiles)
Say you send Internet Mail from work, but you want to use the
same copy of Exchange (and the same machine) for you home
E-MAIL too. You can't load multiple copies of Internet Mail in one
profile, but you can create a second (or third, or fourth) profile, add
Internet Mail to it, and use different settings. All Exchange user
settings go in the active Exchange profile.
To make a new profile, bring up Inbox properties and hit "Show
Profiles". Then select "Add". The Inbox Setup Wizard will run a
second time, prompting you for a new profile name, and prompting
you through all the setups of all installed mail clients. You can
enable or disable whatever mail clients you wish. Then, when you
get to the Personal Address Book and Personal Folders setup
screens, be sure to specify a unique filename for the address book
and mailbox, different from any previous profile. The wizard will
create new files for you if they don't alreadt exist. You CAN use
the same address book (.PAB) and mailbox file (.PST) in multiple
profiles, but why cause confusion? Then, in Tools/Options within
Exchange, enable "Prompt for a profile to be used". This way when
Exchange runs, you can choose the profile to run.
You need to exit and re-start Exchange to swap between profiles.
Be sure to allow it to completely exit (at least wait until the fax icon
disapears) so it logs off from the services in the first profile.
Profiles are cool for Exchange-enabled apps, because the apps will
store their user settings per-profile. Internet Idioms, for example,
can keep a unique signature for each profile. Schedule Plus for 95
also keeps unique schedule books and contact lists per profile. You
don't even need to have a mail client; a profile only needs the
Personal Folders and Address Book services.
Exchange stores profiles in the user portion of the Registry, so User
Profiles apply here as well. Each user can have their own set of
Exchange profiles, of if you don't want to be bothered with the
"Prompt for profile to be used" requester, use a single profile for
each user. This is especially useful of you have roving users that use
Schedule Plus for 95; if you keep the schedule and message files in
your home directory, all of the books will follow you around the
network. Now that's cool.
----------------------------------------------------------------------
Quick backgrounder on the Personal Address Book
If you want to make up that bulk mailing list or that broadcast fax,
here's where to do it.
Hit Tools/Address Book and hit the blank card button (or
File/New) to create an entry. The entries end up becoming a
contact database of sorts, complete with full addressing should you
choose to fill in all the blanks for each person. Then, when you send
letters, you can add names from this address book directly.
The most important entries to add to a new entry are the Name and
E-MAIL address. The name entry shows up as a "friendly" name,
but there are lots of spaces to fill in (like home mail address, work
mail address, home & work phone & fax numbers, etc).
The E-MAIL address actually has two components; the E-MAIL
type and the E-MAIL address. Examples of Exchange E-MAIL
addresses include [FAX:+1 (604) 555-1212] and
[SMTP:gordonf@vcn.bc.ca]. You specify the address type when
you create a new entry, so you don't need to memorize the bizzare
formats I gave examples for, though they do work in the TO: boxes
of letters.
One special type of address book entry is the "Personal Distribution
List", which is where you create groups of people to mail to. These
groups can contain any number of people from your address book,
even with different E-MAIL formats. To create a distribution list,
first create all the entries you want in it, then create a distribution list
and add the entries to it. When you send mail, use this distribution
list as the destination address.
MS Schedule Plus for 95 uses the address book for contact
management, so be sure to fill in all the blanks when making up
entries. This is actually another good reason to stick with Exchange;
when you do get MS Office you will already have a powerful
contact manager with a list of contacts ready to use. Other
Designed for Win95 apps will look for the address book for their
own purpose (like Word 7's cover letter wizard).
----------------------------------------------------------------------
Top ten mis-conceptions about Exchange
10) Exchange is a pig (OK so it's 4.2 MB, but that includes all the
interface, remote mail, and address book! I'd like to see you run
four mail programs and a fax program all at once in less than 4.2
MB)
9) It won't work with Win 3.1 Mail-enabled apps (Yes it does.
Apps call MAPI.DLL to send mail)
8) It requires Win95 networking to work (Not if all you're doing is
faxing or CIS mail)
7) It won't work with MS-Mail Remote (OK so it won't. But it
does work with dial-up networking and the regular MS-Mail
server, so use that instead)
6) It's a poor Internet Mail client (Grab Internet Idioms and stop
bitching)
5) It won't work with MS-Mail shared folders (Download the
Exchange Update to fix)
4) You need Exchange to run Schedule Plus for Win95 (Not. Only
for workgroup functions)
3) You need Exchange Server to use it (Not. Exchange Server is a
very different beast)
2) No one's writing clients for Exchange (well... Microsoft's writing
clients... heh heh... just keep bugging software vendors, and visit
Angry Greycat Designs)
1) It's only MS-Mail re-vamped (OK, but it's DRASTICALLY
re-vamped!)
----------------------------------------------------------------------
Exchange Wish List
MHS (Futurus Team, Office Logic, et al) client, with phone
messaging
IMAP4 client (With optional folder store on the mail server, a'la
MS-Mail)
Voice mail client (receive voice mail as .WAV attachments! Hints
of such a client are at the Exchange Buddy Site; Exchange Buddy is
another Internet formatter for Exchange, like Idioms)
Nicer Internet Idioms installer (Ever consider InstallShield32, Ben?)
FidoNet point client (Store echos as external folders a'la MS-Mail,
send and receive echomail)
Quicker fax manipulation (Actually it's not bad, but I'd dump the
E-MAIL format option for more speed; set the format to "Not
Editable")
Exit QUICKER! For some reason, an Exchange component
(MAPISP32) stays resident for up to 30 seconds after exit!
----------------------------------------------------------------------
[Back to Table of Contents]
--
============================================================// //========
= "I am Gordon of Winterpeg. Windows WAS futile." // // =
= Find out why: http://www.intouch.bc.ca/win95 // // =
= Personal E-MAIL: gordonf@vcn.bc.ca \\ \\// // =
= Home Phone: +1-604-526-8724 \\ XX // =
= \X/\X/ =
= "I am Hitler of BorgSoft. I am the middle inital of William H. Gates. =
= Your work will be Microsofted. Resistance is futile. Heil Windows. =
=========================================================================
Yeah I use an Amiga at home. If you don't like my computer, dial
1-800-DIE-BILL and tell someone who cares.
----------------------------------------------------------------------
Path: news1.ucsd.edu!ihnp4.ucsd.edu!swrinde!newsfeed.internetmci.com!news.mathworks.com!nntp.primenet.com!news.cais.net!van-bc!unixg.ubc.ca!freenet.vancouver.bc.ca!gordonf
From: gordonf@vcn.bc.ca (Gordon Fecyk)
Newsgroups: comp.os.ms-windows.win95.misc,comp.os.ms-windows.setup.win95,comp.os.ms-windows.networking.win95,comp.os.ms-windows.apps.compatibility.win95,comp.answers,news.answers
Subject: Win95 FAQs and Answers Part 11 of 14: Disk Compression
Followup-To: comp.os.ms-windows.win95.misc,comp.os.ms-windows.setup.win95,comp.os.ms-windows.networking.win95,comp.os.ms-windows.apps.compatibility.win95
Date: 30 Jun 1996 16:35:26 GMT
Organization: Vancouver Regional FreeNet
Lines: 438
Approved: news-answers-request@MIT.EDU
Message-ID: <4r6ace$80p@milo.vcn.bc.ca>
NNTP-Posting-Host: opus.vcn.bc.ca
Summary: These postings list many questions asked in said newsgroups,
and answers them as best as I can. I make references to other
Web sites and FAQs when appropriate. Visit the WWW home of
this FAQ (http://www.intouch.bc.ca/win95) for the appropriate
links. This section is the 11th: Disk Compression
X-Newsreader: TIN [version 1.2 PL2]
Xref: news1.ucsd.edu comp.os.ms-windows.win95.misc:111607 comp.os.ms-windows.setup.win95:10984 comp.os.ms-windows.networking.win95:7518 comp.os.ms-windows.apps.compatibility.win95:3583 comp.answers:15522 news.answers:61923
Archive-name: windows/win95/faq/part11
Last-Modified: 1996/07/01
Posting-Frequency: Every two months
URL: http://www.intouch.bc.ca/win95/faq11.htm
11) Disk compression and you
Why should I bother? (Actually it's not as dumb as you might
think)
I heard that using disk compression is helpful on drives > 1 GB.
Is this true? (yes.)
How do I compress my whole hard drive? (Avoid if possible!)
How do I compress a part of my hard drive?
How to make a compressed volume, and keep your Win95
installation OFF it
How do I compress floppy disks?
Enabling "Auto-mount" for removable compressed disks
The DriveSpace driver takes 60 KB and I can't load it high!
How do I do it?
The DriveSpace 3 driver takes 100 KB and I can't load it high!
How do I do it?
How do I start my computer WITHOUT loading the
DriveSpace driver?
Why you should run DOS programs in DOS sessions in
Win95
How do I load the Win95 DriveSpace driver, but NOT load
the DOS DriveSpace driver?
My computer is very, very, slow since I installed disk
compression. How can I speed it up?
Basic DriveSpace 3 theory; regular, HiPack, UltraPack,
Compression Agent
Why on slow computers, you should use "No compression"
and still use DriveSpace 3
Top ten mistakes using disk compression
Top ten mis-conceptions regarding DriveSpace 3
----------------------------------------------------------------------
Why should I bother? (Actually it's not as dumb as you might
think)
With hard drives getting cheaper every day, you will believe (and I
do too) that disk compression is a waste of processor time, a waste
of system memory, and it makes the system unstable. But, here are
some good reasons to use disk compression:
On FAT file systems, it wastes far less disk space (Cluster sizes are
minimum 512 bytes regardless of the partition's 'reported' cluster
size)
It reduces the amount of CPU time spent on the hard drive (It reads
less off hardware)
It makes good use of smaller hard drives
Win95's disk compression take NO conventional memory (At
least, when you run Win95 that is)
----------------------------------------------------------------------
I heard that using disk compression is helpful on drives > 1
GB. Is this true?
DriveSpace 3, in particular, is helpful for drives > 1 GB, if you set
compression to "none". This is because DriveSpace will use a
smaller physical cluster size.
Normally, FAT file systems have a 65 thousand cluster limit (64 K,
or 65 535 clusters); this means as the drive gets bigger, the cluster
size gets bigger too. On a 1 GB hard drive, the cluster size is 32
KB! That's a lot of disk space wasted if your file is much smaller
than 32 KB!
DriveSpace (and Stacker, and what-have-you) use their own file
system and emulate FAT, and they can compress the unused space
in a cluster. DriveSpace 3, in particular, will use no more than 512
bytes per simulated cluster, if your file is smaller than this.
You can observe this by running DEFRAG on a compressed drive
in Win95; after the inital defrag pass, it will de-fragment a second
time, showing the relative sizes of each cluster. Tightly compressed
clusters will appear shorter.
----------------------------------------------------------------------
How do I compress my whole hard drive?
I say Avoid If Possible. If you have to re-install Win95, you might
not be able to read the compressed drive to perform the
re-installation on!
However, it can be done. You will have to have Disk Compression
installed in Win95; check Add/Remove Programs/Windows
Setup/Disk Tools. Then, right-click on your target hard drive and
bring up its properties. You should see a Compression tab which
gives you two options. Select the option to compress the whole
hard drive.
This built in compression (Affectionately called "DriveSpace 2") will
re-boot your computer and run a compression process in a
"miniature" Windows 3.1 environment. This means you can't use
your computer while this happens. This does take a long time, so
you should get it started and let it run overnight. When completed,
you will have two active drive letters, or volumes; your original hard
drive (Re-named to "H:" or some such thing) and your new
compressed hard drive (Renamed "C:" to replace your original hard
drive).
----------------------------------------------------------------------
How do I compress a part of my hard drive?
OK so you heeded my warning. Good. You have to install Disk
Compression if you didn't already do so. Before running
DriveSpace, de-fragment the hard drive you're placing the
compressed volume on. This will maximize the space the
compressed volume can take.
Then, bring up properties of the target hard drive. In the
Compression tab, select the option to create a new compressed
volume. This will run DriveSpace, create the new .CVF file, and tell
you to re-boot your computer. Much quicker.
If you plan to use DriveSpace this way, you should do so right after
you complete your Win95 installation, and create a compressed
volume with all the remaining space. This will maximize the drive
space that gets compressed, and keep your Win95 installation
un-compressed, ready to re-install if necessary. Maybe leave about
100 MB un-compressed for the Program Files folder, which always
goes on your booting drive.
----------------------------------------------------------------------
How do I compress floppy disks?
Bring up properties for your floppy drive, and select the
"Compression" tab. You only have one compression option here;
you can't put a separate CVF on a floppy disk. The rest of it works
like compressing your whole hard drive.
It's best to do this with blank disks; otherwise you will waste time
compressing the files already on the floppy. Use this technique for
any other removable media; optical disks, SyQuest disks,
whatever.
----------------------------------------------------------------------
Enabling "Auto-mount" for removable compressed disks
Back in DOS 6.0, you had to manually mount compressed floppies,
and un-mount them before ejecting them. Win95 will automatically
mount compressed floppies if you allow it to.
Run DriveSpace, then in Advanced/Settings, turn on the
Auto-Mount switch. This is normally turned on by default. The first
time you access the removable disk, if it sees a DRVSPACE.xxx
file, it will use that instead of the actual disk.
No, you can't copy .CAB files to compressed floppies; the files in a
CAB are already compressed.
----------------------------------------------------------------------
The DriveSpace driver takes 60 KB and I can't load it high!
How do I do it?
In order for Win95 to actually start, Win95 DOS has to see any
compressed drives you might have installed Win95 on. There is a
real mode DriveSpace driver (and a real-mode DRVSPACE.INI
settings file) in the root of your boot drive, though they're hidden.
If you have an empty CONFIG.SYS file (which you should), when
Win95 starts it will remove the real mode DRVSPACE.SYS driver
and run the protected mode driver in its place, freeing up the 60
KB.
If you insist on keeping a DOS configuration (Or if you specified a
special DOS config for any of your games), you can continue to use
DEVICEHIGH=%WINDIR%\COMMAND\DRVSPACE.SYS /MOVE
to re-locate the real mode driver to upper memory.
----------------------------------------------------------------------
The DriveSpace 3 driver takes 100 KB and I can't load it
high! How do I do it?
Ahh... monster driver! This thing is so big because it needs to have
compression routines for the three types of compression:
UltraPack, HiPack, and Standard.
If you have enough upper memory, make the DRVSPACE.SYS
/MOVE entry in CONFIG.SYS the very next DEVICE= right after
EMM386. This will eat 100 KB of upper memory of course, and
the rest of your real mode drivers probably won't fit in upper
memory afterwards.
Win95 will un-load this monster driver from conventional memory
when you run Win95, provided you didn't try to load it high. Do
yourself a favor and run your DOS programs in DOS sessions.
----------------------------------------------------------------------
How do I start my computer WITHOUT loading the
DriveSpace driver?
Edit MSDOS.SYS and add or edit these lines to the [options]
section:
drvspace=0
dblspace=0
and re-boot.
NOTE: If you do this, you can't access compressed drives from
DOS of course, but you also can't access them in Win95 either!
This is an important reason not to compreess your whole hard
drive.
----------------------------------------------------------------------
How do I load the Win95 DriveSpace driver, but NOT load
the DOS DriveSpace driver?
Actually, there IS a way NOT to load the DriveSpace driver in
MS-DOS Mode, AND use the compressed drive in Win95! You'll
find this trick useful if you run many programs in Single Mode DOS
or make up special DOS configurations for certain programs and
games, as it saves a good 60 KB to 100 KB of conventional
memory, and still lets you use the compressed drive under Win95
and in DOS sessions.
This is a bit tricky, so only do it if you know what you're doing,
AND you aren't picky about what drive letter the compressed drive
takes, AND you didn't install Win95 on the compressed drive,
AND you don't assign any network shares on the compressed drive
(You'd have to re-share them each time you re-boot if you did this.)
1) Put in the entries to MSDOS.SYS above
2) Run Policy Editor, Select File/Open Registry, and in Local
Computer/System/Run Services, add this entry:
Name: Mount DriveSpace Drive (Actually call this what you want)
Value: DRVSPACE.EXE /MOUNT=001 C:
3) Save changes to the Registry, and test by re-booting to
"Command Prompt Only" (Press F8 on "Starting Windows 95...").
Check that you have lots of conventional memory free.
4) Type WIN to start Win95. Before any other programs load, you
should get some floppy access and a message stating that your
compressed drive has mounted.
5) Now you can re-boot normally, once you're sure everything
works.
What this does, is prevent the real mode DriveSpace driver from
loading at all. Again, this means you can't access compressed drives
outside of Win95. It also mounts the compressed drive, using
protected mode drivers, before any other Win95 programs start
(Run Services runs its programs before anything else does). You
will get an annoying message on start up, but you had to pay the
price somewhere for this cool trickery, no?
Syntax of DRVSPACE.EXE /MOUNT command:
DRVSPACE /MOUNT=xxx y: /NEW=z:
Where "xxx" is the number of the compressed volume (Find out by
showing all files and looking for a DRVSPACE.001 file; the 001 is
the number you put in the MOUNT= parameter). "y:" is the drive
letter where the compressed volume exists. "z:" is the drive letter
you assign the new compressed drive in the /NEW= parameter.
NOTE: /NEW= does not always pick the drive letter you want,
especially if you have network drives. It's best to leave out the
/NEW= and just live with the drive letter it comes up with. You can
specify a range of drive letters in the DRVSPACE.INI file, if you
choose, to make the assignment consistent. Once it settles on a
drive letter it will consistently use it, until you remove the
compressed drive or re-assign the drive letter.
----------------------------------------------------------------------
My computer is very, very, slow since I installed disk
compression. How can I speed it up?
DriveSpace works best in Win95 if you have lots of RAM (16
MB), have lots of extra computing power ('DX2-66es are quite
adequate for this), and some external SRAM for processor caching
(256 KB is best). The CPU has to work harder to interpret
compressed data, but it has to wait less time to actually get it. This
is the trade-off.
To speed compressed drives up, install DriveSpace 3 (in MS
Plus!), and set compression to "none", or "none, unless it is xx%
full, then use Standard". You still get the benefits of reduced cluster
sizes even though you aren't compressing data. Later on, you can
use Compression Agent to compress the drive overnight, or any
other time you aren't using the computer.
If you use DriveSpace 3 on a '486 class computer, do not use
HiPack as the default file format, as MS recommends. Maybe even
set compression to "None" and use Compression Agent to
re-compress overnight, using HiPack then. HiPack takes less time
to read than to write. Also, when using Compression Agent, DO
NOT USE UltraPack! UltraPack is very, very, slow on '486
machines. I wouldn't even recommend it for Pentium machines
slower than 100 MHz.
If you're too cheap to buy MS Plus, simply make sure your swap
file isn't on the compressed drive, and it's set to a fixed size. Do this
from System Properties/Performance/Virtual Memory. Win95
doesn't actually compress the swap file, but it does go through the
DriveSpace driver to access it. Move it to an uncompressed drive
to remove that extra layer of protocol.
Finally, make sure you have NO real mode disk drivers to handle
CD-ROMs, etc, that might be sitting on the hard drive adapters.
The Win95 disk driver can't load then, and it won't use the Win95
DriveSpace driver either.
----------------------------------------------------------------------
Basic DriveSpace 3 advice; regular, HiPack, UltraPack,
Compression Agent
DriveSpace 3 makes more drive space by compressing files tighter.
It does so using Compression Agent, which gets automatically
scheduled in System Agent when you install MS Plus.
Run DriveSpace 3, select the compressed drive, then select
Advanced/Settings. This selects how DriveSpace writes data to the
compressed drive on the fly. As MS recommends, don't use
HiPack on '486 class computers. I won't even use it on
Pentium-75s. "Standard" is best for all '486 machines or better,
though a slow '486 can benefit from the "None until..." setting. Use
"None" on all '386 class machines.
Now, DriveSpace 3 can un-compress data faster than it can
compress it, so it makes sense to try to re-compress the drive
during idle moments, like overnight. Compression Agent does this.
Either in System Agent, or in Accessories/System Tools, run
Compression Agent and hit its Settings button. For Pentiums faster
than 100 MHz, you could try UltraPack, but I doubt you'll get a
whole lot of extra disk space from it. All '486 systems can benefit
by completely turning off UltraPack and specifying HiPack for the
rest of the files (basically meaning "All of them".) Generally, reading
back HiPacked files is quick, so you can specify that for even '386
class machines, but if you really can't handle the decrease in speed,
use "Store them un-compressed".
A re-compression run does take a LONG time, so do it overnight.
Use System Agent to schedule re-compression, say, once a month,
and schedule a thorough disk scan about an hour before
Compression Agent runs.
----------------------------------------------------------------------
Why on slow computers, you should use "No compression"
and still use DriveSpace 3
It handles bigger hard drives (compressed volumes larger than 512
MB)
It reduces wasted disk space (for files smaller than 512 bytes, it
only occupies 512 bytes, regardless of logical cluster size)
It won't eat CPU time if you turn compression off
----------------------------------------------------------------------
Top ten mistakes using disk compression
10) Running your DOS games outside of Win95 (Not enough
memory)
9) Deleting the DRVSPACE.001 file (Fortunately, Win95 has a
safety mechanism for that!)
8) Deleting the DRVSPACE.BIN file
7) Using an old DOS compression program (Sorry Stac
Electronics... you lose here)
6) Using a DOS driver for your IDE CD-ROM and DriveSpace
(Get Win95 drivers for the IDE port and it'll find the CD-ROM)
5) Not using ScanDisk regularly (Use System Agent to do
automatic disk scans)
4) Setting your estimated compression ratio higher than your real
one (Then installing a big game...)
3) Using UltraPack on a '386 computer
2) Using Norton Disk Doctor for Win95 on DriveSpace 3 drives
(ScanDisk is more reliable... Symantec released _two patch sets_
to fix Norton Utilities)
1) Compressing your whole hard drive
----------------------------------------------------------------------
Top ten mis-conceptions regarding DriveSpace 3 from MS
Plus
10) Norton Utilities for Win95 works on it (Sorry... it reported
false errors on mine!)
9) It's faster than "DriveSpace 2" (At least not at first...)
8) I need a Pentium-133 to use it (Just don't use UltraPack)
7) It eats more conventional memory (Actually, it eats NONE
under Win95, if set up properly)
6) I can compress my whole drive with it (Yeah... then try
re-installing Win95)
5) It's useless on '386 machines
4) It makes my computer un-stable (use System Agent to schedule
disk scans)
3) A virus can wipe out the system (A nasty virus could wipe out
the system, compressed or not)
2) MS deliberately crippled Win95's built-in DriveSpace to make
us buy MS Plus
1) It's the best compression program for Win95 (Actually, it's the
ONLY one... heh heh)
----------------------------------------------------------------------
[Back to Table of Contents]
--
============================================================// //========
= "I am Gordon of Winterpeg. Windows WAS futile." // // =
= Find out why: http://www.intouch.bc.ca/win95 // // =
= Personal E-MAIL: gordonf@vcn.bc.ca \\ \\// // =
= Home Phone: +1-604-526-8724 \\ XX // =
= \X/\X/ =
= "I am Hitler of BorgSoft. I am the middle inital of William H. Gates. =
= Your work will be Microsofted. Resistance is futile. Heil Windows. =
=========================================================================
Yeah I use an Amiga at home. If you don't like my computer, dial
1-800-DIE-BILL and tell someone who cares.
----------------------------------------------------------------------
Path: news1.ucsd.edu!ihnp4.ucsd.edu!swrinde!newsfeed.internetmci.com!news.mathworks.com!nntp.primenet.com!news.cais.net!van-bc!unixg.ubc.ca!freenet.vancouver.bc.ca!gordonf
From: gordonf@vcn.bc.ca (Gordon Fecyk)
Newsgroups: comp.os.ms-windows.win95.misc,comp.os.ms-windows.setup.win95,comp.os.ms-windows.networking.win95,comp.os.ms-windows.apps.compatibility.win95,comp.answers,news.answers
Subject: Win95 FAQs and Answers Part 12 of 14: Running MS-DOS Games
Followup-To: comp.os.ms-windows.win95.misc,comp.os.ms-windows.setup.win95,comp.os.ms-windows.networking.win95,comp.os.ms-windows.apps.compatibility.win95
Date: 30 Jun 1996 16:35:58 GMT
Organization: Vancouver Regional FreeNet
Lines: 428
Approved: news-answers-request@MIT.EDU
Message-ID: <4r6ade$80p@milo.vcn.bc.ca>
NNTP-Posting-Host: opus.vcn.bc.ca
Summary: These postings list many questions asked in said newsgroups,
and answers them as best as I can. I make references to other
Web sites and FAQs when appropriate. Visit the WWW home of
this FAQ (http://www.intouch.bc.ca/win95) for the appropriate
links. This section is the 12th: Running MS-DOS Games
The info here can apply to running non-game DOS apps as well.
X-Newsreader: TIN [version 1.2 PL2]
Xref: news1.ucsd.edu comp.os.ms-windows.win95.misc:111608 comp.os.ms-windows.setup.win95:10985 comp.os.ms-windows.networking.win95:7519 comp.os.ms-windows.apps.compatibility.win95:3584 comp.answers:15523 news.answers:61924
Archive-name: windows/win95/faq/part12
Last-Modified: 1996/07/01
Posting-Frequency: Every two months
URL: http://www.intouch.bc.ca/win95/faq12.htm
12) Running MS-DOS games
Why you should run your DOS games in DOS sessions under
Windows 95
Quick lesson on PIF files
How do I use upper memory in Windows 95?
Why you should run your DOS games in DOS sessions
under Windows 95
How do I use EMS memory?
How do I use XMS memory?
How do I use DPMI memory and DPMI programs?
How do I speed up this DOS game?
Why do DOS programs "stutter" in a DOS session?
Why shouldn't I use EMM386 (or other memory manager)?
Why you should run your DOS games in DOS sessions
under Windows 95
How do I set up network games?
How to set up your network card
Why you should run your DOS games in DOS sessions
under Windows 95
Why do you keep telling me to run my games under Win95?
Why you should run your DOS games in DOS sessions
under Windows 95
But this game won't run under Win95! How can I get it to
work?
How you can do away with "boot disks" forever!
How to make network games work without running Win95
----------------------------------------------------------------------
Why you should run your DOS games in DOS sessions under
Windows 95
The big speech... here it comes. Skip it if you don't want to read
about it.
Win95 does all of its hardware control, its network control, its
drivers, its protocols, whatever, in '386 protected mode, so none of
its software really needs to run in conventional memory, or in upper
memory. You get minimum 604 KB free conventional memory, no
matter what hardware or drivers for Win95 you have loaded.
In addition to this, all of the MS-DOS software interrupts,
hardware interrupts, function hooks, etc operate in protected mode
also. This means that DOS programs can still work, even though
there aren't any DOS drivers handling the hooks. Win95 only
provides a basic real mode driver set for basic compatibility
(HIMEM, SETVER, IFSHLP, COMMAND); everything else runs
outside of the DOS session. The protected mode hooks are
re-entrant, so multiple DOS sessions can use them. They are also
faster in many cases; CD-ROM performance greatly improves, for
example.
Win95 will also virtualize I/O spaces, if you enable that feature in a
DOS program's properties. This is similar to what Windows NT
does, but not as robust. This will prevent the programs from
accessing the hardware directly. If a "protected" DOS program
crashes, it won't take the rest of the system with it. "Protection" will,
however, add to the CPU overhead and may cause a program not
to run at all, which is why it's an option.
NOTE: Don't confuse this direct hardware access with the
DirectX API; DirectX programs run in protected Win32
sessions by design, and access the hardware through an
absolute minimal API. DirectX has nothing to do with DOS
programs accessing hardware directly.
So, with all this benefit, and not eating any conventional memory
and still providing a nice compatible DOS box, you should run your
DOS games in DOS sessions in Win95.
So, hide or delete your CONFIG.SYS, remove all TSRs in
AUTOEXEC.BAT, get Win95 drivers for all your hardware, and
read on.
----------------------------------------------------------------------
Quick lesson on PIF files
You can maximize a game's performance in a DOS session by fine
tuning its session settings. Right-click on the executable that runs the
game (batch file, COM file, EXE file, whatever), and select
Properties. Hit the "Program" tab and, if necessary, change the
command line used to run the game. Insert any parameters it needs,
change the working directory, whatever. Hit the "Advanced" button
and quickly see the "Prevent MS-DOS programs from detecting
Windows" switch. If a game claims it can't run under Windows, turn
on this switch. Now the game will think it's running in DOS. Hah,
sucker! Ignore the rest of this window for now; hopefully we won't
have to resort to the rest of the stuff here.
Have a look at the other tabs; I'll cover them each in turn with each
question.
Win95 will save the changes you make here in a PIF file, or a
"Shortcut to MS-DOS Program". Whenever you bring up
properties for the program, it will bring up its PIF file.
----------------------------------------------------------------------
How do I use upper memory in Windows 95?
There's no such thing as "upper memory" under Win95, and no
need to worry about it either, if you have Win95 drivers for all your
stuff and run your games under Win95.
I cover how to use upper memory in Single Mode MS-DOS later.
----------------------------------------------------------------------
How do I use EMS or XMS memory?
In the program's properties, hit the Memory tab. You'll notice the
defaults for these settings is "Auto"; this means Win95 will allocate
memory as needed for this program to run. This can cause a lot of
extra disk swapping, so you should find out what the game needs
(Check its manual) and set the EMS and XMS values to match.
Example 1: TIE Fighter (tm) by LucasArts: TIE requires 2048 KB
of EMS memory (Expanded memory), so set the EMS value to
2048 KB, and set XMS to None.
Example 2: The Seventh Guest (tm) by Virgin/Trilobyte: T7G needs
4096 KB of XMS memory (Extended memory), so set its XMS
setting to 4096 and its EMS setting to None.
Example 3: DOOM (tm) by id Software: DOOM doesn't use EMS
or XMS memory, so set both of these values to None. Leave the
DPMI (DOS protected mode interface) memory on Auto, or if you
wish, fix it to 8 MB or 16 MB, if you feel it will improve its
performance.
Notice that all games use one kind of extra memory or another, but
not two at once. You can always set one and turn the other off.
This will ease Win95's job of guessing what the game needs. Of
course, if a game runs completely in conventional memory, turn off
everything BUT conventional memory.
Oh yeah, that "Protected" switch is in here; turn it on if you think
this program causes Win95 to crash.
----------------------------------------------------------------------
How do I use DPMI memory and DPMI programs?
If a program doesn't claim to use XMS or EMS memory, chances
are it's a protected mode program. DOOM by id and Descent (tm)
by InterPlay are two such programs.
In this program's Memory tab, turn off EMS and XMS memory,
and set DPMI to whatever the game requres, or leave it on Auto.
Auto mode will make Win95 allocate more RAM to the game as
needed, but it will cause extra disk swapping. Set this to the game's
recommended value, no higher than your total memory actually
installed in the computer.
If the game does its own disk swapping (like Descent does), fix the
DPMI memory value to the game's recommended value and don't
use Auto. There's no point in having Win95 and the game do
swapping at the same time.
Some DPMI games do bizzare stuff and may crash Win95 the first
time running. If so, turn on the "Protected" switch just below the
conventional memory setting. This will virtualize most of the I/O
space in that game's DOS session. Turning on "Prevent DOS
programs from detecting Windows" might help too. If the game
does hardware detection, try by-passing it and specifying your
video and sound card properties in the game manually. Descent has
troubles detecting sound cards in a DOS session, for example.
----------------------------------------------------------------------
How do I speed up this DOS game?
The first time you try running a "standard" DOS game, it will try to
run in a window on your desktop. Type ALT-ENTER to switch it
to a full screen.
To fix that setting in place, bring up the program's properties, hit the
Screen tab, and set the screen usage to Full Screen. There are
other screen controls here:
"Fast ROM Emulation" works if the video driver emulates its BIOS
in protected mode. All of Microsoft's video drivers do this. Keep
this turned on if the game works properly. Try turning it off if you
can't get VESA games working, though a properly written Win95
video driver should emulate VESA video modes in protected
mode.
"Dynamic memory allocation" specifies that Win95 will grab system
memory as needed to update the game's display. Try turning this off
if the display jitters, or the hard drive goes crazy as the display
updates itself.
----------------------------------------------------------------------
Why do DOS programs "stutter" in a DOS session?
DOOM will freeze on occasion, precisely four times, then continue
on normally.
This is probably Win95 trying to maintain system memory for the
display. Turn off "Dynamic memory allocation" in the Screen tab to
fix this. Maybe also turn off "Fast ROM Emulation".
If the video card requires a VESA TSR and you turned off Fast
ROM Emulation, you can load its real mode VESA driver in its
particular DOS session, by including it in the "Batch File" section of
the Program tab; hit the Program tab, and in the Batch File text
box, put in the full path to your VESA TSR.. This way, it only loads
into one session and not all DOS sessions. You're probably better
off trading that video card for one that has VESA support built into
its BIOS and its Win95 driver.
This problem only seems to happen with DPMI games; particularly
those that use the DOS4GW extender.
----------------------------------------------------------------------
Why shouldn't I use EMM386 (or other memory manager)?
A real mode memory manager will interfere with Win95's protected
mode memory management. If you include NOEMS in
CONFIG.SYS, for example, no program in a DOS session can
access EMS memory. Delete or hide your CONFIG.SYS and let
Win95 provide EMS memory in DOS sessions.
For those of you who paid money for Quarterdeck's QEMM 8.0:
SUCKERS! Take it back and get your money back!
----------------------------------------------------------------------
How do I set up network games?
Most of the net games use IPX protocol to communicate between
several game computers on the network. Microsoft's "IPX/SPX
Compatible" protocol works with these games.
First, install your network card and load a Win95 driver for it. Then
add IPX/SPX Protocol. If all you're doing is playing network
games you can remove all other network components, such as
Clients. If necessary, read up on How to set up a network card.
Then run the game in its DOS session and set it up to use the
network. It should find the hooks needed to use IPX and play
normally, as though you loaded an IPX.COM driver. If not,
complain to the game maker. They screwed it up.
A handful of old network games use NetBIOS to work with more
networks. In this case you can use any network protocol, such as
NetBEUI, to link the machines together. All the real mode
NetBIOS hooks are there as well. To use both IPX and NetBIOS
games, use the IPX/SPX protocol and turn on "I want to run
NetBIOS over IPX" in IPX/SPX Properties.
Modem games work by using the COM devices from DOS, so you
don't need to use Dial-up Networking just to play a game over the
modem. If, however, the game doesn't support modeming but
DOES support IPX networking, you could try using IPX over the
dial-up adapter, and rig one computer as a dial-up server. This is a
bit extreme, as IPX over PPP is quite slow.
----------------------------------------------------------------------
Why do you keep telling me to run my games under Win95?
I thought I answered this question at the top of this section! So you
can save yourself the hassles of multi-config, loading crap high,
running out of conventional memory, boot disks, whatever!
Win95 can do DOS's jobs a lot quicker and with a lot less
overhead. Yes, everything works. Yes, CD-ROM drives work.
Yes, network cards work. Yes, you can do EMS/XMS/DPMI.
Yes, sound cards work. Get a sound card that has Win95 drivers
for it. Yes, visit Advanced Gravis for a Win95 driver. Or just trade
your hardware in for hardware with Win95 support.
----------------------------------------------------------------------
But this game won't run under Win95! How can I get it to
work?
OK ok ok ok... so you can't live without playing this game (Star
Trek: A Final Unity (tm) by Spectrum Holobyte falls into this
category) and you can't run it in a DOS session. Or maybe you can;
bring up the program's properties, hit the Program tab, hit
"Advanced", and hit "Prevent DOS programs from detecting
Windows". This'll make the "smarty" programs run in a DOS
session.
If that didn't work, read on.
Here's how you make a special DOS setup for this program that
won't run in Win95:
Bring up properties for its start-up program again, and hit the
Program tab.
Hit Advanced, and turn on MS-DOS mode. This will make
Win95 exit before running the game. And since all the Win95
CD-ROM, netcard, etc drivers will unload at this point:
Hit "Specify a new MS-DOS Configuration". This will activate
the two text boxes below, so you can feed a special
CONFIG.SYS and AUTOEXEC.BAT for this program.
Fill in the empty spaces for CONFIG.SYS and
AUTOEXEC.BAT. All your normal DOS drivers, memory
managers, and TSRs should go in here. You can also copy from
your CONFIG.DOS, and press CTRL-V (Paste) to copy it
here; that does work. Be sure you use Win95 versions of
HIMEM and EMM386, and other DOS version-specific
drivers.
Save your changes and run the program. You should get a
warning that you're about to enter MS-DOS mode. If you OK
it, Win95 will re-boot your computer and run your special
CONFIG.SYS and AUTOEXEC.BAT. When you exit the
game, the system will re-boot into Win95 using the original DOS
configuration (which should be empty!)
With this setup, you can specify a DOS configuration just for this
program without polluting your Win95 configuration. You will have
to load all the real mode components necessary to make your
hardware work, including real mode sound card and CD-ROM
drivers. Net cards I'll cover later.
Some useful stuff to include in these files are:
HIMEM.SYS and EMM386.EXE: Yes, definitely include that
in the special CONFIG.SYS you make. Use the Win95
versions.
SMARTDRV.EXE: You should have real mode disk caching
here. Again, Win95 comes with its own version of SmartDrive.
PAUSE: Put this at the end of the special AUTOEXEC.BAT so
you can prevent your game from starting right away. You can
always press CTRL-C here and fine-tune the CONFIG.SYS
and AUTOEXEC.BAT, and re-boot to try again. When Win95
finally re-starts, it will copy your changes to the program's
properties. Now that's cool.
LOCK C: If you want to run Windows 3.1 this way (Yes it is
possible) and you want 32-bit disk/file access, include this
command. LOCK will allow direct disk writes by DOS
programs, including Win 3.1's memory manager and
FASTDISK drivers. Some DOS games that do disk swapping
may also require this command. Use this with caution; it also
allows viruses to do their dirty work.
MSCDEX.EXE: If you use a real mode CD-ROM driver, you
obviously need MSCDEX to mount it and run it. Load
MSCDEX before SmartDrive, so SmartDrive can cache
CD-ROM reads. Save on conventional memory this way by
specifying /M:4 (minimal buffer size). Win95 keeps this file in
%WINDIR%\COMMAND.
MOUSE.EXE or MOUSE.COM: A must for mouse driven
games.
Keep in mind, that "MS-DOS Mode", or "Single Mode MS-DOS"
is MS-DOS through and through, except for the LOCK and the
direct disk access inhibitor. You can use all the MS-DOS memory
management techniques you learned back in DOS 5.0. You might
also want to disable the DriveSpace Driver if you use disk
compression, and you can't get enough conventional memory. You
could also try running MEMMAKER, if you're really desparate, in
this configuration; add the old DOS utilities from
DRIVERS\OLDMSDOS, then while you're in a special DOS
configuration, run MEMMAKER. As long as you keep Win95
booting in this mode (where it says "Win95 is now starting your
MS-DOS based program..."); the changes that MEMMAKER
makes will only affect this particular configuration; it won't affect
your normal Win95 configuration.
This above technique replaces boot disks and Multi-Boot entirely!
If you use PIF files that specify MS-DOS mode, you can throw
away all your boot disks and your multi-boot CONFIG.SYS file.
You can even set up multiple PIFs for the same program; re-name
the PIF file that the Properties sheet made up, and bring up
Properties for the program again; it will build a new PIF file.
Another cool trick is to look for an "Exit to DOS" file in your
Win95 directory, bring up its properties, and set it up to use a new
MS-DOS configuration. This way, whenever you "Restart
computer in MS-DOS mode", you will run this configuration. Real
handy for running a bunch of games without having to make a
special configuration for each. In this mode, type EXIT or WIN to
return to Win95. You can also edit the custom startup files within
DOS mode; when Win95 finally re-starts, it will update the .PIF file
with the changes you made.
----------------------------------------------------------------------
How to make network games work without running Win95
Network Setup not only installs protected mode drivers for your
card; it also installs NDIS 2.0 real mode components specifically
for MS-DOS mode. You will need to install a Win95 net card
driver and IPX/SPX Protocol for this to work.
In the special AUTOEXEC.BAT you make for MS-DOS mode
games, include:
NET START NWLINK
This will load a real mode protocol manager, net card driver, and
Microsoft's IPX compatible protocol. You can go a step further
and type NET START NWREDIR to load a NETX compatible
client for NetWare, if you need to get to your games stored on the
NetWare server, and you installed Microsoft's Client for NetWare.
These components will try to load high if you have upper memory
available. Put this at the start of the special AUTOEXEC.BAT, to
improve upper memory usage.
WARNING: NET START does not always work, because some
NDIS 2 drivers look in SYSTEM.INI and PROTOCOL.INI, and
all of those settings moved to the Registry. Inspect Win95's
PROTOCOL.INI and compare it to the examples that come with
the net card's NDIS driver, or try to get updated Win95 drivers for
the card, which should include the Protected mode (NDIS 3.1) and
Real mode (NDIS 2.0) drivers. If NET START does not work,
you can always load Novell's drivers and clients from MS-DOS
mode, or from that program's special AUTOEXEC.BAT, instead
of using NET START.
----------------------------------------------------------------------
[Back to Table of Contents]
--
============================================================// //========
= "I am Gordon of Winterpeg. Windows WAS futile." // // =
= Find out why: http://www.intouch.bc.ca/win95 // // =
= Personal E-MAIL: gordonf@vcn.bc.ca \\ \\// // =
= Home Phone: +1-604-526-8724 \\ XX // =
= \X/\X/ =
= "I am Hitler of BorgSoft. I am the middle inital of William H. Gates. =
= Your work will be Microsofted. Resistance is futile. Heil Windows. =
=========================================================================
Yeah I use an Amiga at home. If you don't like my computer, dial
1-800-DIE-BILL and tell someone who cares.
----------------------------------------------------------------------
Path: news1.ucsd.edu!ihnp4.ucsd.edu!swrinde!cs.utexas.edu!uwm.edu!news.cse.psu.edu!news.ecn.bgu.edu!vixen.cso.uiuc.edu!newsfeed.internetmci.com!info.ucla.edu!news.bc.net!news.mindlink.net!van-bc!unixg.ubc.ca!freenet.vancouver.bc.ca!gordonf
From: gordonf@vcn.bc.ca (Gordon Fecyk)
Newsgroups: comp.os.ms-windows.win95.misc,comp.os.ms-windows.setup.win95,comp.os.ms-windows.networking.win95,comp.os.ms-windows.apps.compatibility.win95,comp.answers,news.answers
Subject: Win95 FAQs and Answers Part 13 of 14: MS Plus!
Followup-To: comp.os.ms-windows.win95.misc,comp.os.ms-windows.setup.win95,comp.os.ms-windows.networking.win95,comp.os.ms-windows.apps.compatibility.win95
Date: 30 Jun 1996 16:36:55 GMT
Organization: Vancouver Regional FreeNet
Lines: 447
Approved: news-answers-request@MIT.EDU
Message-ID: <4r6af7$80p@milo.vcn.bc.ca>
NNTP-Posting-Host: opus.vcn.bc.ca
Summary: These postings list many questions asked in said newsgroups,
and answers them as best as I can. I make references to other
Web sites and FAQs when appropriate. Visit the WWW home of
this FAQ (http://www.intouch.bc.ca/win95) for the appropriate
links. This section is the 13th: MS Plus
X-Newsreader: TIN [version 1.2 PL2]
Xref: news1.ucsd.edu comp.os.ms-windows.win95.misc:111609 comp.os.ms-windows.setup.win95:10986 comp.os.ms-windows.networking.win95:7520 comp.os.ms-windows.apps.compatibility.win95:3585 comp.answers:15524 news.answers:61925
Archive-name: windows/win95/faq/part13
Last-Modified: 1996/07/01
Posting-Frequency: Every two months
URL: http://www.intouch.bc.ca/win95/faq13.htm
13) Microsoft Plus (tm) add-on for
Win95
What is Microsoft Plus and why do I care?
How do I use...
...System Agent?
But Norton Anti-Virus (tm) already installed a scheduler!
But F-Prot Anti-Virus (tm) already installed a scheduler!
But Colorado Backup (tm) already installed a scheduler!
How can I use System Agent instead of those other
schedulers?
Why should I use System Agent instead of those other
schedulers?
Top ten reasons why System Agent is cool to use
...Internet Explorer and Setup Wizard?
Why should I get Internet Explorer 2.0?
...DriveSpace 3?
Is it safe to use Norton Utilities for Win95 with
DriveSpace 3?
...Desktop themes?
How do I make my own theme and save it?
Where can I get more themes?
Why do all the themes I downloaded take up so much
hard drive space?
How did Microsoft replace all the drive, folder, printer,
etc icons?
How can I do it?
...the "Visual Enhancements"?
How do I remove the Visual Enhancements?
...Dial-up Networking Server?
...3D Pinball?
How come 3D pinball doesn't play any music or sound
effects?
Top ten things missing from Microsoft Plus
----------------------------------------------------------------------
What is Microsoft Plus and why do I care?
MS Plus! is all the stuff that Microsoft should've included in Win95,
but decided they wanted to make you pay more for them. OK, it's
really a bunch of add-ons designed for high powered computers
('486 machines and Pentiums) to make your system run a little
smoother and look a little nicer. Kerep in mind that the Plus stuff is
for high powered computers, which was probably the biggest
reason MS didn't include this stuff with the operating system.
----------------------------------------------------------------------
How do I use System Agent?
System Agent is a little scheduler that runs programs at certain
times. It's quite handy because it already schedules disk
maintanence processes, so all you have to do is keep your
computer turned on and it keeps itself clean.
To install System Agent, install MS Plus. A little icon shows up in
the SysTray; the place with the date and time in it on the Taskbar.
Double-click it to bring up the System Agent manager. You will see
four programs already scheduled (five, if you installed DriveSpace
3) which will scan your hard drives, de-fragment them, check for
low disk space, and re-compress any DriveSpace 3 drives you
have.
You can bring up properties for these programs, and change their
settings and their scheduled run times. System Agent-Aware
programs will offer special "Scheduled settings" requesters if you
change their settings from here.
You can also add new programs to this list. Hit Program/Schedule
new program. Hit Browse to search for the program you want to
run, or type its command line in the box. NOTE: Programs with
long filenames or directory names belong in quotes, like
"C:\Program Files\Plus!\RunMe.EXE" /parameter1 for example.
Bring up properties for the included programs for examples.
Any clickable object in Explorer can run from System Agent,
including DOS .PIF files and even documents. I specify "PIF"
because it's better to specify a DOS program's settings and use the
PIF as the object to run. Win 3.1 and Win95 programs and
documents will have their icons appear in this window.
----------------------------------------------------------------------
But Norton Anti-Virus (tm)/F-Prot Anti-Virus (tm)/Colorado
Backup (tm) already installed a scheduler!
So? You paid for System Agent when you bought MS Plus. Use it.
I get a real kick out of people who run three different schedulers
and then complain that their system swaps to the hard drive so
often. They're a waste of memory.
----------------------------------------------------------------------
How can I use System Agent instead of those other
schedulers?
First you will need to remove the other schedulers. The three I
mentioned all insert an icon in the Startup group in your Start Menu.
They're easy enough to remove; here's how to remove Start Menu
items.
Second, read up on the programs you want to schedule. The three I
mentioned all have instructions for running them from a command
line, for example, Norton Anti-Virus will scan all local hard drives
by running:
NAVW32.EXE /L
The /L means "local". Be sure to test this command line from a
DOS session; Win95 DOS sessions can run Windows programs,
and the START command in a DOS session can launch documents.
Third, Hit the Program menu in System Agent Manager and select
"Schedule new program". In the "Program to run" box, type in the
command line that makes your program run (like the NAVW32 /L
example above). Tell the program to run minimized if you wish.
Last, select "When to run..." and pick a time for this program to
run. Be careful not to overlap programs; you don't want an
Anti-Virus scan to happen while running ScanDisk, for example.
The System Agent Manager shows the last started and stopped
times of all scheduled programs, so use this as a guide for adding
new programs and preventing overlap.
For another example, Win95's built in Backup lets you launch the
backup set rather than the program. Just open the Full System
Backup from Backup, which enables Registry back-up, then select
the files or drives you want to back up. Pick your target (usually
your tape drive), pick your options, and save the backup set with a
unique name. Finally, schedule this backup set to run (by including
the .FST itself; not the program, and don't include a START
command; there's no need) in System Agent. Colorado Backup
works much the same way. Other back-up programs will have
different commands to use; experiment from a DOS prompt to get
the commands right.
Why should I use System Agent instead of those other
schedulers?
Is this a rehtorical question? You paid for it when you bought MS
Plus.
----------------------------------------------------------------------
Top ten reasons why System Agent is cool to use
10) It takes practically no memory
9) It can stop scheduled programs if you start using your computer
8) It can run stuff on start up if you don't like Startup groups (Great
for User Profile users)
7) It's always running (except in Safe Mode)
6) It's easy to schedule programs to run
5) It keeps your hard drives clean by running ScanDisk for you
4) It knows when you're on batteries (notebooks) and won't run big
programs if you're on batteries
3) It can wake you up in the morning (heh heh... just schedule a
.WAV file to play every day at 6:00 AM)
2) You don't need a Pentium to use it (heh heh)
1) It comes with all the other cool stuff in MS Plus
----------------------------------------------------------------------
How do I use Internet Explorer and Setup Wizard?
When you re-start the computer after installing Plus, you'll notice an
obvious "The Internet" icon staring at you. Open it. This launches
the Internet Setup Wizard. I won't get redundant, so to make it
short & sweet, get an answer sheet from your service provider with
answers to these questions:
Access phone number
Login name and login password
DNS server addresses
Gateway address (if using default gateway, ignore this)
E-MAIL address
POP3 server login name and password (Usually same as dial-up
login name and password)
POP3 server name (usually mail.somewhere.com or something
like that)
Also SMTP server name for outgoing mail (if it's not the same as
the POP server)
Check out the detailed Setup Wizard Instructions for the rest of the
details. The wizard will add all the needed Win95 networking
components to get you hooked to The Internet.
Why should I get Internet Explorer 2.0?
Well, It's free, has a lot of things missing from the web browser
included in Plus, and it's a direct upgrade. Visit the Internet
Explorer Home Page.
After you run the Internet Setup Wizard you could get a different
browser instead, like NCSA Mosaic, and the auto-dialer and stuff
will still work with it.
----------------------------------------------------------------------
How do I use DriveSpace 3?
No point in being redundant... check out the Disk Compression
Section.
Is it safe to use Norton Utilities for Win95 with
DriveSpace 3?
I don't trust it, even though Symantec swears by it. Contrary to
popular belief, Microsoft's ScanDisk and Defrag (You know; those
programs that MS pirated off Symantec?) work just fine on
DriveSpace 3 drives, keeping them clean, especially if you schedule
these programs to run regularly with System Agent.
Notice though, that Plus comes with replacement versions of
ScanDisk and Defrag, so that's enough to scare me from third party
disk maintanence tools... MS must've changed something
fundamental with DriveSpace 3.
----------------------------------------------------------------------
How do I use Desktop Themes?
Be sure to install at least one theme from the included Plus themes
to enable themes in general, otherwise Plus Setup won't install any
theme support. You can always hand-delete the components of the
theme and retain theme support.
From here, you can use a theme from the included list, or download
a favorite from www.windows95.com.
How do I make my own theme and save it?
To make your own theme, make your own custom changes to the
desktop scheme, colour scheme, sound scheme, mouse pointers,
and screen saver, using the Properties sheets or control panel
programs for each. Once you're satisfied with your work, run the
new Themes control panel and "Save As..." to create a .theme file.
You may also change the icons for My Computer, Net
Neighborhood, and Recycle Bin. Bring up Display properties and
hit the Plus! tab to change them.
You should store all the custom icons, animated pointers, sounds,
screen saver, and bitmaps in C:\Program Files\Plus!\Themes so
your theme users can install the theme easily. If you use a custom
font, include instructions on copying the font to the Windows\Fonts
folder. Batch files can use the Win95 START command if
necessary.
Where can I get more themes?
www.windows95.com has a well regulated themes section. I'm sure
other major FTP sites will also carry Plus themes.
Usually a custom theme has a special installation procedure; you
have to install a font, copy a screen saver to your Windows
directory, copy a bitmap to your Windows directory, etc, for use in
the theme. All of these options (except custom fonts) can go
anywhere in the hard drive, so C:\Program Files\Plus!\Themes is a
good place to keep them.
Why do all the themes I downloaded take up so much
hard drive space?
Be warned: a typical theme is about > to 1 MB in size, and that's
the compressed size!
Be reasonable; pick a theme after you browsed all the themes you
wanted to see, and delete the components of the others.
----------------------------------------------------------------------
How did Microsoft replace all the drive, folder, printer, etc
icons?
This is actually quite "cool" how they did this. Explorer has Registry
entries for each icon type it displays, and grabs that icon type from
an .ICO or .DLL file when it starts. It usually grabs them from
SHELL32.DLL.
Plus Themes also support these Shell icons, though they don't
document them. Look for a library file labeled COOL.DLL (I'm not
making this up!) and QuickView it, or try changing the icon for any
shortcut and use COOL.DLL as the source for the new icon. There
are icons in that library to replace all the normal Shell icons. Theme
support also includes replacing the SHELL32 icons with these
COOL ones.
You won't notice any changes to the icons until you use 65
thousand or 16 million colour modes; then the system over-writes
COOL.DLL with a HiColor version. The HiColor icons really
stand out compared to the 256 colour ones. NOTE: If you ever
have to re-install Win95, Setup will restore thr original
SHELL32 icons; you'll need to re-install Plus to restore the
COOL icons.
Theme support does not include directly modifying these icons, but
you could do some searching with REGEDIT (if you feel
adventureous) for the key "DefaultIcon" in any of the
HKEY_CLASSES_ROOT\CLSID sections. There is a
DefaultIcon key for most of those.
How can I replace all the drive, folder, printer, etc icons?
This is a theory, but it is possible based on the COOL.DLL stuff
last section. COOL.DLL is really a 16-bit library (QuickView it to
see for yourself). So, it is possible to edit COOL.DLL with a Win
3.1 icon editor that supports library files (such as Borland's
resource editor for Win 3.1 which comes with Turbo C++), or
copy it and replace all the icons. This is safer than Registry hacking,
and it's easier to transport with your theme.
Once you do that, save it with the name COOL.DLL and replace
the one in your SYSTEM directory with this one. You will need to
re-start Win95 for this to take effect. You will need to replace the
Computer, Net Hood, and Recycle Bin icons the normal way, but
the icons can come from the COOL.DLL replacement you make
up.
NOTE: Every time I see the file "COOL.DLL" I think of an AVI
file Microsoft distributed with their VidTest 1.0 package, which had
Bill Gates saying "Cool!" at the end of it. Look for COOL.AVI in
the MS Multimedia Demo CD-ROM, or in VidTest.
----------------------------------------------------------------------
How do I use the "Visual Enhancements"?
Check out the Plus! tab in Display Properties. This tab shows up
when you install the enhancements from Plus Setup. From here, you
can enable full window drag (which drags the contents of a window
instead of an outline), wallpaper scaling, font smoothing, etc.
Many of these options only work on fast computers with faster
video cards. Don't attempt to use these on a computer less than a
'486 with some kind of high speed video (VESA local bus, PCI)
and a proper video driver for Win95. Font Smoothing only works
on 65 thousand or 16 million colour displays; it uses gray shades to
fill in the jagged edges of large point sizes, and really isn't necessary
if you use TrueType a lot.
How do I remove the Visual Enhancements?
Just turn them off in Display Properties, on the Plus! tab.
----------------------------------------------------------------------
How do I use the Dial-up Networking Server?
Make sure you install Dial-up Networking before you install Plus. If
you choose the dial-up server, you will see a new "Dial-up server"
entry in the Connections menu. Dial-up server works with Win95
(PPP) dial-up clients, and Windows for Workgroups (RAS) clients.
Check out the Dial-up server Details.
From here, select a modem (all the modems appeare as tabs in this
requester) and enable or disable caller access. If you use User
Level Security you can allow particular users on this dial-in
connection, or you can install a password. You may only enable
one modem as a dial-in modem; Microsoft had to disable this
functionality so it doesn't kill sales of NT server. Heh heh
The dial-up server uses the same bindings as the dial-up
connections, so you need to install the Dial-up Adapter and
protocols for it in your Network Properties. It will automatically use
all protocols available to it for PPP clients, but only use NetBEUI
for RAS clients.
NOTE: WFWG dial-in clients (using their included RAS
software) won't work with Win95 dial-up servers running User
Level Security, because the dial-up server can't get a clear-text
version of the NT domain password. If you want WFWG clients to
dial into NT domains through Win95 dial-up servers, disable user
level security on the dial-up server!
The server also acts as a NetBIOS and IPX router to any network
it's connected to, and there's no way to turn off routing.
Administrators: If you don't want your users to open up your
network to the world, disable all Win95 dial-up servers through
system policies.
----------------------------------------------------------------------
How do I use 3D Pinball?
Use? Play, you mean. Just install it from Plus Setup. You'll find the
icon for it in your Games group on your Start Menu, along with the
other classic time wasters like Minesweeper, etc.
How come 3D pinball doesn't play any music or sound
effects?
Most likely because you don't have a sound card, but if you do,
turn on the Music and Sound from the game's Options menu.
Music won't play unless you have a working MIDI device installed.
This works by default on cards with Win95 drivers, but Win 3.1
drivers require special MIDI mapper tuning. Gravis Ultrasound
users will have to manually load a patch map into the GUS's
memory before 3D Pinball will play music.
----------------------------------------------------------------------
Top ten things missing from Microsoft Plus
10) IMAP4 client for Exchange instead of POP3
9) Internet Explorer 2.0
8) Nice method to replace any Shell icon
7) Hardware interface to coffee pot, to start it from System Agent
(Right after it plays a .WAV file for a wake-up alarm!)
6) Method of starting a dial-up connection from System Agent
(Any ideas here?)
5) Win95 admin tools for NT and NetWare networks (The NT
resource kit does have Win95 admin tools though)
4) Good TCP/IP control utility for setting RTU, TTL, etc
3) Internet Idioms for Exchange
2) A proper Marijuana plant icon for the Recycle Bin in the 60's
theme
1) A TCP/IP router for the Dial-up Server
----------------------------------------------------------------------
[Back to Table of Contents]
--
============================================================// //========
= "I am Gordon of Winterpeg. Windows WAS futile." // // =
= Find out why: http://www.intouch.bc.ca/win95 // // =
= Personal E-MAIL: gordonf@vcn.bc.ca \\ \\// // =
= Home Phone: +1-604-526-8724 \\ XX // =
= \X/\X/ =
= "I am Hitler of BorgSoft. I am the middle inital of William H. Gates. =
= Your work will be Microsofted. Resistance is futile. Heil Windows. =
=========================================================================
Yeah I use an Amiga at home. If you don't like my computer, dial
1-800-DIE-BILL and tell someone who cares.
----------------------------------------------------------------------
Path: news1.ucsd.edu!ihnp4.ucsd.edu!agate!howland.reston.ans.net!nntp.coast.net!news.kei.com!newsfeed.internetmci.com!info.ucla.edu!news.bc.net!news.mindlink.net!van-bc!unixg.ubc.ca!freenet.vancouver.bc.ca!gordonf
From: gordonf@vcn.bc.ca (Gordon Fecyk)
Newsgroups: comp.os.ms-windows.win95.misc,comp.os.ms-windows.setup.win95,comp.os.ms-windows.networking.win95,comp.os.ms-windows.apps.compatibility.win95,comp.answers,news.answers
Subject: Win95 FAQs and Answers Part 14 of 14: Miscelaneous
Followup-To: comp.os.ms-windows.win95.misc,comp.os.ms-windows.setup.win95,comp.os.ms-windows.networking.win95,comp.os.ms-windows.apps.compatibility.win95
Date: 30 Jun 1996 16:39:10 GMT
Organization: Vancouver Regional FreeNet
Lines: 457
Approved: news-answers-request@MIT.EDU
Message-ID: <4r6aje$80p@milo.vcn.bc.ca>
NNTP-Posting-Host: opus.vcn.bc.ca
Summary: These postings list many questions asked in said newsgroups,
and answers them as best as I can. I make references to other
Web sites and FAQs when appropriate. Visit the WWW home of
this FAQ (http://www.intouch.bc.ca/win95) for the appropriate
links. This section is the 14th and last one: Miscelaneous
This section also includes starts of my Logo Lamers page,
which you can ignore as you wish.
X-Newsreader: TIN [version 1.2 PL2]
Xref: news1.ucsd.edu comp.os.ms-windows.win95.misc:111603 comp.os.ms-windows.setup.win95:10980 comp.os.ms-windows.networking.win95:7514 comp.os.ms-windows.apps.compatibility.win95:3579 comp.answers:15518 news.answers:61919
Archive-name: windows/win95/faq/part14
Last-Modified: 1996/07/01
Posting-Frequency: Every two months
URL: http://www.intouch.bc.ca/win95/faq14.htm
14) Stuff that doesn't belong in the
other categories (and my own
personal rantings)
Why did Microsoft change Windows so much?
How come (this old Win 3.1 driver) doesn't work?
How come (this old Win 3.1 driver) works? I thought it wasn't
supposed to work!
Why shouldn't I run (this old Windows 3.1 program)?
Can I run Win95 on my '286 with 2 MB of RAM? (joke)
Can I run Win95 on my '386-SX with 4 MB of RAM? (a bit of
a joke, but it does run)
Why do 32-bit programs seem slower than the original 16-bit
ones?
Why didn't Novell/WordPerfect (tm) release a 32-bit version of
PerfectOffice (tm) yet? (UPDATE)
I want to get a Pentium Pro (tm) system, but isn't it slower
running Win95 than a Pentium?
Top ten reasons why Microsoft created Windows 95
Top ten answers to Microsoft's question: "Where do you want
to go today?"
----------------------------------------------------------------------
Why did Microsoft change Windows so much?
Let's face it; Microsoft Windows was a lame DOS extender with
fancy CPU-draining graphics. Even with all the good apps written
for it, the base was shaky. Too many app writers also hacked and
patched Windows so much that nothing worked right together.
Win95 turned the lame DOS extender into as much of a full fledged
OS as possible, without removing DOS altogether.
The Win95 designers tried to take the best ideas, best patches, best
hacks, and integrate them "nicely" into the OS. For example, you
can have virtual desktops with any video card now. The COM port
drivers take advantage of new hardware by design. It still uses
fancy CPU-draining graphics, but it's not just a DOS extender
anymore.
They supposedly got a bunch of "average" people in to rate the OS
and user interface as it stood. They took suggestions from many
people of different walks of life, then totally ignored them.
Supposedly, Win95 is now the OS that anyone can use. Yeah right.
You have to give them credit for a good effort though.
Not to mention all the features they pirated from Apple, Xerox,
Amiga Tech, and IBM, do make it a bit easier to get along with.
MS also wants to bury DOS for good. I believe this, because of the
penultimate Designed for Win95 requirement: The product must run
in Windows NT Workstation too. Besides... too many people out
there are ignoring Win95 in favor of NT. R.I.P. D.O.S.
----------------------------------------------------------------------
How come (this old Win 3.1 driver) doesn't work?
It probably replaced some core Win95 system file, then Win95
replaced its version back. This happens with communication
programs that replace COMM.DRV with their own.
Win 3.1 video drivers tend to hack USER.EXE and GDI.EXE
these days, to provide virtual desktops and such nonsense. Printer
drivers often have their own versions of UNIDRV.DLL or
whatever.
Ask the maker of the hardware if they tested their Win 3.1 driver
with Win95. If not, they probably have a Win95 driver for you. If
no Win95 driver, do yourself a favor and dump the hardware for a
Win95 compatible equivalent.
Net card drivers for Windows for Workgroups won't work for
sure, which is too bad, because those things got decent
performance.
----------------------------------------------------------------------
How come (this old Win 3.1 driver) works? I thought it wasn't
supposed to work!
Then again, "nicely" written drivers that don't replace system
components will work. Most of these include sound card drivers,
though Win95 ignores any MIDIMAP.CFG files; it treats single
MIDI devices as whole patch sets now. You can get MIDI
Mapper functionality with Multimedia properties/MIDI and select
"Custom instrument".
These classes of Win 3.1 drivers could work smoothly with Win95,
if you install them from Add New Hardware/Have Disk:
Sound card (Including the PC Speaker driver)
Printer (Except those that replace core system files or install
dumb "Printing Systems")
DOS CD-ROM (Don't forget MSCDEX if you have to use
these)
Net card (NDIS 2 and ODI drivers work with NDIS 3.1
protocols and clients)
Media Control (MCI) drivers and video CODECs
Notice I wrote "Drivers". Don't install whole programs if they come
with the drivers if you can avoid it; use Add New Hardware and
have it point to the disk with the OEMSETUP.INF file.
All other classes of Win 3.1 drivers you should avoid completely!
----------------------------------------------------------------------
Why shouldn't I run (this old Windows 3.1 program)?
Avoid running these classes of Win 3.1 apps in Win95 for these
reasons:
Communication (Tend to replace Win95 COMM.DRV and
defeat TAPI)
Printing Systems (Waste of memory)
Virus checkers (Can mis-interpret 32-bit components)
Disk utilities (Particularly un-deleters and such that rely on real
mode disk access)
Back up programs (No long filename support)
----------------------------------------------------------------------
Can I run Win95 on my '286 with 2 MB of RAM? (joke)
Oh sure you can. Just get one of those Cyrix 486 processors for
'286 system boards (hah hah)
Seriously, Win95 will run on one of these things I suppose, with the
486 hack, about as well as it could on a 16-bit bus system with 4
MB memory...
----------------------------------------------------------------------
Can I run Win95 on my '386-SX with 4 MB of RAM? (a bit
of a joke, but it does run)
The same here I'm afraid. I tried it once. Never again.
----------------------------------------------------------------------
Why do 32-bit programs seem slower than the original 16-bit
ones?
Microsoft's excuse to this is app writers are just learning how to
write Win32 programs. This is probably right; you can't just take a
C program optimized for Win 3.1 and throw a compiler switch.
You have to make Win32 calls, switch your DOS calls to Win32
disk calls, use built in libraries and requesters instead of the
home-made ones, and trim off the extra memory you'd allocate just
to over-compensate. There's a lot of bad programming practice out
there. I personally believe that all the ex-Amiga coders out there
will take to Win95 the easiest, because we already know how to
write tight code.
Another good excuse is that programmers don't trust the OS and
try to access hardware directly. Wrong. This not only forces a lot of
excess bulk in the code, it has to fight with the OS to get to the
hardware. Some really un-trusting software houses (like Novell) will
even include their own whole subsystems into the OS, rather than
use what's already there. Bad move. Result: 4 MB network clients
(compressed) compared to oh, 200 KB.
Yet another excuse? Intel. The Pentium and '486 class processors
were really optimized for 16-bit code. As much as Intel and
Microsoft wanted to push programmers into using the extended
instruction set of 32-bit processors, the programmers had a 16-bit
OS to contend with, except for a privileged few coding for
NetWare, OS/2, or NT. (OK maybe some UNIX people too)
Hence the Pentium Pro's optimization towards 32-bit code. Of
course all the cheap clone processors had to be fast running 16-bit
code too.
The new companies coming out tend to write cleaner and faster
code that use the OS. Check out the shareware on
www.windows95.com or any major FTP site. The old established
firms will take a long time to switch over.
----------------------------------------------------------------------
Why didn't Novell/WordPerfect (tm) release a 32-bit version
of PerfectOffice (tm) yet?
WordPerfect corp has a history of re-writing everything from
scratch. WordPerfect 6.1 hardly used any built in calls in Win 3.1;
they don't use the Common Dialog for file operations (which is why
Norton's LFN enabler for Win95 doesn't work in it), they don't use
Win 3.1 print functions (causing screwups if you leave EMF
spooling enabled sometimes), and it becomes a monster in the
process, with two patches so far for working in Win95.
Corel just released their own versions of the WordPerfect Office
programs for Win95. I haven't had a chance to look at it beyond
the readme file, but that already scared me because of a notice that
"This program does not run under Windows NT." I understand that
Microsoft included a lot of the Win95 sub-system with MS Office
95 for NT users, but why could not Corel do the same?
If any of you have access to NT 4.0 or the NewShell technology
preview for NT 3.51, please try Corel's WordPerfect 7 Suite on it.
If it's just that NT's missing some Win95 components, then WP7
should run on NT 4.0 beta or the shell preview. If any of you find
out that it does run, it'll be the first in my Logo Winners Page.
----------------------------------------------------------------------
I want to get a Pentium Pro (tm) system, but isn't it slower
running Win95 than a Pentium?
I don't have the details on this, but the noise out there suggests a
Pentium Pro runs 16 bit code slower than a Pentium does. Intel's
optimized the 'Pro for 32-bit code, just like Microsoft's pushing
32-bit apps for the "Designed for Win95" logo. This is another sign
that these two giants are trying to kill DOS.
Yes, the 'Pro will run Win95's 16 bit components slower than a
Pentium can. According to KB article Q122869, these components
use 16-bit code:
Disk utilities (Scandisk, Defrag, DriveSpace 2)
Games (The built in time-wasters, even Freecell is a 16-bit
version here)
Win 3.1 compatibility stubs (like KRNL386, USER, GDI, all
the .DRV files)
Win 3.1 components (WinChat, SYSEDIT, Program Manager,
File Manager, WinVer)
The Win95 tour
DOS programs and COMMAND.COM, and the start up code
which uses DOS
If you use only Win32 programs, you won't touch the 16-bit code
once Win95 is up. If you avoid DOS programs you won't use DOS
for any hardware access.
Yes it's slower than a Pentium for old crap, but it's faster than a
Pentium for the new crap.
----------------------------------------------------------------------
Top ten reasons why Microsoft created Windows 95
(I can use some jokes here)
10) Microsoft had too many programmers doing nothing
9) Bill Gates had a vision from God
8) "Mac on PC! Mac on PC!"
7) Bill Gates wanted to celebrate their latest court victory over
Apple with a bang
6) To sell more NT servers
5) To sell more NT workstations (Hence the Designed for Win95
requirements)
4) MS couldn't buy the source code to the Amiga OS (Though I
bet they tried real hard)
3) OS/2 flopped, NT originally flopped, maybe third time lucky?
2) To bring PCs and users up to speed
1) To kill DOS dead
----------------------------------------------------------------------
Top ten answers to Microsoft's question: "Where do you
want to go today?"
10) Work.
9) Hell.
8) The Win95NetBugs page to see where else Microsoft screwed
up.
7) www.windows95.com for cool Win95 shareware
6) Disneyland. (tm)
5) The MS Knowledge Base because Win95 tech support's too
busy
4) netwire.novell.com to get Client32 (I don't know why...)
3) Redmond, Washington, to assassinate William H. Gates.
2) The Jones's. They have a Mac.
1) Home.
----------------------------------------------------------------------
Rantings from yours truly: (Logo Lamers at the end)
Back in 1985 I went ga-ga over the newly released Amiga by
Commodore. All this cool hardware that was light-years beyond
the faintest hopes of DOS box users with their 8-bit XTs and 16-bit
'286 machines. The first true 32-bit system (Ok so it used a 16-bit
68000, but that 68000 was designed for 32-bit operation from day
one, and the software was ALL 32-bit). I still have an Amiga with
all the latest hardware and enjoy the old stuff (which still runs) and
the new stuff I download from Aminet every other day.
Now ten years later the DOS box industry finally catches up (while
Commodore slept for ten years and eventually went bankrupt) and
Microsoft, the un-disputed industry leader, releases their answer.
Of course they had to keep ten years of 8-bit compatibility (and
DOS boxes will suck forever because of this) but the excitement
was there; one I haven't felt really since 1985. Ok it was there for
about two months with OS/2 2.0 but if you're visiting this page
chances are you aren't using OS/2. I feel the excitement when I find
a cool piece of shareware or some new software that really takes
advantage.
So it was a lame story, OK? But for the first time here's a computer
system that is Mainstream and also Cool. Probably my next system
will run NT when everyone writes cool 32-bit software, but until
then Win95's here, and it's my job to support my boss's customers
who use it.
Hence the FAQ. I read too many stupid and lame questions on the
newsgroups, and the same people insist on running CorelSCSI or
some other old DOS crap because their hardware sucks without it.
Well guess what? Your hardware just sucks even WITH
CorelSCSI or whatever the old DOS software is. Replace it and
get Win95 compatible stuff. That's the answer I keep telling
everyone on the newsgroups, and I know it works because
In-Line's customers do that and everything works. I also figure that
if the stupid questions get answered quickly, In-Line's customers
can call with more intelligent questions, which will usually take
longer, and earn us more, and won't bore us to tears.
Oh yes... regarding my blatant cross-posting of the FAQ. Like I
explained in the very first page and in fact the very first question,
FAQs are supposed to answer frequently asked questions, in order
to reduce traffic on USENET. A minor surge of a 350 KB of text
(which is what my FAQ totals to, incidentally) should prevent about
4 MB a day of useless questions. FAQs have nothing to do with the
World Wide Web (with the exception of FAQs about the WWW
itself) nor is it mandatory to post a FAQ on a web or FTP site.
I was asked to post the FAQ to the standard FAQ repositories
(being the archive at rtfm.mit.edu and news.answers and
comp.answers) so anyone without WWW or FTP access could get
them. So I have. And all I get is sh*t from a couple of salesmen
telling me not to pollute USENET. Yeah right; they probably just
don't want me taking what little business they have. Poor them; they
must go crazy answering stupid questions. I know I do.
I hope everyone out there reading this FAQ are as excited about
this new stuff as I am. Despite all the hype, hoopla, and bullsh*t,
this is finally going to turn Personal Computers upside-down.
...And now... the beginning of my Logo Lamers list!
Hewlett-Packard
Microsoft hasn't awarded any Logos to these guys yet, for good
reasons:
No "Made by HP" Win95 drivers for any of their printers. Any
of them.
Defective T4000s tape drive, that refuses to work with any
Adaptec AIC-6360 style cards or non-HPBACKUP 1.60
software (Non-standard command set!) And the tape drive
won't work in Windows NT Workstation either.
JetAdmin software with its long \\HP_Network_Printers
machine name, prevents Win 3.1 apps (and HP-made Win 3.1
printer drivers, I might add) from working with them! No
updated JetAdmin software over IPX for Windows NT either.
As a consequence, their JetDirect EX box, with three parallel
ports, only works on Windows NT with ONE port, not all
three! No Win NT, no Logo.
Delrina Communications/Symantec
My favorite Anti-Logo program, WinFAX Pro 7.0, had a third
update in recent days but it still insists on using its own dialing
scheme (not using TAPI) by default, and it allows for using DOS
COM ports instead of TAPI modems. So, if it doesn't require
TAPI, why doesn't it work with Windows NT?
I have to give Symantec credit for pcAnywhere32 however!
Excellent remote control program. Its host can remain active while
you use Dial-up Networking or MS Exchange Fax. And it works
with NT.
Novell
How the mighty have fallen. After working in the last couple of
months with NetWare 3.12 and NetWare 4.1, I'm surprised that
Microsoft hasn't taken over completely with NT server yet. I had
the pleasure to attend a Novell seminar last month, and I got my
personal copy of two-user NetWare 4.1 for attending. They had a
well-produced Drama (I use that word in the Soap-Opera sense)
comparing two companies, one running NT server and the other
running NetWare 4.1. Well, the best thing I remember from that
play was, Novell CNEs don't know how to use NT server. Also,
they cleverly hid the difficulties of login scripts and adding more
BIG apps. They don't know now to use Win95 either, relying on
their "Application Launcher" which is very redundant when you use
Custom Folders (or even just copying shortcuts in login scripts) to
spread new apps through a network.
NetWare 3.12 is as solid as ever, and with updated patches it can
even handle the SAP traffic of several Win95 stations running FPS
for NetWare. NetWare 4.1, however, is a bit too difficult to set up
for a small (five users?) network. It's probably fine for expansion
(the whole design scheme of Directory Services) but making it
compatible with Bindery software is a pain if you have multiple
Organizational Units.
Let's not forget Client32, the biggest client behemoth I've ever
seen! Client32 introduced their whole NetWare Lodable Module
interface into Win95, in the pretense that NLM authors can easily
use their current knowledge to write add-ons for stations running
Client32. Well guess what? NLMs completely re-invent what
Win95 Virtual Devices (VxDs) do already! And why does Novell
have to hack their own logic into a perfectly-working framework?
OK... I exaggerated. The components of Win95's networking
have their bugs, but the framework is damn solid! MS or
anyone else can easily replace a single component (like using a
third party TCP/IP protocol instead of MS's) without
disturbing the framework or other surrounding components.
Artisoft did it with LANtastic for Win95. Miramar Systems is
doing it with MacLAN connect. Banyan did it with their VINES
client. So what's Novell's excuse?
Microsoft
Of course I had to throw the definers of this spec in there. heh
heh...
MS gets a Logo Lamer award for FURY3, a game they wrote for
Win95, that supposedly requires the DirectX API but it came out
before DirectX did. Therefore it should run in Windows NT
because it doesn't require anything Win95-specific. Yeah Right.
They smartened-up when they released Return of Arcade. That
package has the "Windows Compatible" logo instead of the
Designed for Win95 logo, and they freely admit it won't run on
anything but Win95.
----------------------------------------------------------------------
[Back to Table of Contents]
--
============================================================// //========
= "I am Gordon of Winterpeg. Windows WAS futile." // // =
= Find out why: http://www.intouch.bc.ca/win95 // // =
= Personal E-MAIL: gordonf@vcn.bc.ca \\ \\// // =
= Home Phone: +1-604-526-8724 \\ XX // =
= \X/\X/ =
= "I am Hitler of BorgSoft. I am the middle inital of William H. Gates. =
= Your work will be Microsofted. Resistance is futile. Heil Windows. =
=========================================================================
Yeah I use an Amiga at home. If you don't like my computer, dial
1-800-DIE-BILL and tell someone who cares.