Thread View: comp.os.ms-windows.announce
1 messages
1 total messages
Started by Tom Haapanen
Thu, 28 Jan 1993 08:01
Windows FAQ: ASCII format, 01/06
Author: Tom Haapanen
Date: Thu, 28 Jan 1993 08:01
Date: Thu, 28 Jan 1993 08:01
1014 lines
45975 bytes
45975 bytes
The following is part 01 of 06 of the ASCII text version of the
Microsoft Windows FAQ (Frequently Asked Questions). While some of you
may find this the best format, the more popular format is the WinHelp
file. These are posted simultaneously with the ASCII version to
comp.binaries.ms-windows.
You can obtain a copy of the WinHelp version as "faqwin01.zip" by ftp
from sonygate.sony.com [192.63.138.2], in /pub/comp.binaries.ms-windows.
It will also be placed on ftp.cica.indiana.edu once disk space permits.
BEGIN--------------cut here--------cut here------------cut here----------
Microsoft Windows FAQ
Frequently Asked Questions
Copyright
This document is compilation copyright (c) 1990-1993 by Tom Haapanen. It
may be freely copied and/or distributed in its entirety as long as this
copyright notice is not removed. It may not be sold for profit or
incorporated into commercial products without the author's written
permission. [Compilation copyright means that you can freely use
individual sections of this document, but any significant collection of
sections is subject to the copyright.]
Note: This is an ASCII text version of the actual WinHelp-based FAQ. The
WinHelp version is posted to comp.binaries.ms-windows, and will also
be available for ftp at ftp.cica.indiana.edu.
CONTENTS
========
1. Credits
2. Microsoft Windows
2.1. Windows 1.0
2.2. Windows 2.0
2.3. Windows/386
2.4. Windows 3.0
2.5. Windows 3.1
2.6. Windows for Workgroups 3.1
2.7. Windows NT 3.1
2.8. Win32s for Windows 3.1
2.9. Windows for Pen Computing 3.1
2.10. Multimedia Windows
2.11. Modular Windows
2.12. Win-OS/2
3. Internet and Usenet
3.1. Usenet
3.2. Usenet Windows newsgroups
3.3. Alternatives to Usenet
3.4. Freeware and shareware by ftp
3.5. Popular Internet ftp sites
3.6. Using archie
3.7. Ftp by email
3.8. More about Internet and Usenet
3.9. FTP archives on CD-ROM
4. Setting Up and Configuring Windows
4.1. System Configuration
4.1.1. Minimum Windows 3.1 configurations
4.1.2. Minimum Windows 3.0 configurations
4.1.3. Minimum Windows NT pre-release configuration
4.1.4. Standard mode vs. 386 Enhanced mode
4.2. Selecting a hardware configuration for Windows
4.2.1. CPU/FPU
4.2.2. Memory
4.2.3. Hard disk
4.2.4. Video adapters
4.3. System BIOS compatability
4.4. Video drivers
4.4.1. Identifying Your Video Card
4.4.2. Locating a driver
4.4.3. Video card manufacturers
4.4.4. Using 256 (or more) colors in Windows
4.4.5. Panacea Winspeed
4.4.6. CGA drivers
4.5. Printer drivers
4.5.1. Selecting a PostScript printer driver
4.5.2. Eliminating the Ctrl-D in PostScript output
4.5.3. EPS graphics print in portrait even on landscape pages
4.5.4. Hewlett-Packard DeskJet printing problems
4.6. Math coprocessors and WIN87EM.DLL
4.7. Multimedia
4.7.1. AdLib cards and .wav files
4.7.2. Using MIDI cards with Windows 3.1
4.7.3. SoundBlaster Pro and Windows 3.1
4.7.4. Using the PC's built-in speaker
4.8. System Resources
4.9. Networking
4.9.1. Compatible Networks
4.9.2. Novell's NWPOPUP utility won't initialize
4.9.3. Using Windows for Workgroups with TCP/IP
4.9.3.1. FTP TCP/IP and NFS
4.9.3.2. Wollongong Pathway Access/NFS
4.10. Integrating with Unix e-mail
4.11. Serial Communications
4.11.1. Using COM3 and COM4
4.11.2. Using a high-performance 16550 serial port
4.11.3. DOS boxes and 16550 serial ports
4.11.4. SmartDrive and 16550 high-speed transfers
4.12. Disk drives and virtual memory
4.12.1. Virtual memory and swapfiles
4.12.2. Maximum swapfile size
4.12.3. Windows 3.x and Stacker
4.12.4. SCSI controllers
4.12.5. SmartDrive double buffering on SCSI drives
4.12.6. Windows 3.x and large hard disks
4.13. Troubleshooting
4.13.1. BMP wallpaper won't display correctly
4.13.2. Frequent GPFs (General Protection Faults)
4.13.3. File Manager won't format floppies
4.13.4. Incorrect system version; reinstall the 386 enhanced version of
Windows
4.13.5. Mouse hangs when using communications software
4.13.6. Parity errors with Windows 3.1
4.13.7. Performance deterioration in a 386 Enhanced mode DOS session
4.13.8. Problems creating a permanent swapfile in Windows 3.0
4.13.9. Program Manager claims only 8 KB of free memory
4.13.10. Using a slow expansion memory board with Windows
4.13.11. Windows 3.0 refuses to run without a file called WINA20.386
4.13.12. Windows 3.1 hangs or crashes during startup
4.13.13. Windows 3.1 hangs or waits a long time on exit
4.13.14. Windows 3.1 Resource Kit won't install
4.13.15. Windows 3.x waits a long time on startup
5. Windows and DOS
5.1. Configuring DOS sessions
5.1.1. DOS in a window
5.1.2. Lotus 1-2-3 in Windows
5.1.3. Reducing the amount of "jerkiness" in DOS window updating
5.1.4. Extended memory in DOS sessions
5.1.5. Changing the font size for a DOS window
5.1.6. Changing the number of lines inr a DOS window
5.1.7. Mouse in a DOS window
5.1.8. TSRs in DOS sessions
5.1.9. VGA graphics in a windowed DOS session
5.2. Troubleshooting DOS applications
5.2.1. Out of Environment Space
5.2.2. Protected-mode software
5.2.3. Corrupted diskettes when copying files in a DOS session
5.3. DOS shells and extenders
5.3.1. QEMM/386 and DesqView/386
5.3.2. MKS Toolkit: setting up
5.3.3. MKS Toolkit: maximizing DOS session memory
5.3.4. MS-SH
6. Windows Tips, Tricks and Secrets
6.1. General
6.1.1. Automatically opening applications on startup, with predefined
window positions
6.1.2. Changing or bypassing the startup logo
6.1.3. Changing the font used for the icon labels
6.1.4. Limiting the size of the temporary swap file
6.1.5. Making Windows 3.x act like 2.x runtime
6.1.6. Printing PostScript files without a PostScript printer
6.1.7. Search path in Windows
6.1.8. Swapping the Ctrl and CapsLock keys
6.1.9. Using a Dvorak keyboard
6.2. Program Manager
6.2.1. Changing the font used for the icon labels
6.2.2. Changing the program icon
6.2.3. Changing the title of the Program Manager window
6.2.4. Creating your own icons
6.2.5. Creating your own wallpaper
6.2.6. Previewing PostScript output
6.2.7. Restricting the Program Manager
6.2.8. Saving Program Manager settings without exiting Windows
6.2.9. Starting Windows without activating the applications in the
Startup group
6.2.10. Starting an application in a different directory
6.3. Windows Accessories
6.3.1. Cardfile: Converting to ASCII text
6.3.2. Clock: Windows 3.1 Clock limitations
6.3.3. Help: Changing the keyword colors
6.3.4. Notepad: F5 and current time
6.3.5. Recorder: Recording more than 60 seconds of sound
6.3.6. Terminal: Keypad
6.3.7. General: "Can't open TEMP.WRI" (or similar message)
6.4. Changing default directories
6.4.1. Bitmaps
6.4.2. Fonts
6.4.3. Icons
6.5. Fonts
6.5.1. TrueType, ATM and FaceLift
6.5.2. Converting Font Formats
6.5.3. Viewing available fonts
6.5.4. Foreign character sets
6.5.5. Converting Macintosh Type 1 (ATM) fonts to Windows
6.5.6. Replacing your System font with a serif font
6.5.7. Zip code bar code fonts
6.6. Applications
6.6.1. DayBook: running on Windows 3.1
6.6.2. Excel: Calling DLL routines
6.6.3. Excel: Doing log-log graphs
6.6.4. WinQVTNet: Hiding a gateway
6.6.5. Norton Desktop: Wider listbox for Scheduler
6.6.6. Norton Desktop: Using smaller fonts for lists
6.6.7. Word for Windows: changing bullet paragraph indent
6.6.8. Word for Windows: custom toolbar icons
6.6.9. Word for Windows: drop caps (large 1st characters of paragraphs)
6.6.10. Word for Windows: fonts larger than 127 points
6.6.11. Word for Windows: foreign-language dictionaries and thesauri
6.6.12. Word for Windows: getting rid of the list of last files edited
6.6.13. Word for Windows: inserting today's date
6.6.14. Word for Windows: linking in subdocuments
6.6.15. Word for Windows: numbering equations
6.6.16. Word for Windows: overlining words
6.6.17. Word for Windows: printing even and odd pages
6.6.18. Word for Windows: removing hard returns on downloaded text
6.6.19. Word for Windows: setting the find file default directory
6.6.20. Word for Windows: turning echo off in a macro
6.6.21. Word for Windows: using a watermark
6.6.22. WordPerfect for Windows: changing the background color
6.7. Gang screens ("Easter Eggs")
6.7.1. Windows 3.0
6.7.2. Windows 3.1
6.7.3. Ami Pro 2.0
6.7.4. Corel Draw! 3.0
6.7.5. Excel 3.0
6.7.6. Norton Desktop for Windows 2.0
6.7.7. PageMaker for Windows 4.0
6.7.8. Procomm Plus for Windows 1.0
6.7.9. Word for Windows 1.x
6.7.10. Word for Windows 2.0
7. Applications
7.1. Windows 2.x Applications
7.2. Troubleshooting
7.2.1. AllType: converted TrueType fonts not in same family
7.2.2. Ami Pro: table of contents
7.2.3. Ami Pro 2.0: divide by zero error
7.2.4. Ami Pro 3.0: overlapped screen text
7.2.5. Ami Pro 3.0: slow printing
7.2.6. Corel Draw!: can't rotate bitmaps
7.2.7. FrameMaker: scrambled dot-matrix output
7.2.8. KA9Q: dropped packets
7.2.9. Norton Desktop for Windows: can't format in the background
7.2.10. Norton Desktop for Windows: crashes from selecting files
7.2.11. Mathematica 2.0 for Windows: problems with Windows 3.1, other
problems
7.2.12. NCSA Telnet [in DOS session]: crashes in a window
7.2.13. PageMaker 4.0: font selection box won't scroll
7.2.14. PageMaker 4.0: text color changes to almost invisible
7.2.15. PageMaker 4.0: WordPerfect and Word for Windows import
7.2.16. Pathway Access 1.x: terminal font
7.2.17. PC Tools 7.1: restore problems
7.2.18. Procomm Plus for Windows: Zmodem transfer startup
7.2.19. Quattro Pro for Windows: High resource requirements
7.2.20. Quattro Pro for Windows: OLE and DDE problems
7.2.21. Quattro Pro for Windows: Saving over foreign formats
7.2.22. Quicken for Windows: conflicts with communications software
7.2.23. Ventura Publisher 3.0: divide by zero errors
7.2.24. WinFax Pro 2.0
7.2.25. Word for Windows: accessing fonts
7.2.26. Word for Windows 2.0: can't install additional components
7.2.27. Word for Windows 2.0: equation editor fonts
7.2.28. Word for Windows 2.0: equations have too much white space
7.2.29. Word for Windows 2.0: file too big to save
7.2.30. Word for Windows 2.0: headers and graphics
7.2.31. Word for Windows 2.0b: printing from Print Preview
7.2.32. WordPerfect for Windows 1.0: floppy access
7.2.33. WordPerfect for Windows 1.0: button bar won't display
7.2.34. WordPerfect for Windows 1.0: crashes with 256-color display
driver
7.2.35. WordPerfect for Windows 1.0: mixing landscape and portrait pages
7.2.36. WordPerfect for Windows 1.0: printing with TrueType
7.3. Available Windows 3.x applications
7.3.1. Mainstream applications
7.3.1.1. Databases, non-programmable
7.3.1.2. Databases, programmable
7.3.1.3. Desktop publishing
7.3.1.4. Financial Management
7.3.1.5. Groupware
7.3.1.6. Integrated sofware
7.3.1.7. Personal Information Management
7.3.1.8. Project management
7.3.1.9. Spreadsheets
7.3.1.10. Word processing
7.3.1.11. Word processing utilities
7.3.2. Graphics applications
7.3.2.1. Databases, image
7.3.2.2. Charting (flow and organizational)
7.3.2.3. Drawing and illustration
7.3.2.4. Graphics conversion
7.3.2.5. Image viewers
7.3.2.6. Painting and image editing
7.3.2.7. Presentation and business graphics
7.3.3. Communications
7.3.3.1. Communications (ASCII)
7.3.3.2. Communications (IBM mainframe)
7.3.3.3. Facsimile
7.3.3.4. Internet news and mail readers
7.3.3.5. Remote Access
7.3.3.6. TCP/IP Networking
7.3.3.7. X Windows servers
7.3.4. Fonts
7.3.4.1. Font packages
7.3.4.2. Font managers
7.3.4.3. Font utilities
7.3.5. Utilities
7.3.5.1. Backup software
7.3.5.2. Benchmarking utilities
7.3.5.3. Desktop enhancers
7.3.5.4. Program launchers: File Manager type
7.3.5.5. Program launchers: Program Manager type
7.3.5.6. Program launchers: integrated desktops
7.3.5.7. Program launchers: tool bars
7.3.5.8. Program launchers: other
7.3.5.9. Task schedulers
7.3.5.10. Task managers
7.3.5.11. Miscellaneous
7.3.6. Technical and engineering
7.3.6.1. CAD software
7.3.7. Engineering
7.3.8. Multimedia and entertainment
7.3.8.1. CD audio players
7.3.8.2. Games and entertainment
7.3.8.3. Multimedia authoring
7.3.8.4. Multimedia playback
7.3.8.5. Sound editors
7.3.8.6. Video Editors
8. Technical Support Contacts
8.1. Microsoft
8.1.1. Telephone
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
1. CREDITS
===========
The author may be contacted by the following means:
Internet: tomh@wes.on.ca
UUCP: uunet!watserv1!wes!tomh
BITNET: tomh@wes.on.ca
CompuServe: >INTERNET: tomh@wes.on.ca
Mail: Tom Haapanen
Software Metrics Inc.
22 King St. S., suite 303
Waterloo, Ont.
N2J 1N8, Canada
The Word for Windows 2.0 to Windows Help conversion utility used for
creating and maintaining this document, Dr. Help, was created by Roger
Hadgraft, senior lecturer in Civil Engineering at Monash University,
Clayton, Victoria, Australia.
Internet: roger.hadgraft@eng.monash.edu.au
UUCP: uunet!eng.monash.edu.au!roger.hadgraft
CompuServe: >INTERNET: roger.hadgraft@eng.monash.edu.au
I would also like to express my gratitude to the countless people who have
contributed information to the Windows FAQs, through Usenet news, email and
personal conversations. You know who you are: I'm grateful for your help,
as this FAQ would not be what it is without your help.
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
2. MICROSOFT WINDOWS
=====================
---------------------------------------------------------------------------
2.1. Windows 1.0
=================
Microsoft first began development of the Interface Manager (subsequently
renamed Microsoft Windows) in September 1981. Although the first
prototypes used Multiplan and Word-like menus at the bottom of the screen,
the interface was changed in 1982 to use pull-down menus and dialogs, as
used on the Xerox Star.
Microsoft finally announced Windows in November 1983, with pressure from
just-released VisiOn and impending TopView. This was after the release of
the Apple Lisa (but prior to the Macintosh), and before Digital Research
announced GEM, another competing graphical environment. Windows promised
an easy-to-use graphical interface, device-independent graphics and
multitasking support. The development was delayed several times, however,
and the first version hit the store shelves (after 55 programmer-years of
development!) in November 1985. The selection of applications was sparse,
however, and Windows sales were modest,
The following were the major features of Windows 1.0:
* Graphical user interface with drop-down menus, tiled windows and mouse
support
* Device-independent screen and printer graphics
* Co-operative multitasking of Windows applications
---------------------------------------------------------------------------
2.2. Windows 2.0
=================
Windows 2.0, introduced in the fall of 1987, provided significant
useability improvements to Windows. With the addition of icons and
overlapping windows, Windows became a viable environment for development of
major applications (such as Excel, Word for Windows, Corel Draw!, Ami, Page
Maker and Micrografx Designer), and the sales were spurred by the runtime
(Single Application Environment) versions supplied by the independent
software vendors. When Windows/386 (see next section) was released,
Microsoft renamed Windows to Windows/286 for consistency.
The following are the major changes from earlier versions of Windows:
* Overlapping windows
* PIF files for DOS applications
---------------------------------------------------------------------------
2.3. Windows/386
=================
In late 1987 Microsoft released Windows/386. While it was functionally
equivalent to its sibling, Windows/286, in running Windows applications, it
provided the capability to run multiple DOS applications simultaneously in
the extended memory.
The following are the major changes from earlier versions of Windows:
* Multiple DOS virtual machines with pre-emptive multitasking
---------------------------------------------------------------------------
2.4. Windows 3.0
=================
Microsoft Windows 3.0, released in May, 1990, was a complete overhaul of
the Windows environment. With the capability to address memory beyond 640K
and a much more powerful user interface, independent software vendors
started developing Windows applications with vigour. The powerful new
applications helped Microsoft sell more than 10 million copies of Windows,
making it the best-selling graphical user interface in the history of
computing.
The following are the major changes from earlier versions of Windows:
* Standard (286) mode, with large memory support
* 386 Enhanced mode, with large memory and multiple pre-emptive DOS session
support
* No runtime versions available
* Program Manager and File Manager added
* Network support
* Support for more than 16 colors
* API support for combo boxes, hierarchical menus and private .ini files
---------------------------------------------------------------------------
2.5. Windows 3.1
=================
Microsoft Windows 3.1, released in April, 1992 provides significant
improvements to Windows 3.0. In its first two months on the market, it
sold over 3 million copies, including upgrades from Windows 3.0. It is
currently continuing to sell at a rate of over 1 million copies per month.
The following are the major changes from Windows 3.0:
* No Real (8086) mode support
* TrueType scalable font support
* Multimedia capability
* Object Linking and Embedding (OLE)
* Application reboot capability
* "Mouse Trails" for easier mouse use with LCD display devices
* Better inter-application protection and better error diagnostics
* API multimedia and networking support
* Source-level API compatability with Windows NT
---------------------------------------------------------------------------
2.6. Windows for Workgroups 3.1
================================
The Windows for Workgroup package is the first integrated Windows and
networking package offered by Microsoft. It provides peer-to-peer file and
printer sharing capabilities (on a level comparable to LANtastic or Netware
Lite) highly integrated into the Windows environment. The simple-to-use-
and-install networking allows the user to specify which files on the user's
machine should be made accessible to others. The files can then be
accessed from other machines running either Windows or DOS.
Windows for Workgroups also includes two additional applications: Microsoft
Mail, a network mail package, and Schedule+, a workgroup scheduler.
---------------------------------------------------------------------------
2.7. Windows NT 3.1
====================
Microsoft Windows NT, scheduled for release in the first half of 1993, is
Microsoft's platform of choice for high-end systems. It is intended for
use in network servers, workstations and software development machines; it
will not replace Windows for DOS. While Windows NT's user interface is
very similar to that of Windows 3.1, it is based on an entirely new
operating system kernel.
The following are the major changes from Windows 3.1:
* Based on a new microkernel design
* Portable architecture for Intel x86, MIPS R4000 and DEC Alpha processors
* 32-bit addressing for access to up to 4 GB of memory
* Fully protected applications with virtualized hardware access
* Installable APIs for Win32, Win16, MS-DOS, POSIX and OS/2
* Installable file systems, including FAT, HPFS and NTFS
* Built-in networking (LAN Manager and TCP/IP) with remote procedure calls
(RPCs)
* Symmetric multiprocessor support
* Security designed in from start, to be initially C2 certified, with a B-
level kernel design
* API support for unsynchronized message queues, advanced interprocess
communication, registration databases, Bezier curves and graphics
transformations.
Although Windows NT has not yet been released, the following is generally
accepted as the minimum platform for use with the retail release of Windows
NT:
* 33 MHz 386 processor
* 8 MB memory
* 100 MB hard disk
* VGA graphics
As of July 1992, Windows NT is available as a pre-release SDK (Software
Development Kit) from Microsoft at the cost of $69 (or $399 for the pre-
release SDK plus full printed documentation). This release is supplied on
CD-ROM only, and contains the Windows NT operating system as well as all
the necessary 32-bit development tools (including a 32-bit C++ compiler and
all documentation online on the CD-ROM). The purchasers of this SDK will
also receive free updates to Windows NT up to and including final release.
The pre-release Windows NT SDK requires 12 MB of RAM and is not suitable
for evaluating the Windows NT environment. It is intended strictly for
software development! Contact your national Microsoft subsidiary (or
Microsoft itself in Redmond, WA) for ordering information.
---------------------------------------------------------------------------
2.8. Win32s for Windows 3.1
============================
Win32s is a set of libraries for Windows 3.1, which enable users to run
most Windows NT 32-bit applications on Windows 3.1, without the extensive
hardware requirements of Windows NT. The Win32s interface will likely
replace the older Windows-32 interface used by current 32-bit Windows
applications such as Mathematica.
The Win32s development tools are currently in beta release, but Microsoft
has not announced minimum system requirements for using Win32s
applications.
---------------------------------------------------------------------------
2.9. Windows for Pen Computing 3.1
===================================
Microsoft developed Windows for Pen Computing for use on pen-based systems.
In most aspects, it is basically equivalent to Windows 3.1 with extensions
for pen support. These extensions include the useof a pen as a pointing
device as well as handwriting recognition and conversion. Pen Windows
first shipped in April, 1992.
---------------------------------------------------------------------------
2.10. Multimedia Windows
=========================
The term Multimedia Windows describes a package with Windows 3.0 and the
Multimedia Extensions. These extensions are included in Windows 3.1, and
thus Multimedia Windows is no longer sold as a separate product.
---------------------------------------------------------------------------
2.11. Modular Windows
======================
Modular Windows is the operating system for Tandy Corp.'s Video Information
System (VIS) multimedia player. It is essentially similar to Windows'
core, but without any desktop accessories, TrueType fonts or a number of
other features.
---------------------------------------------------------------------------
2.12. Win-OS/2
===============
Win-OS/2 is the Windows component of IBM's OS/2 2.0. It is based partially
on Windows 3.0 and partially on 3.1. While it runs a majority of the
commercial Windows applications, it is not covered by this document.
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
3. INTERNET AND USENET
=======================
---------------------------------------------------------------------------
3.1. Usenet
============
If you received this FAQ from somewhere other than Usenet or Internet, you
may not be familiar with Usenet. Basically, Usenet is a loose collection
of over 100,000 computers which exchange mail and news. The network is
unstructured and highly distributed; most communication is either by TCP/IP
over high-speed connections, or UUCP over public telephone lines. Internet
is a (almost proper) subset of Usenet, consisting of somewhere between
50,000 and 100,000 computers connected by high-speed TCP/IP network
connections.
Usenet news is a software system where a person can post an article to a
selected newsgroup, and have every other news reader be able to read it.
There are over 1000 newsgroups (including the alt groups), and daily volume
of news is approaching 40 MB.
While most Usenet systems are Unix-based, it is not a requirement. If you
have an Internet or UUCP connection, ask your system administrator whether
you have Usenet news available. Some of the most common newsreading
software packages are readnews, rn, trn, nn and notes.
---------------------------------------------------------------------------
3.2. Usenet Windows newsgroups
===============================
There are a total of eight Usenet newsgroups dealing with Microsoft
Windows:
* comp.os.ms-windows.advocacy
This group is intended for adversarial discussions, arguments and
comparisons to other computers and operating systems.
* comp.os.ms-windows.announce
This is a low-volume moderated group with only Windows-related
announcements and with no discussion. Moderated by Todd Derr
(infidel@pitt.edu).
* comp.os.ms-windows.apps
This group contains discussions, questions, and comments about the
selection and use of Windows applications.
* comp.os.ms-windows.setup
This group is meant for questions and discussions about Windows setup
process, driver availability and selection, and hardware compatability
and selection.
* comp.os.ms-windows.misc
All other discussions about Windows should be in this group.
* comp.os.ms-windows.programmer.tools
This group is intended for discussions about the selection and use of
tools for Windows software development.
* comp.os.ms-windows.programmer.win32
All discussions about the Win32 applications programming interface (used
in Windows NT and Win32s) and the Windows NT SDK belong in this group..
* comp.os.ms-windows.programmer.misc
This group is for all other discussions about Windows software
development.
* comp.binaries.ms-windows
This group is for postings of free and shareware Windows applications,
utilities, display and printer drivers -- and for the latest FAQs.
Moderated by Tin Le (tin@something.sony.com).
The following groups have been replaced by those shown above:
* comp.windows.ms
This group was for discussions about Microsoft Windows.
* comp.windows.ms.programmer
This group was for discussions about programming for Microsoft Windows.
The following groups may also be of interest:
* comp.os.msdos.programmer
This groups contains general MS-DOS programming questions. Some,
especially those concerning compiler selection, may be of interest to
Windows programmers.
* bit.listserv.win3-l
This group is a two-way gateway of the BITNET WIN3-L mailing list.
The following groups are not for Microsoft Windows!
* comp.windows.misc
This group is for miscellaneous discussions about windowing systems in
general.
* comp.windows.news
This group is for dicussions about the Sun Microsystems NeWS windowing
system.
In general, these newsgroups are only available to computers connected to
Usenet or Internet; they are not gatewayed into BITNET, CompuServe, Prodigy
or other services. Some FidoNet BBS systems, however, do carry selected
Usenet newsgroups.
---------------------------------------------------------------------------
3.3. Alternatives to Usenet
============================
If you are unable to find a connection to the Internet (that procedure can
not be easily defined, as the Internet does not have any sort of a formal
structure), there are several alternatives available for finding more
information about Windows, and for locating Windows software and drivers.
BITNET users (as well as any other with an electronic mail connection to
Internet) can subscribe to WIN3-L (win3-l@uicvm.bitnet), a mailing list
dedicated to Windows discussions. This mailing list is similar in content
to the comp.os.ms-windows.misc newsgroup; no programmer mailing list exists
on BITNET.
If you live in North AMerica (or in one of selected Western European
countries), you can subscribe to CompuServe, a commercial service.
CompuServe has extensive Windows-oriented discussions and a fairly good
selection of free software. Although the level of discussion is often less
technical, it is much more structured than the Internet. CompuServe also
has numerous vendor-supported forums, including ones organized by Microsoft
for Windows and Windows NT.
Many FidoNet-based BBS systems also carry the Internet Windows newsgroups.
Consult a local BBS listing to find your nearest FidoNet BBS.
---------------------------------------------------------------------------
3.4. Freeware and shareware by ftp
===================================
While CompuServe (which has a lot of software) and your local BBS may have
large selections, the Internet provides an immense resource for all PC
users. The key program to access this software is called ftp (File
Transfer Protocol), and it's useable from most Internet system, but is not
usable through UUCP links.
If you do have ftp available to you, follow the example below to connect to
ftp.cica.indiana.edu (do not type in the // comments):
$ ftp ftp.cica.indiana.edu // make connection
Connected to ... // cica responds
Userid (user@cica): ftp // enter "ftp" as userid
Password: real_userid@site // enter your own userid
ftp> tenex // for binary transfers
ftp> cd /pub/pc/win3 // where the goodies are
ftp> ls -l // list the directory
ftp> get ls-ltR // get the current index
ftp> quit // we're done!
$ _
Of course, you can get multiple files at a time -- read the ftp manual page
for more information.
Remember that shareware is not free: register the software you use to
encourage the development of more low-cost software.
---------------------------------------------------------------------------
3.5. Popular Internet ftp sites
================================
The following ftp sites provide significant amounts of software of interest
to Windows users:
* ftp.cica.indiana.edu (129.79.20.84)
Directory /pub/pc/win3 contains one of the largest selections of Windows
software and device drivers anywhere. Mirrored by wuarchive. Please do
not access ftp.cica.indiana.edu between 8am and 6pm EST to prevent
overloading the system.
* simtel10.army.mil (26.2.0.74)
Directories /msdos1, /msdos2 and /msdos3 contains a very large selection
of MS-DOS (and some Windows) software. Mirrored by wuarchive.
* wuarchive.wustl.edu (128.242.135.4)
Directory /mirrors/win3 contains a copy of the cica Windows archives, and
directory /mirrors/msdos contains a copy of the simtel10 MS-DOS archive.
* ftp.uu.net (137.39.1.9)
Directory /vendors/microsoft contains a lot of the Microsoft developer
support materials available on CompuServe, including tech notes, sample
sources, the ODBC SDK and WinHelp documentation for Windows and Win32
SDKs.
* garbo.uwasa.fi (128.214.12.3)
Directories /win3 and /win31 contain a majority of the cica Windows
archives, and a fair amount f non-cica material. Note that garbo.uwasa.
fi is located in Finland, and North American users should avoid
congesting transatlantic Internet links by ftping from this site.
Mirrored by wuarchive.
If your ftp program complains about an unknown site, you can substitute
the numeric Internet address (shown after each site name above) for the
name in the ftp command.
---------------------------------------------------------------------------
3.6. Using archie
==================
If you know the program you're looking for, but don't know where to find
it, you might try using a utility called archie. This program allows you
to search for a filename in all the available ftp sites.
There are numerous archie servers available; to use one of them, telnet to
the system, and sign on as archie. Follow instructions to search for a
file. The following lists some of the know archie servers currently
available for use; pick one in your geographical area:
* archie.rutgers.edu United States (Northeast)
* archie.sura.net United States (Southeast)
* archie.unl.edu United States (West)
* archie.mcgill.ca Canada
* archie.au Australia and New Zealand
* archie.funet.fi Europe
* archie.doc.ic.ac.uk United Kingdom
---------------------------------------------------------------------------
3.7. Ftp by email
==================
There are several sites that will perform general FTP retrievals for you in
response to a similar mail query, although it appears that the info-
server@cs.net server is permanently out of order.
In general, please be considerate, and don't over-use these services. If
people start using them to retrieve megabytes and megabytes of GIF or WAV
files, they will probably disappear. Also, keep in mind that your system
may be linked to the net using a long-distance UUCP connection, and your
sysadmin may not be happy about large mail files using up modem time and
filling overloaded spool directories.
* bitftp@pucc.bitnet
For information on this one (available only to BITNET sites) send it the
message:
help
* ftpmail@decwrl.dec.com
For information on this server, available to all Internet sites, send it
a mail message with a body containing simply:
help
* mailserv@garbo.uwasa.fi
One final choice is to use the garbo.uwasa.fi server, which lets you
access the garbo.uwasa.fi archive (which contains most of the cica
files). For instructions, send it a mail message with "Subject: garbo-
request" and a single line of text "send help" to
send help
Please do not use this service if you are located in North America!
---------------------------------------------------------------------------
3.8. More about Internet and Usenet
====================================
To learn more about Internet and Usenet, I strongly recommend you purchase
or borrow a copy of Ed Krol's The Whole Internet User's Guide and Catalog
(ISBN 1-56592-025-2, $24.95), which covers email, news, ftp, archie and
much more. This 400-page handbook is a thorough guide to getting around on
the Net, clear enough for neophytes but with new information even for true
Internet veterans.
To purchase The Whole Internet User's Guide and Catalog, check your local
bookstore or contact the publisher, O'Reilly and Associates at 1-800-998-
9938 (103 Morris St., Sebastopol, CA 95472).
---------------------------------------------------------------------------
3.9. FTP archives on CD-ROM
============================
Walnut Creek offers copies of the cica, wuarchive and simtel FTP archives
on CD-ROM, at prices ranging from $25 to $50, with annual subscriptions
available. Call (800) 786-9907 or (510) 947-5996 for more information.
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
4. SETTING UP AND CONFIGURING WINDOWS
======================================
---------------------------------------------------------------------------
4.1. System Configuration
==========================
...........................................................................
4.1.1. Minimum Windows 3.1 configurations
------------------------------------------
The minimum system configurations to run Windows 3.1 are as follows:
* Standard Mode
286 processor, 640KB base memory, 256KB extended memory, EGA graphics
* 386 Enhanced Mode
386 processor, 640KB base memory, 1MB extended memory, EGA graphics
The following are recommended minimum configurations (based on the
experiences of many net Windows users) for good performance.
* Standard Mode
286/12 processor, 2MB total memory, VGA graphics, mouse
* 386 Enhanced Mode
386SX/16 processor, 4MB total memory, VGA graphics, mouse
...........................................................................
4.1.2. Minimum Windows 3.0 configurations
------------------------------------------
The minimum system configurations to run Windows 3.0 are as follows:
* Real Mode
8088 processor, 640KB base memory, CGA/Hercules graphics
* Standard Mode
286 processor, 640KB base memory, 256KB extended memory, CGA/Hercules
graphics
* 386 Enhanced Mode
386 processor, 640KB base memory, 1MB extended memory, CGA/Hercules
graphics
The following are recommended minimum configurations (based on the
experiences of many net Windows users) for good performance. (Real Mode is
not configurable for good performance, and many applications will not run
in it due to a lack of memory.)
* Standard Mode
286/12 processor, 2MB total memory, VGA graphics, mouse
* 386 Enhanced Mode
386SX/16 processor, 4MB total memory, VGA graphics, mouse
...........................................................................
4.1.3. Minimum Windows NT pre-release configuration
----------------------------------------------------
The minimum recommended system configuration to run the Windows NT pre-
release Software Development Kit is as follows:
* 386DX/33 processor
* 12 MB memory
* 100 MB hard disk
* VGA graphics
The recommended system configuration to run the final retail release of
Windows NT, including networking and several applications, is expected to
be the following (according to Microsoft):
* 386DX processor
* 8 MB memory
* 100 MB hard disk
* VGA graphics
...........................................................................
4.1.4. Standard mode vs. 386 Enhanced mode
-------------------------------------------
If you own a 386- or 486-based system, you have the choice of running in
either Standard or Enhanced mode. The following lists the advantages of
each:
Standard mode
* Speed. Many aspects of Windows run substantially faster in Standard
mode than in 386 Enhanced mode.
386 Enhanced mode
* Virtual memory capability.
* Multiple DOS sessions are pre-emptively multitasked.
* DOS sessions may be run in a window.
* Able to run 386-specific applications such as Mathematica, FrameMaker
and wdeb386.
---------------------------------------------------------------------------
4.2. Selecting a hardware configuration for Windows
====================================================
...........................................................................
4.2.1. CPU/FPU
---------------
As always, faster is better. However, CPU alone won't determine your
system's Windows performance.
You can get fairly good performance even with a 386SX/20 processor given
sufficient memory, and if you have a video accelerator card, a 386DX/40
doesn't feel much slower than a 486DX/33. You most definitely won't be
able to tell a 486DX/33 and a 486DX2/66 apart in "normal" Windows
operation.
Windows itself will not take advantage of a floating point unit such as the
287 or 387.
...........................................................................
4.2.2. Memory
--------------
Again, the more memory the better.
You can get tolerable performance with 2 MB, but 4 MB is a more realistic
minimum for decent performance. If you have 8 MB, you can use a reasonably
large disk cache (such as SmartDrive) and RAM disk; with 16 MB, you can
disable swapping completely and get even better performance.
Make sure your memory is either on the motherboard, or on a high-speed bus
(such as EISA or MCA). The standard ISA bus will slow your memory accesses
down to a crawl.
...........................................................................
4.2.3. Hard disk
-----------------
For best Windows performance, you want a WD-compatible disk controller. As
most SCSI controllers (such as the excellent Adaptec 1542B and 1740) are
not WD-compatible, they can not use Windows' FastDisk 32-bit disk access
facility. Worse yet, you may need to double-buffer your SCSI drive with
SmartDrive, further degrading performance.
The best bet for Windows 3.1 and future Windows NT performance is a high-
speed IDE drive (all of which are WD-compatible). The controllers are
inexpensive (and built into many motherboards), and the new drives are
quite fast. IDE drives tend to be smaller, however, than their SCSI and
ESDI counterparts, ranging from 40 MB up to about 500 MB (SCSI and ESDI
drives currently on the market range from 300 MB to over 2 GB).
The final option is to use an ESDI drive; these drives are usually
identical to their SCSI counterparts, but with different interface
electronics. As long as you don't use a controller with a custom BIOS
(such as the WD-1009), you can use Windows' 32-bit disk access for better
performance. While ESDI is generally somewhat slower than SCSI, the 32-bit
access capability far outweighs that difference.
...........................................................................
4.2.4. Video adapters
----------------------
Given Windows GUI orientation, a fast video adapter is essential for good
performance. In addition, a better video adapter can provide higher
resolution, higher refresh rates (for a steadier picture) and more on-
screen colors (for more realistic picture reproduction).
You should look for a card supporting a 70 Hz or 72 Hz refresh rate
(provided your monitor can handle that), and likely at least
A local bus or EISA graphics card will provide better performance, but the
difference is not as significant with accelerated cards as it is with dub
frame-buffer designs such as the ET4000 chipset. In general, don't pay
double just to get an EISA card!
The following will attempt to describe some of the high performance (i.e.
better than VGA) video adapters currently on the market. The descriptions
are frequently based on the chipsets rather than commercial product names,
as numerous vendors will market adapters using basically identical
hardware. All comments below are subjective and reflect the author's
opinion only. Do not base a purchase decision solely on this listing, but
always test a video adapter using your own applications prior to purchase,
END--cut here--cut here
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads