| T.R | Title | User | Personal Name
 | Date | Lines | 
|---|
| 253.1 | A marketing edge! | PCBUOA::WHITEC | Parrot_Trooper | Wed Apr 16 1997 15:28 | 5 | 
|  |     Might just be a compaq design flaw!!! ;^)  
    
    Do they control their laptop HAL like their servers?  Could be it.
    
    chet
 | 
| 253.2 | No CD - Still Broken! | ALFSS2::OLSEN_G | Real Men Go Wireless! | Thu Apr 17 1997 15:29 | 9 | 
|  |     Chet,
    
    Customer copied the mw_wa_us folder to his hard disk - ran setup and it
    gives him the same error. No CD involved.  Again - works fine on
    another PC. 
    
    HELP!
    
    Gary
 | 
| 253.3 | i will verify | PCBUOA::WHITEC | Parrot_Trooper | Fri Apr 18 1997 07:37 | 6 | 
|  |     
    Will ask engineering, but I understand compaq builds their own HAL,
    this could be a problem?  Manageworks et al, is designed and tested on
    INTEL platforms.....running Windows with the Windows HAL.
    
    chet
 | 
| 253.4 | HAL can't be an issue | ALFSS2::OLSEN_G | Real Men Go Wireless! | Mon Apr 21 1997 09:36 | 14 | 
|  |     Chet -
    
    What does the HAL have to do with simply expanding a file. None that I
    can see - but then I have no idea why it won't expand it on this one
    machine and it will on others. Can't be a compaq problem or we surely
    would have heard of it by now.  I suspect something related to this
    particular PC - I suspected corruption but it works on other PCs so
    that doesn't seem to be a problem. Scanned for viruses - it's clean.
    Thought about resources - disk space, but it has a gig of free space
    and tons of memory.
    
    Any other ideas?
    
    Gary
 | 
| 253.5 |  | SUTRA::16.36.2.155::Bats | Speeding, speeding, I'm always speeding | Tue Apr 22 1997 11:48 | 9 | 
|  | 
	But then ServerWorks install uses Installshield to do the
	expansion. This is about the most standard installation
	tool which exists.
	There must be something weird on this box.
	What? Sorry no idea either.
	Pjotrr
 | 
| 253.6 | SOLUTION! | ALFSS2::OLSEN_G | Real Men Go Wireless! | Thu Apr 24 1997 10:44 | 8 | 
|  |     Finally solved it by deleting c:\windows\temp and adding c:\temp.
    We ran scandisk and norton utilities - disk reported no errors.  For
    whatever reason, setup couldn't write to c:\windows\temp first because
    we created c:\temp and still got the error - until we deleted the
    windows temp directory (not just the files in it but the directory
    itself.
    
    Gary
 |