1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
  2. Two Factor Authentication is now available on BeyondUnreal Forums. To configure it, visit your Profile and look for the "Two Step Verification" option on the left side. We can send codes via email (may be slower) or you can set up any TOTP Authenticator app on your phone (Authy, Google Authenticator, etc) to deliver codes. It is highly recommended that you configure this to keep your account safe.

ARGH! Critical Error - Assertion Failed

Discussion in 'Hardware, Software & Troubleshooting' started by Zaphoid, Mar 1, 2000.

  1. Zaphoid

    Zaphoid New Member

    Joined:
    Jan 15, 2000
    Messages:
    14
    Likes Received:
    0
    I've reinstalled from the hard drive as suggested at http://unreal.epicgames.com/. This did not fix the problem. Is there any way to verify my installation? This seems to be a recurring problem for quite a few people, with no real answer. Epic, please help.

    [​IMG]



    [This message has been edited by Zaphoid (edited 03-04-2000).]
     
  2. Noodle

    Noodle New Member

    Joined:
    Mar 1, 2000
    Messages:
    16
    Likes Received:
    0
    I did the same thing last night, installed from HD and got the Assertion Error again not 30 mins after new install.

    Come on Epic lets have another bug fix asap please!!
     
  3. el Gato

    el Gato Has-Been

    Joined:
    Jan 19, 2000
    Messages:
    3,523
    Likes Received:
    0
    The 406 should be the fix. Check out Bounca's post, this forum: "$100 dollars for anyone..."



    [​IMG]

    Hey man, sniff my finger...
     
  4. STC_Wacky

    STC_Wacky Guest

    I'm not sure if this will help.
    You should run a scan disk + a surface scan to make sure that your HD is ok. Then you have to copy the CD onto your HD then install UT into a fresh folder (not over the contents of an older folder)
    This worked for a mate of mine. /~unreal/ubb/html/smile.gif

    [​IMG]
    <BLOCKQUOTE><font size="1" face="Tahoma, Arial, Helvetica">quote:</font><HR> Fighting for peace is like screwing for virginity! <HR></BLOCKQUOTE>
     
  5. STC_Wacky

    STC_Wacky Guest

    Here are a few things that I just found that might help you out if my last suggestion didn't work.

    Make Sure You Are Using Protected Mode CD-ROM Drivers
    Make sure you are using protected mode (32-bit) drivers for your CD-ROM drive. To do this:
    Click Start, point to Settings, and then click Control Panel.


    Double-click System.


    Click the Performance tab, and then confirm that the File System entry is 32-bit. If the File System entry is Some drives are using MS-DOS compatibility, you may be using real mode (16-bit) CD-ROM drivers. If this is the case, you may not be able to read certain files on the CD-ROM.

    Contact the manufacturer of your CD-ROM drive to obtain an updated, protected mode driver for your CD-ROM drive.


    Click OK, and then close Control Panel.


    If the issue continues to occur, proceed to the next method.
    Reduce CD-ROM Drive Caching
    To reduce CD-ROM drive caching:
    Click Start, point to Settings, and then click Control Panel.


    Double-click System.


    On the Performance tab, click File System.


    On the CD-ROM tab, move the Supplemental Cache Size slider to the Small position.


    In the Optimize Access Pattern For box, click No Read-Ahead.


    Click OK, and then click Close.


    When you are prompted to restart your computer, click Yes.


    If the issue continues to occur, proceed to the next method.
    Disable Auto-Insert Notification
    NOTE: If you disable Auto-Insert Notification, your programs can no longer start automatically.

    To disable Auto-Insert Notification:
    Click Start, point to Settings, and then click Control Panel.


    In Control Panel, double-click System.


    On the Device Manager tab, click the PLUS SIGN (+) next to CDROM to expand the branch.


    Click your CD-ROM drive, and then click Properties.


    On the Settings tab, click to clear the Auto Insert Notification check box.


    Click OK, and then click OK again.


    Close Control Panel, and then restart the computer.


    Remove Duplicate CD-ROM Drives
    Remove any duplicate CD-ROM drives being loaded by Windows. To do this:
    Click Start, point to Settings, and then click Control Panel.


    Double-click System.


    On the Device Manager tab, click View Devices By Type.


    Double-click the CDROM branch to expand it.


    Note the properties for each device listed in the branch. To do this:


    Click a device, and then click Properties.


    Click each tab in the device properties dialog box, and then record the device information and settings.


    Click OK.


    Click OK, and then close Control Panel.


    Restart Windows in Safe mode. To do this, use the appropriate method for your version of Microsoft Windows.
    Windows 95
    Restart the computer. When you see the "Starting Windows 95" message, press the F8 key, and then select Safe Mode on the Startup menu.
    Windows 98
    Restart your computer, press and hold down the CTRL key when your computer completes the Power On Self Test (POST), and then select Safe Mode on the Startup menu.


    When Windows starts in Safe mode, click OK.


    Click Start, point to Settings, and then click Control Panel.


    Double-click System.


    On the Device Manager tab, click View Devices By Type.


    Double-click the CDROM branch to expand it.


    Verify that there are no changes in the list of devices in the branch. If you see a device that is not in the list of devices you noted in step 5, click the new device, and then click Remove. Repeat this step for each device in the branch that is not in the list of devices you noted in step 5.

    NOTE: If you see new copies of a device that is in the list of devices you noted in step 5, check the properties of each copy of the device. If the properties for the device match the properties you recorded, keep the device. If the properties for the device do not match the properties you recorded, remove the device.


    Click OK.


    When you are prompted to restart the computer, click OK.




    [​IMG]
    <BLOCKQUOTE><font size="1" face="Tahoma, Arial, Helvetica">quote:</font><HR> Fighting for peace is like screwing for virginity! <HR></BLOCKQUOTE>
     
  6. Zaphoid

    Zaphoid New Member

    Joined:
    Jan 15, 2000
    Messages:
    14
    Likes Received:
    0
    STC_Wacky: Thanks for the tips but unfortunately these do not help me. Before I reinstalled from the hard drive, I did a surface scan and a defragment. (with 30 full gigs it took hours) I haven't run 16 bit cd drivers since I ran Windows 3.1.

    In fact just to be sure, I tried copying the CD to the hard drive from 2 different cdroms, once from my 32x reader and once from my 6x cdr. I'm pretty sure it's a problem with the code in the game, especially after reading Bounca's post, this forum: "$100 dollars for anyone..."

    So now I'm hoping they get 406 released SOON. Damn, I hate being dumped in the middle of intense games.



    [This message has been edited by Zaphoid (edited 03-04-2000).]
     
  7. STC_Wacky

    STC_Wacky Guest

    My mate didn't install any patches at all. He did what I mentioned above and the problem disappeared. Stange though, it only ever crashes UT in an intense battle and always while in the air (well that was the case on my mates machine).
    I'm glad Epic are aware of the problem, the next fix should remove this bug.....and will probably introduce another 40 or so new bugs LOL. /~unreal/ubb/html/smile.gif /~unreal/ubb/html/smile.gif /~unreal/ubb/html/smile.gif

    [​IMG]
    <BLOCKQUOTE><font size="1" face="Tahoma, Arial, Helvetica">quote:</font><HR> Fighting for peace is like screwing for virginity! <HR></BLOCKQUOTE>
     

Share This Page