| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1677.1 | please any help??? | ISIDRO::ELSA | | Fri Nov 11 1994 11:01 | 15 |
|
Hi,
Please someone have any idea of this problem.
This customer received hubtwatch 2.0 for windows, and the
installation failed. We send Hubwatch 3.1 for windows in
order to solve the problem and this fails too.
Thanks.
Elsa Soengas
MCS Spain
|
| 1677.2 | please help??? | ISIDRO::ELSA | | Fri Nov 11 1994 11:12 | 20 |
|
Hi,
The steps in order to reproduce the problem are the following:
a) c:\win
b) choose principal icon and select the file manager
c) put the diskette 1 of hubwatch
d) INSTALL
e) choose install hubwatch and network
f) begin the installation
g) when arrives to install icon in hubwatch window group
after of select it gives the error
Thanks in advance,
Elsa Soengas
MCS Spain
|
| 1677.3 | Resource related | NETCAD::WAGNERCOFFIL | | Fri Nov 11 1994 12:58 | 16 |
| It sounds like a resource related issue.
If you have multiple things running when you are installing HUBwatch
for Windows 3.1, try closing the other applications and windows.
You should check Memory uasage(type MEM at DOS prompt from in Windows).
Also, check the following configuration and initialization
files c:\AUTOEXEC.BAT, c:\CONFIG.SYS, c:\windows\WIN.INI, and
c:\windows\SYSTEM.INI.
Check the settings in these files and drivers being loaded.
See if you can disable something. Check BUFFERS and FILES values
in c:\autoexec.bat.
Barb
|
| 1677.4 | you may not believe this, but | OREGUN::GREGORYDA | David Gregory, MCS, Portland, OR | Fri Nov 18 1994 23:34 | 18 |
|
I had a very similar problem.....
(I forget what line it died at, but it was very repeatable - o yea -333!)
Not only do all the files need to be in the SAME directory, when installed off
of a hardisk, but the problem is much more evident on a FASTpc - the customer
had 66mhz pc's. (My laptop has never dreamed of 66mhz!)
Fortunately, DEC has only issued me a laptop 320pc, and after putting
all the eggs into one sock, it all installed, without failing at line 333.
The statement ..GET QUEUED FILES appears to arrive before there are any
queued files to be had.... another, of the many, DOS/Windows interop
problems solved.
- dg
|