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

Conference akocoa::decpc_portables

Title:DECpc _Portables
Moderator:PCBUOA::GLANTZ
Created:Wed May 08 1991
Last Modified:Thu Jun 05 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2423
Total number of notes:11059

2413.0. "Is there a problem with FIS on VP575 Win95 Systems?" by WHYNOW::NEWMAN (Protector of the Cause) Sat May 24 1997 14:56

    We are starting to wonder if there is a problem with the Windows95 FIS
    Software being shipped on the HiNote VP575 laptop computers.
    
    We have just had our third out of three new HiNote VP 575  fail in the
    following manner.    

    All 3 systems are brand new.  When each was removed from the box and
    initially powered up the systems invoke the FIS software procedure. 
    Shortly after beginning the Win95 installation process a screen appears
    stating that the previous installation of Windows95 did not complete
    successfully and that a "safe installation" should be done. (I do not
    remember the exact wording as I am entering this from home).  What
    bothers us is that this is a brand new, first time installation but the
    system indicates that a previous installation of Windows 95 had been
    started on the computer and aborted.

    Why had a previous installation of Win95 been started on these "new"
    computers?

    After completing the installation of Win95, all systems were running
    normally and had been shut down properly without any errors, etc.  When
    they were later powered on, the following occured.

    The systems are powered up and the BIOS boot process completes and the
    Win95 splash screen appears.  Then I get the following error message
    
    	While initializing device IOS:
    	Windows protection error.  You need to restart your computer.
    
    Several attempts to restart the computer have not resulted in the
    system booting correctly.  It will, however, start up in SAFE MODE.
    
    All systems were running the FIS version of Win95.  After rebuilding
    from scratch with the supplied CDROM's everything works fine.

    Any idea what is wrong?  We have seen this on three out of three HiNote
    VP 575 computers.  We have 5 more VP575 and 10 VP560 computers to load
    and cannot afford to have this problem on each one.

    Help would be greatly appreciated!  Calls to 1-800-354-9000 have not
    resulted in any answers.
T.RTitleUserPersonal
Name
DateLines
2413.1TARKIN::LINBill LinSun May 25 1997 00:227
    re: WHYNOW::NEWMAN
    
    > Calls to 1-800-354-9000 have not resulted in any answers.
    
    Fine, but did you get them to escalate the problem to engineering?
    
    /Bill
2413.2Is there a specific way to do this?WHYNOW::NEWMANProtector of the CauseSun May 25 1997 09:003
    How specifically is this done?  I asked what else I/they could do and
    did not get much of a response.  Is there something specific I should
    ask for?
2413.3get a log numberTARKIN::LINBill LinSun May 25 1997 09:1810
    re: .2 by WHYNOW::NEWMAN
    re: How?
    
    The 800 number you called is run by the CSC which is part of MCS.  MCS
    is the primary (if not only) organization that does problem elevations
    to engineering.  There may be intermediate groups involved.  You just
    have to TELL them to escalate and don't take no for an answer.  100%
    failure rate is unacceptable.
    
    /Bill
2413.4I'll call next weekWHYNOW::NEWMANProtector of the CauseSun May 25 1997 11:171
    I'll give a call on Tuesday and post what happens
2413.5It happened again!WHYNOW::NEWMANProtector of the CauseTue May 27 1997 13:495
    Just had it happen on yet two more systems (one not built by me).  I
    logged a call with MCS and requested that they escalate it to
    engineering.  This time I got an understanding telephone support rep
    who took down all the information and said someone will call me within
    24 hours.
2413.6VP575 system.1stNNTPD::"[email protected]"BPKWed May 28 1997 11:4531
I was lucky.  I had no problem of installing the VP575 with OSR2.
(The DEPCM lan card took a little bit longer to install.)

Just like what you have, it is a brand new notebook. I removed the VP575 from
the box and powered up the systems to invoke the FIS software procedure.
Similarly, shortly after beginning the Win95 installation process a screen
appears stating that the previous installation of Windows95 did not complete
successfully and that a "safe installation" should be done.  I proceeded from
there on, as if it is the normal Win95 OSR1 install.

After the installation, I let the notebook to reboot itself without powered
down the PC.  I did not insert any PCMCIA cards, nor the additional memories.
I vaguely remember that the PC rebooted twice, but I did not have to touch the
Power button at all.  OSR2 was then installed without any problem.  I do not
understand why you have to power on to continue.

After sucessful installation, it is important that you have 5 important
hidden files:

C:\SYSTEM.1ST
C:\WINDOWS\SYSTEM.DA0
C:\WINDOWS\SYSTEM.DAT
C:\WINDOWS\USER.DA0
C:\WINDOWS\USER.DAT

One of the Microsoft Windows KB file explains how you can reset the notebook
using the file SYSTEM.1ST .

Good luck.

[Posted by WWW Notes gateway]
2413.7Another one bites the dust...WHYNOW::NEWMANProtector of the CauseThu May 29 1997 11:0930
    re .5
    
    Well it has been over 24 hours and no one has called yet.  I called
    back MCS and they said they would have someone call me "within 24
    hours".
    
    As to the ongoing saga of "bad systems", we have just returned yet
    another one to the Repair Center to be fixed.  This one experienced the
    following problems:
    
    1)  Took it out of the box, powered it up, and ran the FIS installation
    process.  Appeared to complete without error, however...
    
    2)  When the Windows95 installation process said it was done and would
    reboot to complete the process the system rebooted and came up with a
    "Registry Corruption Error".  It said to reboot to restore to the last
    known good version of the registry.
    
    3)  When the system rebooted it said there was no good version of the
    registry and to reinstall Windows 95.
    
    4)  Following the instructions in the User Guide, and using the CDROM's
    supplied with the system, proceeded to reload Windows 95.  The reload
    process appeared to work but when the system rebooted it only knew
    about the hard disk; it did not know about the CDROM drive.
    
    5)  Step 4 was repeated 3 more times, each time giving the same
    results.
    
    6)  A call was placed to MCS and they said to return the unit...
2413.8Need more info to help resolve the issuePCBUOA::FERRANTEVThu May 29 1997 12:4710
    Could you folks tell me what language and country these systems are
    coming from.. Serial number might also help.. There would appear top be
    a problem in Manufacturing but I do not know which of the 3 sites is
    having the problem. It appears that these are all on VP575 FIS Win95
    systems. When the FIS was tested, no such issues occurred. Something is
    going wrong in the process and more information on model #, serial #,
    language, MFG POD (Compal, Bizcom, etc) is needed..
    
    Thanks,
    Vin
2413.9License and Registration, SirPCBUOA::GLANTZThu May 29 1997 16:372
    Please provide the "sequence number" or "case number" the Helpdesk gave
    you. That way I can follow up with the Helpdesk manager.
2413.10They would not give me one!WHYNOW::NEWMANProtector of the CauseThu May 29 1997 17:125
    Unfortunately they did not give me one.  I asked at least twice for one
    but was told that since the problem was being referred to engineering
    that one would not be assigned until the problem had been referred.
    
    This is really what they told me!
2413.11It is Problem Number 13182WHYNOW::NEWMANProtector of the CauseThu May 29 1997 17:213
    I just called back MCS to see if they could find out a problem number
    or log number.  After a little searching they did find a record of the
    call and said that it was assigned "Problem Number 13182"