Well without knowning the specifics of the users machine... there's
a lot of variables so there is no correct, it takes x seconds to load.
However if startup is longer than 1 minute something is hokey (on my
machine 2001 starts in 18 seconds). I would suggest the following...
(1- re emphasize problem with Mcaffee, most cases it turns out to be
this even when customer already said it's not. 2 - check various system
settings such as free disk space, available memory, etc. 3 - If problem
still exists run attached test program. This will tell us exactly how
long it takes to load Rose and give us a MS diagnostic report. In this
report we can see such thing as available memory and whether or not they
really did nuke McAfee, etc.) If you are still having problems with
this after going thru the following let me know and send me the report.
#1 Check known issue with McAffee Virus checker
#2 Check system
#3 Run test program and get system info.
###################################################################
#1 Check known issue with McAffee Virus checker
###################################################################
Known problem with McAffee Virus checker.
First test would be to disable this.
-------------------------------------------------------------------
RBU DefectID: 11555 : Problems with McAffee need to be added to
release notes
Priority _______ 2 - High Attention
Severity _______ 2 - Major
Type ___________ defect
State __________ assigned
Notes::
McAffee virus scan causes Rose startup to perform like a dog.
It also causes the installation to perform like a dog.
We're not the only product - Word, etc. perform like a dog,
primarily because
McAffee is checking the executable modules (e.g. dll's) as they get
loaded.
-------------------------------------------------------------------
More information regarding Rose startup delays that we wanted to
pass along to you. The change McAfee made that impacts us the most
is that they are now scanning *.ini files as they are accessed.
As you may know, Rose stores a significant amount of information in
the rose.ini and stereotype.ini file, as well as ini files used by
different Rose Add-ins. Rose accesses keys in these ini files using
the standard windows calls, which, unfortunately open, search, and
close the ini file every time we query for a key from a file. This
means that McAfee scans the complete ini file every time we attempt
to read a key, literally 100s of times for some of the files. This,
in addition to the dll scanning that is exacerbated by Rose's high
level of componentization as discussed in our previous mail, is
what is causing the slowdown in Rose startup.
The best solution we can offer now is to disable scanning of ini
files in McAfee. To do this follow these steps
1. Go to the system tray and double-click on the Vshield icon (the one with
the V).
2. Click on "Properties" in the system scan dialog.
3. In the Properties dialog, make sure that the Viruscan is scanning for
"Program files only"
4. Click on the "Extensions" button.
5. In the "Program File Extensions" dialog, find the INI extension in the
dialog and click on the "Delete" button.
6. Click "Ok" in the dialog to leave the dialog.
7. Click "Apply" in the Properties dialog to save the changes.
###################################################################
#2 Check system
###################################################################
------------------------------------------------------------------
CLOSE _ALL_ OTHER APPLICATIONS
ELIMINATE POSSIBLE CONFLICTS
Other programs that are loaded use resources that could be taking
away from or conflicting with one another. To check for other
programs that are loaded, Press CTRL ALT DELETE. A Windows NT
Security dialog box will appear. Click Task Manager. Under
Applications, click an item, and click End Task.
Make sure any virus checking program currently running is
disabled.
Disable any screen saver currently running.
Click Screen Saver. Set the Screen Saver to None.
------------------------------------------------------------------
DISK ISSUES
- Disk Errors?
To check for disk erros run CHKDSK or another similar utility on
any drive in question. If you are using the FAT file system, use
Scandisk, or other MS-DOS based hard drive utilities.
- Free up disk space:
How much free disk space is on your windows drive? Lack of free
disk space for windows to do memory swapping can lead to
peformance problems. In general with NT you should have a minimum
of 2.5 x <installed memory>. For example on a 64meg machine you
should have at least 150meg free disk space. Also be aware that
disk drives slow down when > 80% full.
- Temp files:
All applications require an area of hard drive space to be set
aside for the creation of temporary files used during the course
of normal operations.
Windows NT 4.0 allows you to specify the location of your Temp
folder. This TEMP folder must be located on a drive with ample
space for expansion. If the drive where the TEMP folder is located
has less than 150 MB of free space, relocate the TEMP folder to an
uncompressed drive by modifying or constructing appropriate
statements.
To do this, click Start, Settings, Control Panel.
Double click the System icon and click the Environment tab.
Consult the Windows documentation for information on changing
these variables.
Note:
The recommendation of 150 MB is a MINIMUM and should be increased
if working with memory intensive applications.
Clean up old temp files.
To find where TEMP points to either go to a DOS prompt
and type SET, or
Control Panel, System
Delete all files in the Temp directory.
Go to a DOS prompt and type 'set' to determine where temp files
are being created. Set should show you something simular to the
following:
C:\>set
TEMP=C:\WINNT\TEMP
Delete files with dates older than today from the Windows
directory:
After freeing disk space defragment the hard disk.
There are commercial products available with a free limited or
trial version available: Norton's Speed Disk (part of Norton
Utilities), Diskeeper, and PerfectDisk NT.
------------------------------------------------------------------
NETWORK RELATED?
Model files local or remote? If remote does problem continue if
models are copied local?
------------------------------------------------------------------
USE WINTUNE TO IDENTIFY AND FIX COMMON PROBLEMS:
Wintune 97 for Win95 version 1.0.
Wintune 97 for WinNT version 1.0.
Wintune 97 for Windows 95/NT is WINDOWS Magazine's test and tune-up
kit for analyzing and optimizing Windows 95/NT. Wintune 97 examines
your system's performance by testing the CPU, video, disk and
memory components. It analyzes the results and advises you as to
how to get the best out of your system. Wintune can also detect
common Windows 95/NT configuration problems and give you specific
instructions for fixing them.
Author: CMP Media Inc.
Home Page: www.winmag.com/software/wt97.htm
Date: April 1, 1997
File Size: 995kB
Category: System Utilities
License: Free
Requirements: Windows 95/NT.
------------------------------------------------------------------
WINDOWS NT PERFORMANCE MONITOR
Check the Windows NT Task Manager Performance utility to do an on
the fly check of avaiable resources.
Use Windows NT Performance monitor to see if you can identify the
bottleneck. See NT documenation for help on using Performance
Monitor.
Additionally check out the following technical notes for help on
using the Performance monitor and steps to indentify and optimizing
NT systems.
http://support.microsoft.com/support
Gathering Information for Troubleshooting Performance Issues
Article ID: Q175658
How to Create a Performance Monitor Log for NT Troubleshooting
Article ID: Q150934
http://www.hadler.com/SUPPORT/246.htm
Optimization and Tuning for Windows NT Server
http://k9.dv8.org/~dcoker/readings/258e.html
Subject: Optimization and Tuning for Windows NT Server
http://www.gasullivan.com/boerg/00000/000b3.htm
Chapter 33
Optimizing Windows NT Workstation Performance
------------------------------------------------------------------
BOOT WITH CLEAN AUTOEXEC.NT AND CONFIG.NT FILES OR AUTOEXEC.BAT
AND CONFIG.SYS FILES if you have these on your machine.
NT doesn't need either of these files, but will create a 0 byte
file for each of these since some 16-bit programs may still use
them.
If you have information in these files, try Remarking (REM) any
nonstandard lines in the existing files to determine if anything
in this file may be the source of the errors. If you are unsure of
what any line does, DO NOT DO THIS. Some machines may use disk
compression or have needed disk drivers in these files.
------------------------------------------------------------------
INCREASE AVAILABLE MEMORY:
Go to your control panel and under performance, increase
your swap file from whatever to 100Mb for both the minimum and
maximum thresholds. As a general recommendatation make sure
Virtual memory should be 3x RAM. i.e. 256mb RAM = 768mb Virtual
Memory.
Control Panel
System
Peformance Tab
Virtual memory
Initial size
increase to something greater than current size, something larger
that currently recommended size.
Eliminate unused fonts. Fonts are stored in memory, which
reduces what's available for other purposes.
------------------------------------------------------------------
###################################################################
#3 Run test program and get system info.
###################################################################
1. Shut down your machine, and restart.
2. Ddisable any other running software that might be suspected
as being part of the problem then run the attached VB program
rose_test.exe.
This file will
- create a MS Diagnostic summary report by running
MS NT utility winmsd and output it to the location of
this file (rose_test.exe).
Filename will be <machine_name.txt>.
- Load and start Rose, and send back a msgbox with amount
of time it took. After opening Rose, minimize Rose, and you should
see this msgbox.
How long does it take on your machine?
And could you please send us back the report file from winmsd.
'''''rose_test.exe''''''''''''''''''''''''''''''''''''''''''''''''
Sub TimeDiff(Time1 As Date, Time2 As Date)
'Function TimeDiff(Time1 As Date, Time2 As Date) As String
Dim Seconds1 As Integer
Dim Minutes1 As Integer
Dim Seconds2 As Integer
Dim Minutes2 As Integer
Dim NumSecs As Integer
Dim MinPart As Integer
Dim msg As String
Seconds1 = DatePart("s", Time1)
Minutes1 = DatePart("n", Time1)
Seconds2 = DatePart("s", Time2)
Minutes2 = DatePart("n", Time2)
MinPart = (Minutes2 - Minutes1) * 60
NumSecs = MinPart + (Seconds2 - Seconds1)
msg = "The Elapsed Time to load was " + Str$(NumSecs) + " Seconds"
MsgBox (msg)
End Sub
Private Sub Command1_Click()
Dim aClass As Object
Dim allClasses As Object
Dim roseApp As Object
x = Shell("winmsd /s")
Dim Time1 As Date
Dim Time2 As Date
Dim NumSecs As Integer
Time1 = Time
On Error Resume Next
Set roseApp = GetObject(, "Rose.Application")
If roseApp Is Nothing Then
Set roseApp = CreateObject("Rose.Application")
End If
'When you call GetRoseApplication the first time, the value
'of roseApp will be Nothing and GetObject will be
'attempted. If GetObject fails, then a new instance is
'created using CreateObject. From that point on you will be
'using the same instance of Rose's automation server.
'If you relied on GetObject, your program would break if the
'user opened another instance of Rose.
roseApp.Visible = True
' roseApp.openmodel "c:\temp\test.mdl"
Time2 = Time
TimeDiff Time1, Time2
End Sub
''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
Data
