Announcement

Collapse
1 of 2 < >

Welcome back!

If you're seeing this then welcome to the NEW Vintage Computer Forums.

The forums have been updated to the latest version of the software which means new features and some changes to old ones.

Please don't be alarmed. Change is good!
2 of 2 < >

Forum etiquette

Our mission ...

This forum is part of our mission to promote the preservation of vintage computers through education and outreach. (In real life we also run events and have a museum.) We encourage you to join us, participate, share your knowledge, and enjoy.

This forum has been around in this format for over 15 years. These rules and guidelines help us maintain a healthy and active community, and we moderate the forum to keep things on track. Please familiarize yourself with these rules and guidelines.


Remain civil and respectful

There are several hundred people who actively participate here. People come from all different backgrounds and will have different ways of seeing things. You will not agree with everything you read here. Back-and-forth discussions are fine but do not cross the line into rude or disrespectful behavior.

Conduct yourself as you would at any other place where people come together in person to discuss their hobby. If you wouldn't say something to somebody in person, then you probably should not be writing it here.

This should be obvious but, just in case: profanity, threats, slurs against any group (sexual, racial, gender, etc.) will not be tolerated.


Stay close to the original topic being discussed
  • If you are starting a new thread choose a reasonable sub-forum to start your thread. (If you choose incorrectly don't worry, we can fix that.)
  • If you are responding to a thread, stay on topic - the original poster was trying to achieve something. You can always start a new thread instead of potentially "hijacking" an existing thread.



Contribute something meaningful

To put things in engineering terms, we value a high signal to noise ratio. Coming here should not be a waste of time.
  • This is not a chat room. If you are taking less than 30 seconds to make a post then you are probably doing something wrong. A post should be on topic, clear, and contribute something meaningful to the discussion. If people read your posts and feel that their time as been wasted, they will stop reading your posts. Worse yet, they will stop visiting and we'll lose their experience and contributions.
  • Do not bump threads.
  • Do not "necro-post" unless you are following up to a specific person on a specific thread. And even then, that person may have moved on. Just start a new thread for your related topic.
  • Use the Private Message system for posts that are targeted at a specific person.


"PM Sent!" messages (or, how to use the Private Message system)

This forum has a private message feature that we want people to use for messages that are not of general interest to other members.

In short, if you are going to reply to a thread and that reply is targeted to a specific individual and not of interest to anybody else (either now or in the future) then send a private message instead.

Here are some obvious examples of when you should not reply to a thread and use the PM system instead:
  • "PM Sent!": Do not tell the rest of us that you sent a PM ... the forum software will tell the other person that they have a PM waiting.
  • "How much is shipping to ....": This is a very specific and directed question that is not of interest to anybody else.


Why do we have this policy? Sending a "PM Sent!" type message basically wastes everybody else's time by making them having to scroll past a post in a thread that looks to be updated, when the update is not meaningful. And the person you are sending the PM to will be notified by the forum software that they have a message waiting for them. Look up at the top near the right edge where it says 'Notifications' ... if you have a PM waiting, it will tell you there.

Copyright and other legal issues

We are here to discuss vintage computing, so discussing software, books, and other intellectual property that is on-topic is fine. We don't want people using these forums to discuss or enable copyright violations or other things that are against the law; whether you agree with the law or not is irrelevant. Do not use our resources for something that is legally or morally questionable.

Our discussions here generally fall under "fair use." Telling people how to pirate a software title is an example of something that is not allowable here.


Reporting problematic posts

If you see spam, a wildly off-topic post, or something abusive or illegal please report the thread by clicking on the "Report Post" icon. (It looks like an exclamation point in a triangle and it is available under every post.) This send a notification to all of the moderators, so somebody will see it and deal with it.

If you are unsure you may consider sending a private message to a moderator instead.


New user moderation

New users are directly moderated so that we can weed spammers out early. This means that for your first 10 posts you will have some delay before they are seen. We understand this can be disruptive to the flow of conversation and we try to keep up with our new user moderation duties to avoid undue inconvenience. Please do not make duplicate posts, extra posts to bump your post count, or ask the moderators to expedite this process; 10 moderated posts will go by quickly.

New users also have a smaller personal message inbox limit and are rate limited when sending PMs to other users.


Other suggestions
  • Use Google, books, or other definitive sources. There is a lot of information out there.
  • Don't make people guess at what you are trying to say; we are not mind readers. Be clear and concise.
  • Spelling and grammar are not rated, but they do make a post easier to read.
See more
See less

IBM Personal Computer 340 CPU Issues

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

  • IBM Personal Computer 340 CPU Issues

    Hello, I have the following IBM Personal Computer 340 I am currently restoring/upgrading:

    Machine Type: 6560-17A
    Surepath BIOS Flash Revision Level LXKT20AUS
    BIOS Date: 07/21/96
    System Board Identifier: 0YVTGL28S25

    I'm trying to replace the original Intel Pentium 100 CPU with an Intel Pentium 200 CPU (non-MMX of course).

    - The FSB jumpers can be set for 50MHz, 60MHZ, or 66MHz
    --- I set them for 66MHZ

    - The multiplier jumpers can be set for 1.5x, 2.0x, 2.5x, and 3.0x
    --- I set them for 3.0x

    - The CPU voltage jumper can be set for 3.3V or 3.52V
    --- I set it for 3.3V

    When I install the 200MHz CPU it is still reported at 100MHz? I played the binary shuffle with the multipliers but that only resulted in the CPU being reported as 0MHz at times or 100MHz, nothing else.

    I installed an Intel Pentium 133MHz CPU (66MHZ FSB, 2.0x) and that works fine. I don't currently have a 166MHz CPU laying around to test.

    I don't understand why 66MHz with a multiplier of 3.0x is not working? I looked around for BIOS updates but these seem non-existent (I would much appreciate if someone could point me to a location to find IBM BIOS updates).

    Is there something I'm missing with this model/series of IBM systems?

    Any help would be appreciated. Thank you.

  • #2
    If the motherboard can't properly determine the CPU speed at 200 MHz, it very likely doesn't support it.

    Many motherboard vendors in the 1990s often included bus speeds and multipliers that didn't actually work. They were usually intended for forwards compatibility with not yet released processors, but in many cases never actually worked due to bugs in the board, chipset limitations or never getting a newer BIOS release.

    Sometimes you can get lucky though, and the CPU will still operate at the proper speed, despite the BIOS not being able to report the speed properly.

    Try this program in DOS:
    https://www.elhvb.com/webhq/download...ols/sst470.zip

    Comment


    • #3
      I'll see what System Speed Test reports, thank you. As you pointed out I figured the limitation falls somewhere in either the motherboard or BIOS. I'm hoping that someone has successfully upgraded the model 340 beyond 133MHz and can help point me in the right direction. I've seen YouTube video of people getting their 340 systems working with a 166MHz CPU, so there's a chance 200MHz will work as well. Thank you for the reply.

      Comment


      • #4
        Most likely just a display anomaly since the BIOS lacks an entry for that CPU. If you set it to 66 x 3.0, it will run at 200 MHz, as the multiplier pins are a direct connection to the socket 7 and the BIOS has no control over the actual speed of the CPU.

        Comment


        • #5
          Originally posted by Timo W. View Post
          Most likely just a display anomaly since the BIOS lacks an entry for that CPU. If you set it to 66 x 3.0, it will run at 200 MHz, as the multiplier pins are a direct connection to the socket 7 and the BIOS has no control over the actual speed of the CPU.
          SUCCESS!

          I had to upgrade the BIOS which I found here:

          http://ps-2.kev009.com/pccbbs/commer...op/lxjt27a.exe
          http://ps-2.kev009.com/pccbbs/commer...op/lxjt27a.txt

          After *finally* finding the BIOS updates I noticed a later BIOS than mine supported up to 166MHz CPUs. I flashed the BIOS with the latest revision, set the jumpers for 166MHz and it actually reported that in BIOS using a 200MHz CPU.

          Per Timo W.'s suggestion I set the speed for 200MHz and sure enough, SPEEDSYS reports the system running at 200MHz even though the BIOS reports a 100MHz CPU.

          (Thanks to GiGaBiTe for the SPEEDSYS link)

          What a HUGE improvement in performance! I upgraded the video RAM to 2MB as well. This thing chews through DOS games almost as well as a 233MMX system would.

          Now a new anomaly to deal with: When I upgraded the video RAM to 2MB the mouse pointer in Windows for Workgroups 3.11 turned into a splotchy looking square, LOL. This is probably because I am using the Cirrus Logic Alpine drivers meant for the GD5430 chipset. This system has the CL 5434 chipset so I'll need to find either an exact match or something closer than the Alpine drivers.

          Comment


          • #6
            Correction, that's a GD5436 video chipset contained in this PC. As I suspected, the correct video drivers fixed the funky mouse image.

            I found the IBM Windows 3.1x video drivers here:

            http://ps-2.kev009.com/pccbbs/commer...op/lz2t07a.exe

            Other IBM video drivers pertaining to this computer can be found here:

            DOS: http://ps-2.kev009.com/pccbbs/commer...op/lz0t03a.exe
            OS2: http://ps-2.kev009.com/pccbbs/commer...op/lz1t13a.exe
            W95: http://ps-2.kev009.com/pccbbs/commer...op/lz3t08a.exe
            WNT: http://ps-2.kev009.com/pccbbs/commer...op/lz4t05a.exe

            Duke Nukem 3D and Quake/Quake II run as smooth as silk on this system with a 200MHz CPU installed. Very happy with the results.

            Thanks for the help everyone

            Comment


            • #7
              Nice to hear. One of my retro systems is a 200 MHz Pentium system as well and I'm loving it.

              Comment

              Working...
              X