So,you think your a tech?Trie this one...
Results 1 to 10 of 10

Thread: So,you think your a tech?Trie this one...

  1. #1
    Registered User kcornod's Avatar
    Join Date
    Oct 2001
    Location
    ny
    Posts
    66

    Question So,you think your a tech?Trie this one...

    I'm working on a toshiba laptop (satellite 2655xdvd),tried a restore from the factory cd..hangs on a few of the files (bad cd).so,did a format and tried to do a instal from a win98 se cd..goes through the scandisk..no errors..then goes to the scanning registry and gets ready to copy files.Then i get error measage
    Standard mode:fault in msdos extender...
    Bad fault in msdos extender...
    tried fdisk,fdisk/mbr,format/u,ect...keep getting the same responce....i thought I knew it all and seen it all..this one has me stumped...Is there a real tech in the house who can anser this one?If so please email me...
    Don

  2. #2
    Adm¡nistrator JungleMan1's Avatar
    Join Date
    Jan 2001
    Posts
    2,463

    Post

    Well I'm not a tech but I hope I can be of assistance

    <a href="http://support.microsoft.com/support/kb/articles/Q87/2/39.ASP" target="_blank">http://support.microsoft.com/support/kb/articles/Q87/2/39.ASP</a>

    From the page:

    <font color=blue size=2 face=Courier New>his error message occurs when the fault handler dispatcher in DOSX.EXE generates another cascaded fault while trying to handle a protected-mode exception. This error is usually caused by one of the following factors:

    HIMEM.SYS is unable to control the A20 line.


    DOS=HIGH is not functioning properly (related to HIMEM.SYS control).


    The RAM, static RAM (SRAM), single in-line memory module (SIMM), or dynamic RAM (DRAM) chips are not functioning properly.


    You are running DR DOS.


    The third-party memory manager is not configured correctly.


    The EMM386.EXE NOEMS x=A000-EFFF line is missing from the Config.sys file.


    You have an old, out-of-date ROM BIOS.


    Your CMOS settings are incorrect.


    Your Windows files are old or corrupted. To test this, create a new directory on the hard drive, and install Windows in that directory.


    Your disks are corrupted.


    Your system is infected with the Form, Forms, Noint, or Yankee Doodle virus.
    </font>

    Good luck!

  3. #3
    Junior Member
    Join Date
    Sep 2001
    Posts
    8

    Post

    Beat me to it, that's what I came up with too...

  4. #4
    Registered User
    Join Date
    Jun 2001
    Location
    N.Y.C.
    Posts
    118

    Post

    I come up with the same thing...

  5. #5
    Registered User
    Join Date
    Aug 2000
    Location
    Grand Rapids, MI, USA
    Posts
    813

    Post

    Regarding JungleMan's fix, don't necessarily go in order on his suggestions as bad memory will most likely be the fix. Good answer JungleMan.

  6. #6
    Registered User
    Join Date
    Apr 2001
    Location
    Canada
    Posts
    15

    Post

    It isn't a bad CD, it's a hardware problem.

  7. #7
    Registered User cabal's Avatar
    Join Date
    Feb 2001
    Location
    Lake Placid,NY
    Posts
    336

    Cool

    I don't know if this applies here, but i had a similar problem a few weeks ago. This pc had Win2K on it and was working fine till one day it wouldn't boot.I tried everything I could think of, nothing worked. Luckily customer had all his files backed up ( I was stunned! most don't back up a thing), so I tried to re-format and re-install, no go. Then I tried fdisk, format and re-install, still no go. It would hang at different points trying to re-install. I thought I had bad hardware, so I swapped the motherboard and chip( had a known good one in the shop) but still wouldn't re-install win2k. I then assumed hard drive so I went to Western Digitals site to get an RMA number. They make you run their diagnostic software to check the drive and generate an error code before they give you an rma( at least online they do, I know I could have called them and insisted on an exchange )so I ran their software but the drive passed all their tests. As a last ditch effort I tried their " reset the drive to all zereo's" software. I didn't believe it would work, but the drive took off and worked like a charm. I still am not sure why fdisk and re-format didn't solve the problem but the drive is fine now.
    "You've been livin' on the razor's edge, since you began to shave...
    Make sure you live, you're a long time dead, cradle to the grave"-Motorhead

  8. #8
    Registered User
    Join Date
    Jun 2001
    Location
    Mass
    Posts
    26

    Post

    Sounds like bad memory.

  9. #9
    Registered User kcornod's Avatar
    Join Date
    Oct 2001
    Location
    ny
    Posts
    66

    Post

    Sorry I did'nt get back sooner but the problem was toshiba restore disk is accompanied with a start up disk that configures the config sys.
    with DEVICEHIGH=emm386 among other things.
    I resolve this issue not with the companion disk but nortons disk doctor?go figure........Had nothing to do with bad memory, just misconfigured memory..

  10. #10
    Registered User tha 4NiK8R's Avatar
    Join Date
    Mar 2001
    Location
    Idaho
    Posts
    465

    Post

    FIX: Kick the POS to the curb and get a DELL.

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •