User Interface
Recycle Bin
is an object…main property is setting % of hard drive may be used to store deleted files
(0% to 100%). When max % reached, deletes older files 1st until has enough space.
Taskbar - contains:
Start button
buttons for all active programs & utilities
notification area.
Add programs to Start Menu 3 ways:
1. from Settings/Taskbar/Start Menu Programs of Start Menu
2. Taskbar’s Properties/Start Menu Programs
3. Drag & drop object on the Start button
Activate Start button by clicking on it, CTRL+ESC, or Windows button on Win 95
keyboards.
My Computer contains Icons for every drive in the system, Control Panel folder,
Printers folder, Dial-Up Networking folder, and its Menu bar.
EXPLORER [/n] [/e] [root,<object>] [[,/select],<sub object>]
/n = Open new window
/e = Use Windows Explorer view (dual-paned Window)
Secondary mouse button:
Move Here, Copy Here, Create Shortcut(s) Here, Cancel
Keystroke combo to delete object without putting in Recycle Bin -- SHIFT/Del
Keystrokes to activate Start Button -- ALT/S or CTRL/ESC. (Or Windows
key on 104 key Win95 keyboard.)
Find feature (Start/Find/Files and Folders) - Can use several criteria:
? Name
? Time parameters, incl modification dates.
? Text contents
? Type of object
? Size
Programs that use the Windows 95 (Win32s) common dialog boxes allow you to create new
folders from within the Save As dialog box. Common dialog boxes also have browsing
capabilities.
What are properties of a shortcut?
Configuration info from the application referenced by the shortcut and how/where
it’s to be run.
Tips:
? Press ESC key during startup logo to view startup messages
? Type period (.) from Start/Run opens a windows to the desktop.
? Double click some items in notification area to bring up adjustment windows.
? Hold SHIFT while deleting object bypasses Recycle Bin
? SHIFT/Right Click on object adds “Open With” to the normal Right Click options.
Shutdown options:
? Shut down
? Restart (warm boot)
? Restart in MS-DOS mode
? Close all programs and log on as a different user
Installing & Configuring
Win95 Requirements:
? 386DX/20 or higher
? 4 Meg (8 Meg rec), 8 Meg required to use Windows Messaging or MSN
? 40 Meg disk space, 50-55 Meg typical, 35-40 Meg for typical upgrade.
Upgrade from DOS……DOS v3.2 minimum…v5.0 or later recommended.
If install Win95 over DOS, certain DOS files are deleted or renamed. Why? - Win95
has its own versions of files for same function, or they’re not needed.
Install Win95 over Novell DOS (DR-DOS)? NO!
For Dual Boot:
? Req. MSDOS 5.x or 6.x.
? Install Win95 in own directory.
? BootMulti=1 in MSDOS.SYS…may have to reinstall apps
Win95 / WinNT dual boot is possible, but not recommended.
Win95 can’t see NTFS partitions. WinNT can’t see FAT32 partitions. Win95
can’t be installed in same directory as WinNT or into shared WinNT/Win3.x directory.
Upgrade OS/2 to Win95? Yes!
But OS/2 partitions must be FAT….no HPFS.
Windows apps running in OS/2…transfer to Win95? NO! Must
reinstall apps.
Setup Options:
? Typical
? Portable (Dial up networking, Direct cable connect, and Briefcase. No accessories,
backup, games, Exchange, Internet)
? Compact
? Custom.
Install from:
? Floppy
? CD
? Network (source copy on server loaded with NETSETUP.EXE)
? Shared - (diskless - use copy on server…less disk space, control, but more network
traffic)
? Batch (push).
Setup switches:
? /is do not run ScanDisk from Windows
? /in do not install network components
? /d do not use existing version of Windows for early phases
? setup msbatch.inf specifies MSBATCH.INF as script installation file, if run from DOS.
If want then install:
Dual Boot Win95 to a different folder from Win 3.1/WFW 3.11.
Migrate Win3.x user environment and settings Upgrade Win3.x to Win95
Necessary to remove Win95 - on diskette:
UNINSTALL.EXE
Uninstall info: W95undo.dat & W95undo.ini
Log files:
? DETLOG.TXT *** record of devices setup finds after detection phase starts root
directory.
? DETCRASH.TXT binary record of detections used to avoid crash 2nd time deleted
after
? SETUPLOG.TXT record of successful and failed detections root directory
? NETLOG.TXT network components log <win_root>
Lockup during setup --- power off/10 sec/power on. Will pick up where left off,
skipping the problem device.
Deleting/Uninstalling Win95: From CP/AddRemove programs. Requires
W95undo… Must reinstall Win 3.x. Not in OSR2.
Control Panel - Major Icons (Programs) in it: (are
others)
? Add new hardware
? Add/Remove Programs
? Network
? Mail and Fax --- settings for Exchange (services, delivery, addressing)
? Microsoft Mail --- Administer an MS Mail workgroup post office. Not in OSR2.
? Multimedia
? Display --- Background, Wall paper, Screen Saver, & Settings and other. Also
from right click on desktop.
? System ---Device Manager, Hardware Profiles, Performance. Also from right
click on My Computer.
Hardware profiles.
Virtual Memory - CP/System/Performance/Virtual Memory.
Default is temporary swap file, Win386.SWP in Windows root folder.
If dual boot with WinNT, can use the NT swapfile, pagefile.sys.
Registry:
SYSTEM.DAT and USER.DAT in Windows root folder.
? HKEY_LOCAL_MACHINE - all global hardware and software settings - SYSTEM.DAT
HKEY_CLASSES_ROOT - OLE and file associations.
HKEY_CURRENT_CONFIG
HKEY_DYN_DATA (in RAM only, not the registry file)
? HKEY_USERS - all user-specific and application settings - USER.DAT
HKEY_CURRENT_USER - Created at run time from above.
FAT FAT32
Max partition 2GB 2048 GB
Cluster size for 2GB 32K 4K
Locally accessible from Win95, MSDOS, WinNT Win95 OSR2 only
Remotely accessible from all all
Drivespace Yes No
Long File Names
? “Alias” means the MSDOS 8.3 name.
? Max number of directory entries in root of a FAT partition is 512. LFNs deplete
directory entries faster.
? Copy, Edit, Backup destroy LFNs if performed on the alias.
? Copy, Edit, Backup & Restore can change 8.3 aliases.
? Some MSDOS utilities can destroy LFNs.
? LFNs are not available booting to command prompt.
Win95 uses tunneling to preserve LFNs.
Disk Compression:
? Compressed Volume File (CVF)
? CVF typically named DRVSPACE.000.
? CVF can contain only 512MB of data (uncompressed).
? CVF is 256MB for 2:1 compression.
? Adjust size of CVF depending on expected compression to get full 512MB and/or to not
waste space.
? Driver: DRVSPACE.BIN
? Token conversion and sector allocation granularity.
Also, DriveSpace 3. Boosts compressed space to 2GB, plus other features.
ScanDisk (SCANDISK.EXE & SCANDSKW.EXE)
DEFRAG.EXE is a Win16-based appl. Will not move hidden+system files or mounted
CVFs.
MSBACKUP (BACKUP.EXE) - not compatible with DOS or WinNT backup. Will do
“full” and “incremental” backups…not “differential” or “copies.”
System Agent (SAGE.EXE) - in Plus! And OSR2. Particular time-day-week-month or
during idle periods.
Plug and Play
PnP Functions
? Self-Identify & Self-Specify
? Dynamic Configuration changes
? Compatible w/existing systems and peripherals
? Independent of Operating System and Hardware
Docking - Types & When
? Cold Powered off
? Warm Reduced power
? Hot Full Power
- Auto-Eject
- Manual
Remember IRQs:
0 - System timer
1 - Keyboard controller
2 - Cascade to 9 / EGA/VGA
3 - Comm2
4 - Comm1
5 - LPT2 / -Avail-
6 - Floppy controller
7 - LPT1
8 - Real time clock
9 - Cascade from 2 / -Avail-
10 - Avail
11 - Avail
12 - PS/2 Mouse
13 - Math Co-processor
14 - Hard Disk Controller
15 - Avail
ISA/Legacy Detect Modes
? Safe - or passive - look in CONFIG.SYS, etc for clues.
? Invasive - calls to device it thinks it is…see if works.
? User
PnP Steps
1. Put in configuration mode
2. Isolate PnP devices and assign handle
3. Read resource data structure to determine requirements & capabilities
4. Allocate resources
5. Activate PnP cards
Sequence
1. Boot devices PnP or not
2. Non-PnP devices
3. PnP devices
PnP Components
1. Bus Enumerators (Win95 does not have for MCA or VL-bus) - assign unique id code
to each device on bus.
2. BIOS - configure, maintain data, notify
3. Hardware tree & registry
4. Operating System
5. Devices & device drivers
6. Resource Arbitrator
7. Configuration Manager
8. Applications
Supporting Programs in Win95
Know Preemptive and Cooperative Multitasking.
Know: Processes, threads, and primary and secondary schedulers
Thread scheduling is by priority.
? Are 32 priorities (0-31)
? Priorities 0-15 are Dynamic. Used for applications.
? Priorities 16-31 are Real Time. Used for Operating System.
DOS programs. W95 places the PIF in the same folder as the program. If not
found there, will search the <win_dir> folder, then the path, then finally APPS.INF.
Be able to explain a Virtual Machine.
Number of Virtual Machines is always “DOS + 1”
? Win16 applications run in the System Virtual Machine. All Win16 apps share a
single address space. Also share a common message queue. Single thread for each
Win16 app process. Are cooperatively multitasked among themselves. Are
preemptively multitasked as a whole with Win32 and DOS app threads. Configuration
settings in Registry or INI files.
? Win32 apps run in the System Virtual Machine. Each has its own memory space and
message queue. Multithreaded. Preemptively multitasked. Configuration
settings in Registry.
? Each DOS window (app) has its own Virtual Machine. Single thread for each.
Preemptively multitasked with Win32 threads, the active Win16 thread, and other DOS
threads.
Memory Management:
? Intel processor design follows a Ring Model
? Ring 0 is protected by the processor itself. Core WIN95 OS runs in Ring 0.
? Ring 3 protection is provided by the Operating System. All application run in Ring
3.
Win95 “stalls”
Core Win95 system code is non-reentrant. A process raises the Win16Mutex flag when
using the code.
All programs are governed by the Win16Mutex flag.
Win16 programs lower the flag when they check the message queue. But if a Win16
process using the flag is blocked from the Win16 message queue, it keeps Win16Mutex up and
blocks all programs - including Win32 processes - from using the system code.
Therefore, the system appears to stall (but it’s only foreground activity that’s
stalled).
Size of memory blocks for allocation and for paging - 4K.
How much memory accessible in Win95? - 4GigaBytes (GB)
What runs where in the 0 to 4GB range?
0K to 640K/1MB Real mode drivers, DOS apps, and Win16 Summary: DOS 0 to 1MB
1MB to 4MB Win16 Win16 0 to 2GB
4MB to 2GB Win32 (private address space), also some Win16 Win32 4MB to 2GB
2GB to 3GB Shared core system components, like DLLs O/S 2GB to 4GB
3GB to 4GB Kernel and other
Ring 0 software
Excessive paging??? --- Add more RAM!!!
MS-DOS Mode
Exit to DOS.PIF in Windows dir.
When in Win95…DOS boot configuration files are CONFIG.DOS and AUTOEXEC.DOS.
When in MS-DOS Mode, Win95 boot configuration files are CONFIG.W40 and AUTOEXEC.W40.
Obviously, CONFIG.SYS and AUTOEXEC.BAT are for the current OS.
Printing
Spool Files:
? Raw (device-dependent)
? Enhanced Metafile (EMF)
Note: Postscript is not EMF, but similar.
Spool files located in <win_dir>\spool\printer folder. Are two files spool
(.spl) and shadow (.shd) for each job.
for EMF, spl file point to EMF page files (.tmp).
Bi-directional printing support - needs:
? bi-directional printer
? IEEE 1284 cable
? bi-directional port. The port is also called an Enhanced Printer Port or Extended
Capabilities Port (ECP).
Bi-directional printing will use two modes. Compatibility mode for the 8 bit wide
parallel path from PC to printer. Nibble mode for the 4 bit wide signaling/status
path from printer to PC.
ECP capability must exist physically on the motherboard. Then enable ECP support
in Win95.
Networking Windows 95
Computer name - 15 characters max (NetBIOS standard). Set in
CP/Network/Identification.
Universal Naming Convention (UNC): \\Computername\Sharename\…
Win95 supports NDIS 3.1 drivers for network cards. Can also use NDIS 3.0, NDIS
2.0, and ODI (NetWare) drivers. Does not support NDIS 4.0 drivers from NT 4.0.
? NDIS 3.1 - protected mode, supports PnP.
? NDIS 3.0 - protected mode, nonPnP.
? NDIS 2.0 - real mode.
Win95 supports following (LAN) transport protocols:
? NetBEUI
? IPX/SPX Compatible (NWLink)
? TCP/IP
? DLC
For performance:
- A protocol can be designated as the default protocol. Use for the most frequently
used protocol.
- Disable unused bindings between Adapters and Protocols.
DNS, WINS (Windows Internet Name Service), and Gateway.
TCP/IP -- Remember:
? IP Address
? Subnet Mask
? Default Gateway
? WINIPCFG utility
? PING LOCALHOST (or 127.0.0.1) - pings self to confirm TCP/IP protocol at least active.
? IP Address entered locally or obtain from DHCP (Dynamic Host Configuration Protocol)
server.
? Use WINS (Windows Internet Naming Service) to resolve NetBIOS names to IP Address.
Alternative is a local LMHOSTS file. Specify IP Address of WINS server or to use
DHCP server for WINS.
? Similar for DNS (Domain Name System) used to resolve host computer/system names to IP
Addresses. Specify IP Addresses of one or more DNS servers to use.
Client for Microsoft Networks
? for connecting to: Win95, WFW, NT, LAN Manager computers
? Transport protocols: NetBEUI, IPX/SPX, TCP/IP
? File Sharing (higher level, Application/Presentation/Session layer) protocol is Server
Message Blocks (SMB).
? Compatible with clients as above, plus IBM LAN Server/Warp Server and DEC Pathworks.
To share local resources, must add the File & Printer Sharing for Microsoft
Networks service.
User-level security or share-level security, except if logging into Windows NT
domain. Then user-level security only.
Share access is: (Without WinNT domain logon)
? Read Only
? Full
? Depends on Password (one for each of the other two).
Access is by password defined for the share.
Can share printers. Share name: Printer$
Client for NetWare Networks
? for connecting to: NetWare file servers.
? Transport protocols: IPX/SPX only
? File Sharing (higher level, Application/Presentation/Session layer) protocol is NetWare
Core Protocol (NCP).
? Compatible with NetWare servers only.
To share local resources, must add the File & Printer Sharing for NetWare Networks
service.
User-level security only.
Share accesses are similar to “Custom” below for WinNT Domain user-level security.
Must add the File & Printer Sharing for NetWare Networks service.
Can share printers. See below.
A share name can be up to 260 characters, but only 1st 15 are seen over the network.
Remote Administration:
? Enable remote admin through CP/Passwords/Remote Admin tab.
? Two hidden shares: ADMIN$ (C:\) and IPC$ (gives and inter process communication
channel).
? NetWatcher to monitor share resources on any Win95 peer server. Install with
Add/Remove Programs.
? Workgroup model: 15 or fewer clients AND no real security requirements.
Is share-level security, no centralized admin.
? Domain or server-based model: More than 15 clients OR significant security
requirement. Is user-level security, has centralized admin.
Microsoft “browsing” and “browse lists:”
Part of Microsoft network design is each computer with any server or shared resource
broadcasts its presence. (Re)broadcast is every 12 minutes.
Each computer identified by its NetBIOS name.
One computer per network segment selected as “browse master” - maintains master browse
list.
Also backup browse master(s) with copy of list.
Master and backup browsers determined by an election among all computers on subnet.
Browse list is what shows up in Network Neighborhood. Also Microsoft NET VIEW
command.
Browse master updates its master list every 15 minutes.
Microsoft networks need a backup browse master for approx every 15 computers in a
workgroup.
If any computer goes off-line w/o normal shutdown, Browse Master doesn’t drop it from
list for 45 minutes (3 reporting periods).
All this part of File and Printer Sharing for Microsoft Networks service.
? Computer’s role in browse lists set by the Browse Master value: Enable, Disabled, or
Automatic.
? Can also configure computer for access to Microsoft LAN Manager clients through
LMANNOUNCE property value.
NT Interoperability
Log into Domain is a check/field on Client for Microsoft properties.
Assign logon scripts (.BAT files) with User Manager for Domains.
Domain login uses the domain security provider.
User-level security is the only option. Generates an access token with user’s
rights & permissions.
Enable User-level security on CP/Networks/Access Control tab.
NT Printing - supports Point & Print, but does copy drivers to local drive.
Must remove/reinstall printer for new driver. Implement by 1) dragging shared
printer icon from Network Neighborhood to Desktop or 2) to Printer Folder, or 3) by click
Install on network printer’s context menu.
Sharing creates ACL - stored in HKEY_LOCAL_MACHINE.
User vs Group Permissions: if in combination, User permissions override
Group’s. Different from NT, where is cumulative.
With User Level Security, Win95 assigns permissions to folders, not files:
? Read Only
? Full
? Custom
Explicit/Implicit permissions - permissions flow down the folder hierarchy unless reset
lower down.
Interoperability with NetWare
NetWare v2.15 and above.
Bindery based servers or NDS with bindery emulations.
NDS exception for Client for NetWare Networks from OSR2 or Service Pack 1.
IPX/SPX Compatible Protocol only. Can be bound to one adapter only, plus Dial-Up
Networking. (Dial-Up + 1)
Frame type settings:
? AUTO (Automatic detection)
? Ethernet 802.2
? Ethernet 802.3
? Ethernet II
? Token ring
? Token Ring SNAP
Plus some other settings.
Install Client for NetWare Networks. For NDS access, install Services for NetWare
Directory Services also. Don’t forget “context.”
For NetWare Point & Print: Add into to bindery
? Printer name & config
? Names of printer driver files
? Location of printer driver files.
Must be done by ID logged into NetWare as Supervisor or equivalent.
MSPSRV.EXE for despooling for NetWare print queues. (Acts like PSERVER. or
RPRINTER ?)
File & Printer Sharing for NetWare Networks requires:
1. IPX/SPX
2. Client for NetWare Networks
3. File & Printer Sharing for Microsoft Networks cannot be present.
4. A bindery NetWare server security provider.
Two properties to configure:
? SAP Advertising: Disabled for Win95 NetWare clients. Needed for real mode NetWare
clients.
? Workgroup Advertising: mist be enabled.
Must use user-level security. No World account access from unknown users.
Similar but different terms between NetWare and Microsoft for Delete, Change/Modify
Attributes, List Files, and Access Control.
Must access NetWare utility programs from and mapped drive….versus Microsoft.
User Profiles
In HKEY_CURRENT_USER in USER.DAT file of registry.
Enable profiles with CP/Passwords/User Profiles tab.
Note: Start Menu saved is optional.
Local User Profiles
Stored in local hidden folder named \windows\profiles\<user name>
Contains USER.DAT & USER.DA0
and directories for user prefs. (Desktop, Net’hood, Recent, Start Menu)
Roaming User Profiles.
? Stored on network server
? Always also updates local profile copy.
? Stored in user’s home folder on NT server, in SYS/mail/<user_id> on NetWare.
? (Note: to save Start Menu settings on NetWare, must have LFN support enabled - via OS/2
name space support.)
? Updated on server when user logs off.
? Time synchronization is important. Later time rules the update or not.
? NET TIME command to sync with NT.
Mandatory profile:
? Is a roaming user profile on server.
? rename user.dat to user.man.
? Must be available on all PDC/BDCs. Candidate directory for replication.
System Policies
Use templates for user categories.
POLEDIT utility. – needs a template file to get going.
System policies are registry settings set automatically when the user logs on.
Applied to any combination of:
? Computers
? Users
? Groups
Profiles vs System Policies:
? Mandatory profile can be changed for current session.
? Policy keeps users from the tools. More restrictive - or controlling.
? Policies are granular. Mandatory profiles are completely mandatory to all things.
? Mandatory profiles work when profile server is available.
But both change registry settings.
Policies applied to computer’s registry during logon:
? HKEY_CURRENT_USER: desktop settings …USER.DAT
? HKEY_LOCAL_MACHINE: login and network access settings … SYSTEM.DAT.
Stored in CONFIG.POL file: location:
? Stand-alone Win95 \<win_root> folder
? Win95 for Microsoft NETLOGON share of PDC
? Win95 for NetWare SYS:PUBLIC on preferred server
Policy File Mode vs Registry Mode
saved on server -- edit local registry files.
System policy file has registry settings:
? Checked - add to local registry
? Cleared - subtract from local registry.
? Grayed - setting not recorded in policy file or tool not installed.
System Policy Editor (POLEDIT) opens default policy template (ADMIN.ADM) in
\windows\inf folder.
Group policies - restrictions to NT Directory Services (NTDS) global groups or NetWare
groups.
? Group policy support must be installed on all computers
? Only applied of not policy exists for user
? Must be used with central security provider
? Can only be applied to existing groups.
Group policies downloaded in order by group priority - lowest to highest. Later
groups (higher priority) override earlier ones. So, implement the most restrictive
policies in the highest priority groups.
(System, User, Group ???)
Remember system policies relationship to load balancing. If load balance - policies
taken from logon server (controller) rather than from PDC only. Therefore, must
replicate policy file to NETLOGON share on all domain controllers. (NETLOGON is
\winnt\system32\repl\import\scripts folder). Implement load balancing in
<computer>/Network\Update\Remote Update in NT.
Dial-Up Networking
Remember LAN protocols (IPX/SPX, NETBEUI, TCP/IP) vs Line protocols (PPP, SLIP, RAS,
NetWare Connect)
2 PPP features that aren’t in SLIP: Encryption algorithm for user name
and password, Dynamic configuration of client TCP/IP, i.e. - DHCP.
Win95 dial-up client can connect to these dial-up servers:
? Win95
? WinNT
? WFW
? Novell NetWare Connect
? Shiva LANRover
? any other that supports PPP or SLIP
Then can use any and all LAN protocols supported by both client and server.
TAPI……. TAPI dialing properties stored in TELEPHON.INI in <win_root> folder.
Dial-Up Adapter appears in list of installed Network components in Net’hood /
CP/Networks. Is a network adapter driver that interfaces with Win95 communications
device driver. Makes it look to rest of network components that a network adapter is
being used rather than a modem.
Adapter bindings are to LAN (Network) protocols.
Explicit connections - started from Dial-Up Networking folder.
Implicit connections - started from an attempt to connect to a network resource that
isn’t available on the physical network.
Connect to a Win95 Dial-Up Server (comes in the Plus! Pack):
? PPP - any supported LAN protocol
? RAS - NETBEUI LAN protocol only
Connect to WinNT RAS server:
? PPP or RAS
? TCP/IP is supported
? Can use callback security
To an ISP:
? SLIP - does not support IP header compression, no error correction, no encryption, no
dynamic IP address (DHCP)
? PPP
? CSLIP
Connect to remote NetWare server:
? NRN: NetWare Connect line protocol
? IPX/SPX only
? no simultaneous connection to LAN NetWare server and dial-up NetWare server.
Win95 Dial-Up Networking Server
? Clients dial in using PPP or RAS.
? Clients: Win95, WinNT, WFW, Workgroup Add-on for MS-DOS, LAN Manager
? One client at a time only.
? Comes in OSR2, Plus!, …
? If use PPP, then NetBEUI or IPX/SPX.
? If use RAS, then NetBEUI only.
Challenge Handshake Authentication Protocol (CHAP)
? Specify require encrypted passwords.
? Uses “Three-way handshake::
Server sends challenge encrypted with private key.
Client decrypts with public key, encrypts with its private key - password, sends.
Server decrypts with public key and matches.
Modem troubleshooting:
? MODEMLOG.TXT - in <win-root> folder
? CP/Modems/modem/Diagnostics tab/More Info
? Can also enable connection log file, PPPLOG.TXT - connection and negotiation data. -
Dial-Up Adapter/Properties/Advanced tab.
Connect with Direct Cable Connection:
? One is host, other is client
? Host is also a router if connected to a LAN. Client can pass-thru.
? Requires IPX/SPX!
? Null modem serial or parallel (Std, ECP, UCM) cables.
Microsoft Exchange
Exchange is a central access point for all messages sent or received. Is MAPI
(Messaging A P I) compliant. Through MAPI, can communicate with any Email or
messaging system that is a MAPI service provider.
Exchange contains entries for various messaging resources: Information services,
Address books, Information stores.
Message profile consists of:
? Services
? Delivery
? Addressing
Can have multiple message profiles.
Under Delivery, incoming messages are directed to a single message store (per
profile). For outgoing messages, services are listed in the order they process the
outgoing message.
Install a workgroup post office on your Win95 machine with Control Panel/Microsoft Mail
PostOffice. \WGPO is default location for it.
Troubleshooting Win95 mail issues, first remove all services other than Personal
Address Book and Personal Folders…then add back each service provider one at a time.
File Synchronization / Briefcase
Can have more than one Briefcase on desktop. However, a Briefcase cannot be
shared between multiple users. Is for one user on multiple machines.
Install on portable computer for a docking station situation. Will synchronize
automatically (with network directory ??) when dock - if using PnP BIOS docking station.
Briefcase update will work across Remote Access connections. - or direct cable connect,
or …
Creates My Briefcase folder on desktop. Folder contains files, plus hidden (very
hidden!) files DESKTOP.INI and Briefcase Database.
Orphan file is a copied file that doesn’t have a master - probably either original
file deleted or file created in Briefcase.
Tuning and Optimizing Win95
System performance factors:
? Memory
? Processor Speed
? Hard Disk Speed
? Display Adapter speed
? Network adapter speed
? Protected mode vs real mode drivers.
System Monitor tool to monitor/profile system performance.
? Monitor real time performance
? Determine system capacity
? Identify bottlenecks
? Monitor effects of system configuration changes.
Can also monitor remote computers over the network. Remote registry service
required on the remote computer. Multiple computers simultaneously by starting
multiple copies of system monitor.
Key values to monitor:
? Kernel: Processor usage
? Kernel: Threads (count)
? Memory Manager: Page Faults (per second)
? Memory Manager: Discards and Page Outs - high indicates Thrashing - need
more RAM.
Network Monitor Agent
Optimization:
Virtual Memory:
? Each app can address up to 4GB of RAM (are virtual addresses)
? Total amount of virtual memory is sum of you computer’s RAM plus the free disk space
avail to the swap file.
? Swap file (WIN386.SWP) is dynamic. Can shrink or grow. Can be fragmented.
Can be on a compressed drive.
? Put swap file on best performing disk, unless it’s overused.
? Is on boot partition.
? Is temporary swap file by default. Can be permanent…can’t shrink below minimum
size. Rec to set max to total amount of free space on drive. Then will always
float maximum to what’s available.
Install rolls up all used VxD’s into VMM32.VXD
File Systems:
? Disk:
Select role for computer: Desktop, Mobile or docking station, Network Server.
Tip: if have more than 16Meg of RAM, set to Network Server.---- largest cache for files.
? CD-ROM:
Optimize access pattern:
? No read ahead - no CD caching
? Single - for 8Meg or less
? Double - 8-12 Meg
? Triple - 12-16 Meg
? Quad or higher - more than 16 Meg.
Overall as a network client:
? Use 32bit protected mode network client s/w
? Use protected mode NDIS 3.1 NIC drivers
? Get faster adapter….32 bit (PCI) NIC
If running File & Printer Sharing, set read-only attribute on files whenever
possible. Network caches only read-only files.
Troubleshooting Win95 Boot Sequence
Boot files needed:
? c:\io.sys Boot into real mode. Loads real mode drivers & TSRs from CONFIG.SYS
& AUTOEXEC.BAT.
? c:\msdos.sys Controls boot process for compat with old apps. Must be at least 1KB
in size.
? c:\config.sys Set system environment variables, load real mode drivers and TSRs.
? C:\autoexec.bat Specify commands to execute in real mode.
? <win_dir>\win.com Start win95 load phases.
BIOS Bootstrap:
? POST
? PnP devices identified and configured
? Master Boot Record (MBR) located.
Master Boot Record - determines bootable partition, passes control to boot sector in
it.
Boot Sector - has disk boot program and disk characteristics.
Disk Boot Program - finds root directory, copies IO.SYS into memory and passes control to
it.
Real Mode Boot:
1. *Loads minimal FAT file system in order to load additional OS components
2. *Reads MSDOS.SYS for boot config parameters
3. *Displays Starting Windows 95 and waits for ‘x’ sec (dafault=2) for function keys -
like F8, or F4 or F5…
4. *Loads and displays bitmap stored in logo.sys, or io.sys (the clouds win95 image) if
logo.sys doesn’t exist. ESC disables logo.
5. *Loads DRVSPACE.BIN for compresses drives, if DBLSPACE.INI present.
6. Checks SYSTEM.DAT
7. Loads SYSTEM.DAT or SYSTEM.DA0
8. SCSI stuff
9. Selects hardware profile from registry based on detected hardware
10. Reads and processes CONFIG.SYS, COMMAND.COM, and AUTOEXEC.BAT.
* - important steps for test.
Real Mode Configuration:
Loads drivers in CONFIG.SYS. If no CONFIG.SYS, loads HIMEM.SYS, IFSHELP.SYS,
SETVER.EXE
Protected mode load:
? WIN.COM after AUTOEXEC.BAT
? Loads VMM32.VXD and other virtual device drivers per registry and system.ini.
? Switches processor to protected mode and initialized VxDs
? Then loads rest of kernel, plus services, user libraries, and the desktop.
Startup Menu:
F8 while “Starting Windows 95” on screen.
Options:
Normal
Logged (bootlog.txt)
Safe Mode
.
.
.
Previous version of MS-DOS
MSDOS.SYS - text file…must be at least 1024 bytes for compatibility with virus
programs and DOS apps.
Key entries:
BootDelay=n Startup delay in seconds.. Default 2
BootKeys= 1 enabled (def) or 0 disabled.
BootMenu= 0 disabled (def) or 1 enabled
BootMulti= For dual boot. 0 disabled (def) or 1 enabled.
LoadTop= Loading of command.com or drvspace.bin at top of 640K. 1 enabled
(def). 0 disabled for some NetWare conflicts - like on win95 set to load NETX or
VLMs before Win95 starts.
WIN.COM switches: win /d:?
/d:f Turn off 32 bit disk access. Use if computer seems to have disk problems or if
Win95 stalls. Like 32BitDiskAccess=FALSE in system.ini.
/d:s Don’t use ROM address between F000:0000 and 1MB for break point. Use if
Win95 stalls. Like SystemRomBreakPoint=FALSE in system.ini
/d:x Exclude all of adapter area from range Windows uses. For upper memory conflict with
devices that load into upper memory. Like EMMExclude=A000-FFFF in system.ini.
/d:m Safe mode
/d:n Safe mode with Networking
/d:v ROM routine to handle interrupts
*** 1st three real important to remember for test.
Driver Load Failures --- see bootlog.txt
Driver Initialization Failures --- look for SYSCRITINIT in bootlog.txt.
Safe Mode loads only mouse, keyboard, standard VGA, and drivers required for Device
Manager.
No registry, CONFIG.SYS, AUTOEXEC.BAT.
No load= or start= lines from win.ini.
If normal mode doesn’t work but safe mode does, likely:
? Network Configuration disable network (by removing) then recreate.
? Protected Mode disk driver
? Video driver
? Third party VxDs comment out 3rd party VxDs 1 by 1 until find it.
Troubleshooting
*WILDCARDS* - Very common problems categories and usual answers:
Hardware - Add RAM
Registry - it’s in HKEY_LOCAL_MACHINE
IPX/SPX - Frame Type
Every successful start, Win95 backs up registry by copying .DATs to .DA0.
Can copy DA0 files back to recover last successful settings.
Export and Import - branch or entire registry.
Real mode REGEDIT.EXE. Use Win95 startup disk to start, then import a .REG file.
Another option for backing up registry: Microsoft Configuration Backup on win95
CD. Make periodic backups. Maintains up to nine (9) backups. (Does not
back up profiles or policies.)
Emergency Startup Disk - boot diskette. Boots MS-DOS mode. Normal files,
plus EBD.SYS.
Disabled (with an X) or problem state (exclamation point) devices in Device Manager.
- Disabled is physically present but no driver loaded.
- Problem state had Win95 load a driver but failed, or is in conflict.
Resources tab displays system resources: IRQ assignments, I/O ports, DMA channels,
Memory addresses.
For conflicts, if stumped, take everything out and re-add 1 by 1.
Troubleshooting remote computers. With Registry Editor and System Monitor.
Requires:
1. Both computers must support user-level security.
2. Remote Registry services must be installed on both.
3. Remote Administration must be enabled (CP/Passwords/Remote Admin tab)
4. User name must be in list of administrators on Remote Admin tab. Or if NT -
Domain Admins group, NetWare - Supervisor or equivalent.
Remote Registry is a service installed through CP/Network
Deploying win95
5 or less installs - use CD or floppies.
More than 5 - use a push installation from a network server.
More than 5 with same configuration - use batch scripts. Can combine with push for
complete automation.
Installation location:
Local (hard drive)
Shared (on network server)
Server-based Setup: NETSETUP.EXE from Win95 CD.
Make Script in SBS to create MSBATCH.INF.
|