[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference jamin::pathworks32

Title:Digital PATHWORKS 32
Moderator:SPELNK::curless
Created:Fri Nov 01 1996
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:337
Total number of notes:1612

337.0. ""could not open log file" on install of pw32 alpha" by VMSNET::mtspc.alf.dec.com::Michael () Fri Jun 06 1997 10:45

A customer running autoplay from pw32 7.0 gets "could not open
log file" immediately after clicking "network connectivity". 
The system is an Alpha.   Running setup.exe from the alpha directory 
gives the same results.  He installed excursion with no problems and 
tried 3 different cds.

What gives?

Michael
T.RTitleUserPersonal
Name		DateLines
337.1Alpha, SETUP can't open/write logJAMIN::T_BROWNFri Jun 06 1997 11:5824
    Michael,
    
    
    -A customer running autoplay from pw32 7.0 gets "could not open
    -log file" immediately after clicking "network connectivity". 
    -The system is an Alpha.   Running setup.exe from the alpha directory 
    -gives the same results.  He installed excursion with no problems and 
    -tried 3 different cds.
    
    There needs to be some disk space on the c:\ drive for
    our log file (PWSETUP.LOG).  On most Alpha systems the 
    C:\ dirve is very small.  Excursion and/or Powerterm 
    eats up most of whatever is left.
    
    If a customer is prompted saying SETUP can't write to
    the log and is given the option to continue with logging,
    they should choose to continue without logging.  SETUP
    should install PATHWORK32 without a problem.
    
    If the log file can't be open and no options are given,
    have the customer free up some diskspace on the c:\ drive.
    
    Thomas Brown