Win 95 features
Support preemptive multitasking. Doesn’t support multi processors.
Compatibility with MS-DOS & Win-16 bit.
Compatibility with Legacy hardware.
Plug & Play. (NT doesn’t have it).
FAT (Up to 2GB) / FAT32 (OSR2 only, up to 2 TB).
Minimum hardware requirements: 386DX/20, 4 MB RAM (8 recommended), 40 MB (for typical),
VGA, MS-DOS 3.21 / Win 3.1 / OS/2.
Installation: New: 50-55 MB, Typical: 35-40, Upgrading from Win 3.1: 20MB, Upgrading
from Win 3.11: 10-20 MB.
Dual Booting
With MS-DOS
Minimum – MS-DOS 5.x.
Install Win 95 in its own directory.
F4 key during boot sequence.
BootMulti=1 in MSDOS.SYS file.
With Win NT
Must be FAT (NT cannot access FAT32 & Win 95 cannot access NTFS).
Setup Options
Typical: Default.
Portable: For mobile computer. Installs: BREIFCASE, DUN.
Compact: For limited disk space.
Custom: Based on user selection.
In order to uninstall Win 95 you should install it to an existing Win 3.x
directory.
The Setup Process
The Log Files
DETLOG.TXT: Created once Win 95 is installed, logs devices found during the
detection process.
DETCRASH.LOG: This is the binary file for DETLOG.TXT, created if the detection
process stopped. Logs successful steps, so the computer won’t crash on the same
problem. When hardware detection finishes - DETCRASH.LOG is deleted.
SETUPLOG.TXT: Created once Win95 is installed, during hardware detection failure.
Logs failures & success. Before hardware detection begins - SETUPLOG.TXT determines
the point of failure.
NETLOG.TXT and BOOTLOG.TXT created as Win starts up
the first time.
(When Setup reaches 20% - it’ll ask for floppy to
make Start up disk).
To troubleshoot the setup process
(and everything else in life) use "FIT"
F ind the problem, Isolate it, Test
the solution.
Emergency Startup Disk (ESD)
Can be created during windows setup, or by Add/Remove
Programs icon in Control Panel, after installation. Contains several files like
– Command.com, Fdisk.exe, Msdos.sys etc. Recommended add-on files: System.dat,
System.ini, Win.ini etc.
Troubleshooting
If setup halts during hardware detection
Turn off the computer, wait 10 sec. Don’t press
CTRL-ALT-DEL. Choose “Use Safe Recovery” option. Windows skip the
portion of the problem.
- If computer locks during restart
- Boot into Safe Mode (F5 at startup / win/d:m at command prompt), and/or
- Remark out lines in the Config.sys file (conflicts with real / protected mode drivers),
and / or
- Check network components for improper configuration.
- F8 at startup and choosing one of the options: Logged, Safe Mode, Step-By-Step
Confirmation etc.
- Try win.com switch: win /d
Win 95 Switch Options
Option |
Meaning |
Win
/d: F |
Turn off 32-bit disk
access. |
Win
/d: M |
Safe Mode. |
Win
/d: N |
Safe Mode with
Networking. |
Win
/d: S |
Doesn’t
use F000:00000-1 MB ROM address (use it if windows stalls during system startup). |
Win
/d: V |
ROM routine will
handle HD interrupts (use it if windows stalls during system startup or disk operations). |
Win
/d: X |
Exclude adapter area
from memory windows scans for free space (upper memory conflicts). |
Uninstalling
Simply deleting Win 95 may not work. You must uninstall
it.
- Uninstalling Dual-Boot computer restores the previous MS-DOS/win 3.x
- Uninstalling on upgraded (win 3.x) computer requires reinstalling win 3.x
- Uninstalling is not possible with Win 95 OSR2.
Conditions for Uninstalling
Saving system files during setup (W95undo.dat & W95undo.ini exist).
No compression of the system and/or boot partition after Win 95 installation.
Procedures
From Install/Uninstall page of Add/Remove programs (Control Panel).
Uninstall.exe from startup disk.
Uninstall.exe from command prompt.
Hardware Profiles
You can create several hardware profiles for your
computer, mobile computer, or different users.
Creating new hardware
profile:
- Right-click My Computer, click Properties, click Hardware Properties,
copy to new profile name.
- In Device Manager tab – double-click a device, select/deselect device
from one of the profiles you created.
- When booting the computer – you can choose either of the profiles.
PC card (PCMCIA)
After installing PC card, the PC card icon appears in Control
panel. From PC card properties you can:
- Stop the PC card, if you want to remove it.
- Configure PC card icon to appear on the Taskbar (stop it easily).
- Display warning if the card is removed before it’s stopped.
Configuring Virtual Memory
Virtual Memory is a combination of RAM & hard disk
space (swapfile). The swapfile is Win386.swp, in \win_root
directory. It can be on compressed disk, if DRVSPACE.VXD exists, and controls the
compressed disk. In networked computer the swapfile can be in the computer directory on
the network. The swapfile is a dynamic file. Each program can use up to 4 GB (actual &
RAM).
If dual-booting with Win NT – you can use the NT
swapfile (Pagefile.sys), by adding PagingFile=<drive_letter>:\pagefile.sys to
[386Enh] section in system.ini.
Manually configuring the swapfile can be done through:
Virtual Memory button on Performance tab in System,
on Control Panel.
If you have drives C:\ and D:\, and you install Windows 95 on
D:\Windows, then Win386.SWP will be on the root of D:\. Otherwise, it will be placed on
the win_root.
The virtual memory allocation
Memory Area |
Used for |
0–640
KB |
If not used for a Virtual DOS
Machine (VDM), this memory is made available for any real-mode device drivers and TSR
programs. |
0–1
MB |
In a VDM, this memory is used to
execute MS-DOS programs. If a 16-bit VM is used, then 16-bit apps operate much as they do
under Windows 3.1. |
1–4
MB |
Normally this memory is unused.
Windows 95 doesn’t use this space, nor do 32-bit apps. If this memory is needed
by 16-bit apps, it is available. |
4
MB–2 GB |
32-bit apps and some 16-bit apps
use this memory. Each 32-bit app has its own address space, whereas 16-bit apps all share
a common address space. |
2–3
GB |
This memory is used to run all Core
System Service components, shared DLLs, and other shared objects. Those components are
available to all applications. |
3–4
GB |
This memory is reserved for all
Ring 0 components, such as the File Management subsystem and the VMM subsystem. Any VxDs
are loaded in this address space. |
The Registry
The registry is a database, used for storing software
& hardware settings. It can provide local and remote support for system configuration.
Because 16-bit applications still use INI files, Win 95 support INI files for
compatibility with those applications. Old programs that use INI files will continue to
use these files. The registry built during setup & updated if changes are made to
devices or software. It is made up of two files: SYSTEM.DAT
& USER.DAT, in win_root folder.
- SYSTEM.DAT
contains computer specific configuration.
- USER.DAT
contains user specific configuration.
The registry is a hierarchical structure, with six subtrees. Its
components are subtree, keys
& values.
The Registry Structure
SUBTREE |
NOTES |
SUBKEYS |
HKEY_LOCAL_MACHINE |
Global hardware & software
settings for every installed device & application. |
Config :
hardware profiles. Enum: installed devices. Hardware: CPU vendor, port/modem info. Network:
logged user info, system policies. Security: network security
provider. Software: apps & component’s info. System: installed devices & configuration. |
HKEY_USERS |
User specific system & program
settings for each user logged to the computer. |
|
HKEY_CLASSES_ROOT |
OLE & file association. |
(From HKEY_LOCAL_MACHINE) |
HKEY_CURRENT_CONFIG |
Current config, for different
profiles or mobile computers |
(From HKEY_LOCAL_MACHINE) |
HKEY_DYN_DATA |
Dynamic status, for PnP &
system info from SYSMON. |
|
HKEY_CURRENT_USER |
User specific settings (color
schemes etc) |
(From HKEY_USERS) |
You can edit the registry with Regedit.exe
(in win_root). The Connect Network Registry command is used to remedit the
registry. The Microsoft Remote Registry service must be on the remote computer and you
user-l.
Each time Win 95 successfully starts, it is copying the current
SYSTEM.DAT and USER.DAT files to SYSTEM.DA0 and USER.DA0. If Win 95 fails to start, the backed-up Registry from the
last successful startup can be copied over the current Registry.
Import/Export commands allow you saving registry
data in a REG text file and restoring it when necessary.
FAT / FAT32
Win95 uses FAT16 (up to 2 GB disk). OSR2 can use
FAT32 (up to 2 TB).
FAT16 / 32 Comparison
Feature |
FAT16 |
FAT32 |
Max partition size |
2 GB |
2 TB |
Cluster size |
32 K |
4 K |
Accessible locally |
95, NT, DOS |
OSR2 only |
Accessible remotely |
95, NT, DOS |
95, NT, DOS |
DriveSpace compression |
Yes |
No |
95 Scandsk, Defrag etc |
Yes |
Need update |
Partitions
Fdisk.exe used to partition
hard drives. With Fdisk.exe you can Create or delete: primary, extended or logical
partitions and designate an active partition. Fdisk cannot
delete NTFS logical drives in extended partition.
Primary partition:
active partition, used by the system to boot. (Up to 4 Primary partitions, only one can be
active). Cannot be subpartitioned.
Extended partition:
created from free HD space. Can be only one. Can be subdivided into logical drives.
When deleting partitions, you must keep this order:
- Non-DOS partitions.
- Logical drives in extended partition.
- Extended partition.
- Primary partition.
Formatting
Quick: erases directory table. Doesn’t erase data from disk.
Full: erases all data from disk.
Copy system files: copy system files & create boot sector.
Long File Names
–LFN
Max of 250 characters, max entire path length – 260.
LFN uses the first 6 characters of the name (Uppercase), adds tilde (~), a number and
extension. The extension composed of 3 characters following the final period in the name.
Long File Name Examples
File name |
Long file
name conversion |
“This is a long file
name.document.txt” |
THISIS~1.TXT |
“This
document.is.created.by.doc” |
THISDO~1.DOC |
Another “This
document.is.created.by.doc” |
THISDO~2.DOC |
Possible problems with LFNs
LFN not supported when booting to command prompt. (But supported from within Win
95 MS-DOS prompt.
Some MS-DOS utilities destroy LFN.
Using copy, edit, backup etc might change the alias
(“LONGFI~1.TXT”).
Using copy, edit, backup etc on the alias can destroy the LFN.
512 entries in the root are possible, but LFN uses more than one entry per file name, so
it’s recommended being conservative in the root directory.
This summary is not completed. I'm
working on it, and hope it'll be over soon. Any advice or suggestion is welcome! If you
wish to contribute to this page, I'll be happy to get any kind of help. I hope this little
project will help all of you guys out there!
Please feel free to send any kind of feedback here, to
my e-mail
|