Announcement

Collapse
No announcement yet.

Windows 98 SE Insanity

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    why r u using this Vbext.exe ??
    if u don't need it .. then remark that line in autoexec.bat and see if that helps ..
    GigaByte 6BXC, celeron300A@450, 128 Ram, G200 8M SD

    Comment


    • #17
      I don't think so. I've never seen any documentation that ties a PD version with a minimal BIOS rev. I use PD 5.52 w/ BIOS 1.5-22 w/o problems, except ... Under Win98, I've had IE 5 and 5.5 lock up the PC but that's been w/ both the 5.52 and 5.41 versions. Only happens on certain pages, w/ banners I believe; I always attributed it to IE bugs exasperated by my paranoid settings (no JVM, JIT, etc.). It happens rarely, but I'll try upgrading the BIOS to see if it still occurs. Jorden, can you back up your statement with any proof? Can anbody else back you up? I have my doubts.
      <TABLE BGCOLOR=Red><TR><TD><Font-weight="+1"><font COLOR=Black>The world just changed, Sep. 11, 2001</font></Font-weight></TR></TD></TABLE>

      Comment


      • #18
        Just because you can boot into a different OS proves absolutely nothing. LAMFDTK is correct, that PS is known to have several problems with Athlon systems.

        Rags



        ------------------
        Partnership for an idiot free America

        Comment


        • #19
          Excuse me xortam, but as it seems I was wrong. I've just been corrected.

          I've looked around and no BIOS notes said a thing about this. If a BIOS note doesn't tell you you need PD x.xx for it to work right, you can still use the last BIOS you have

          Jord.
          Jordâ„¢

          Comment


          • #20
            Wow what a funky thread!

            Comment


            • #21
              You need to update the KA7-100 bios:

              ftp://ftp.abit.com.tw/pub/beta/ka7/ka7ry.zip

              KA7 beta BIOS RY.B00

              8.Fix memory I/O conflict issue with Matrox G400.

              [This message has been edited by phillight (edited 30 July 2000).]

              Comment


              • #22
                I finally tracked down this problem. Creating and looking at a bootlog I noticed that display.drv was failing to load. On a hunch I downloaded (took four bloody attempts! lame windowsupdate.........) and installed the latest DirectX.... and it works!

                Updating all of my other drivers and BIOS may or may not have helped me, I don't know. But it hardly hurts to have the latest in everything I suppose.

                Thanks for the help everyone

                Comment


                • #23
                  Glad you got it resolved. Welcome to the asylum.
                  <TABLE BGCOLOR=Red><TR><TD><Font-weight="+1"><font COLOR=Black>The world just changed, Sep. 11, 2001</font></Font-weight></TR></TD></TABLE>

                  Comment

                  Working...
                  X