Announcement

Collapse

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

Running Win32s on ibm-5150 with Inboard 386/pc

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

    Running Win32s on ibm-5150 with Inboard 386/pc

    Hello
    For the last decade , my personal hobby has been modifying the old IBM pc, in quest for more speed and more possibilities regarding software and hardware enhancements. The hobby took shape on basis of my experiences in 1987 when i did buy my first PC. It was an nice clone with only floppy drive and no monitor. (got myself a nice green cga monitor though).
    The constant waiting for the PC , nourished the goal of more power and speed and space for this PC. And then 18 years later in 2005, i did restart this search for more power and space for this old PC.
    Originally i did only look at add on boards, but later defined the hobby as "the original IBM 5150 with the coolest addons".
    In some way i can say that i did achieve some of my goals.

    More space for the old computer is simple - give it TMC 850 scsi controller and a modern SCSI disk, then you got ALOT of space.
    More speed to the PC - i did test the 486 for inboard and it runs fast , but perhaps not practical in daily living due to heat exhaust from the CPU.
    ( http://www.vintage-computer.com/vcfo...on-Inboard-386 )
    Now for the software! With this post, i describe the road from standart windows 3.0 (realmode) to a more modern stage.

    5150-cimonvg.jpg

    edit : my mistake device=ibvhd.386 should read device=ibvfd.386


    senario:

    Let us imagine a person that did buy the first IBM 5150 and felt it was enough and did fulfill the duties of an personal computer.
    Years go bye and some day a fellow coworker comes and "brags" about his new 32bit game called FreeCell! Our imaginative person then decides also to play FreeCell on this beloved IBM 5150.
    ...well if this is your senario - then read on , here comes the "how to do it"...

    And YES it WERE possible to run win32s applications on the original 5150 with an Inboard 386/pc, in the year 1993

    In this posting all hardware(*) is 1993 and earlier and software from the date Win32s 1.1 hit the streets (the files in Win32s v.1.1 dates 27 july 1993).
    2015_10_04_7355--.jpg

    *
    components:
    IBM 5150a 16-64kb motherboard
    - BIOS chanced to facilitate Hard Drive and VGA with EPROM onboard.
    Inboard 386
    - 4 Mb extra RAM add on
    I/O, parallel and serial,
    -and a logitech mouse connected to the RS232 port.
    VGA card, "video7" anno 1989
    floppy controller with high density. and 1.44Mb floppy drive.
    - all the discs i used for this project were in 1.44mb format.
    - But if the original floppy were at hand in 360Kb format, it would be possible to install through an old low density controller and 360Kb drive.
    Harddrive controller , the old Xebec version from 1985
    - only hard disk working (with this Xebec) in my current stock, is the Seagate ST412 , 10Mb full size drive.
    PSU, newer version added.
    - The old 63 watt PSU is not enough, and in this setup i use 130 watt , think it is the import model.
    monitor - VGA.
    mouse and keyboard
    * only not standart in this computer is the 386/16mhz CPU has been replaced with 386/33mhz and the oscillation from 32 Mhz to 40Mhz,resulting in the Inboard running at 20 MHz, but i don't think it affects the way of function for this computer.


    2015_10_06_7365.jpg 2015_09_19_7303--.jpg 2015_09_19_7304.jpg


    how i installed:

    *Boot on PC DOS 5.0 floppy and install into hard drive C:
    - IBM PC DOS boots upon completion. remember to boot next time on floppy, and add Inboard driver.
    - IF you try to boot with HIMEM,SYS as first line in config.sys then PC stalls with "Parity Error"!
    *copy INBRDPC.SYS to C: and add into first line of config.sys
    *edit autoexec.bat so that SMARTDRV.EXE 256 256, by default it is like 2048 1024, and only leeves 3Mb for windows
    *remove unwanted files in DOS directory
    *install windows 3.1 from floppy drive (6 floppies in total)
    *return to dos
    *add share.exe to autoexec.bat (win32s demands share)
    *copy inboard drivers that is extracted from either the original floppies ("windows 3.0 for inboard 386") or copy from an installation on harddrive
    *place the inboard drivers in c:\windows\system directory
    *edit system.ini
    *remove unwanted files in windows and system..... when you got 10Mb in total, the space disappears just like that !
    *defrag harddisk - swapfile must have non fragmented space.
    *boot and start windows C:\win/3
    *add permanent swapfile 1024Mb to system (win32s demands it)
    *boot and start win/3, then install win32s version 1.1 and FreeCell application, from floppy drive , where the unpacked win32s files are

    *boot and start win/3 - now you can play FreeCell on the first IBM PC

    system.ini listing:
    [boot]
    shell=progman.exe
    mouse.drv=lmouse.drv
    network.drv=
    language.dll=langsca.dll
    sound.drv=mmsound.drv
    comm.drv=comm.drv
    keyboard.drv=ibkbd.drv <-----
    system.drv=ibsystem.drv <-----
    386grabber=VGA.3GR
    oemfonts.fon=vgaoem.fon
    286grabber=VGACOLOR.2GR
    fixedfon.fon=vgafix.fon
    fonts.fon=vgasys.fon
    display.drv=SUPERVGA.DRV
    drivers=mmsystem.dll winmm16.dll

    [keyboard]
    ..(i did not alter any settings here)..

    [boot.description]
    ..(i did not alter any settings here)..

    [386Enh]
    device=C:\WINDOWS\SYSTEM\WIN32S\W32S.386
    mouse=lvmd.386
    network=*dosnet,*vnetbios
    ebios=*ebios
    woafont=dosapp.fon
    display=*VDDVGA
    EGA80WOA.FON=EGA80WOA.FON
    EGA40WOA.FON=EGA40WOA.FON
    CGA80WOA.FON=CGA80WOA.FON
    CGA40WOA.FON=CGA40WOA.FON
    keyboard=ibvkd.386 <-----
    ;*vkd
    device=vtdapi.386
    device=ibvpicd.386 <-----
    ;*vpicd
    device=*vtd
    device=*reboot
    device=ibvdmad.386 <-----
    ;*vdmad
    device=*vsd
    device=*v86mmgr
    device=*pageswap
    device=*dosmgr
    device=*vmpoll
    device=*wshell
    device=*BLOCKDEV
    device=*PAGEFILE
    device=ibvhd.386 <-----and yes, my mistake
    device=ibvfd.386 <----- the correct line
    ;*vfd
    device=*parity
    device=*biosxlat
    device=*vcd
    ;device=ibvmcpd.386 << DO NOT USE! Then win32s do not run
    device=*vmcpd
    device=*combuff
    ;device=ibvhd.386
    device=*cdpscsi
    TimeCriticalSection=10000 <- added by me,but not necessary
    InDOSPolling=FALSE <- added by me,but not necessary
    local=CON
    FileSysChange=off
    PermSwapDOSDrive=C
    PermSwapSizeK=1096
    32BitDiskAcces=off <- added by me,but not necessary

    [standard]

    [NonWindowsApp]
    ..(i did not alter any settings here)..
    [mci]
    ..(i did not alter any settings here)..
    [drivers]
    ..(i did not alter any settings here)..
    [LogiMouse]
    ..(i did not alter any settings here)..
    [display]
    ..(i did not alter any settings here)..


    my comments:

    * Must give thanking thought to "Hagen" of this forum for bringing the existence of the "Windows 3.0 for Inboard 386/PC" to hour attention, thank you to the seller at Ebay that gave me the opportunity to try this out, and a great thank you to you forum-reads for your great advice and comments.

    * This is NOT full functioning software/hardware setup! If i click on the "MS-DOS prompt" icon the computer halts with an error
    And some utility programs also do not function. Like the QEMM memory analyser do not run - even though the QEMM do run fine.
    But if you can live without the command.com then alot of other software runs just fine : Office suite 4.3 , photoshop 1.5, internet explorer 5.01 (extreme slow) but it runs online on the internet, Lotus smartsuite 4.0, matchcad 4.0, Borland c++ 4.52 compiles, but VC++ 1.52 do not. Windows 3.11 runs also - but same malfunctioning commmand.com like in the windows 3.1.
    Have tried windows 95 with the inboard drivers but no luck until now.

    * Please do not PM me for copy's of this software, not going to happen. Hope you can respect that.

    remark : please do beware - this setup is by no way supportet by anyone , and for sure filled with bugs !!!

    #2
    hello again
    If you like to some month further then Mathcad 4.0 was released on (?) 15 marts 1993 , and it had incorporated the win32s ver.1.0.
    I have tested and in runs on IBM5150+Inboard
    /cimonvg

    Comment


      #3
      Very nice! I am running a 486 on my InBoard/PC (along with the same 4MB memory daughter card as yours - those are rare!) with no heat issues @ 33MHz, but I took an alternate route. I just left the oscillator as it were and replaced only the original InBoard 386 CPU with 133-pin compatible Cyrix 386>486 20/40 CPU for $26 ( CX486DRX2-20/40GP - http://www.questcomp.com/questdetail...ign=DigipartWS ) - and it runs without any other modification at 33Mhz by default with very little heat over the original 386 (no CPU fan or heat sink needed, but I did add a small 3" fan inside the case just to get more airflow just for good measure though so that I could keep the original 5160 cover on all the time without worry of even modest heat buildup). You might consider the Cyrix - the difference from 20MHz to 33MHz is worth it - you'll find pretty much all Win3.1x apps run substantially faster.

      Thanks for documenting the .ini files layout with the .ibxxx replacement - I've not gotten around to try it yet, but you made it easy to follow

      Regards,
      Mike
      Last edited by nc_mike; October 5, 2015, 07:25 PM.

      Comment


        #4
        I love weird setups like this. I always wondered if Windows 3.1 would work with the special inboard files, but could never try it since I didn't have the special version of windows 3.0. My inboard is long since gone.
        "Will the Highways on the internets become more few?"

        V'Ger XT

        Comment


          #5
          I'll give you added points if you add in one of the 386 to 486 upgrades, then use the software 486 to 586 emulation.
          [Need something to waste time on? Click here to visit my YouTube channel CelGenStudios]
          --------------------------------------------------------------------------------------------
          [No time for videos? Click here to visit my Twitter feed @CelGenStudios]

          = Excellent space heater

          Comment


            #6
            Very nice I'm hoping that the Inboard-specific Windows software gets archived for posterity somewhere

            Again, nice work with this! - the setup looks pretty straightforward, however I'm quite sure that it took alot of trial and error to get there!
            ---
            Currently seeking:
            * Roland MPU-401/AT (with daughter card header)
            * Magitronic K-156 Keyboard (5pin DIN w/ XT-AT switch)
            I also collect PC and C64 Sierra On-Line software!

            Comment


              #7
              Originally posted by NeXT View Post
              I'll give you added points if you add in one of the 386 to 486 upgrades, then use the software 486 to 586 emulation.
              I tend to run everything Windows 95 and later on my behemoth modern system using VMWare virtual machines. For me its the ability to run every bit of x86 software ever made - that's my idea of emulation . Now, what I'd really like to do with my InBoard/386 running the Cyrix 486 @ 33Mhz is to be able run Windows 3.1 in protected/enhance mode so that I can run Windows remote control software over TCP/IP with full a remote graphical UI. That hasn't been possible before now because I haven't been able to run any of the remote control Windows packages in protected mode on a 5150/5160 due to the A20 Gate issue locking up the keyboard when nd entering Windows from DOS (and back again, which causes a system hang due to the lack A20 switching). Tonight I'll try the InBoard files and see if I can get into 386 enhanced mode and see if that fixes the A20 keyboard lock-up and if I can run the remote control (Win 3.1) software. If so the significance would be the unique ability to remotely control a 5150/5160-based system running Windows 3.1 from a modern system over TCP/IP.

              Regards,
              Mike
              Last edited by nc_mike; October 6, 2015, 11:55 AM.

              Comment


                #8
                Hello
                ..and yes have spend some time looking at this configuration. The command.com issue which brings the PC down , i have been looking into. But, i am not a programmer - so i have not found where in the driver the error is..
                @ nc_mike, windows for workgroups 3.11 supports RDP, remote desktop would be possible, or ? ... have not (yet) tried that one out. But wfw 3.11 runs on the 5150+inboard if you follow my instructions.
                @ NeXT, have been looking at a used VRM+Cyrix586 on auction. But not bought it - dont know if the IBM5150 will boot with Inbaord and Transcomputer module
                /cimonvg

                Comment


                  #9
                  I think somebody in another thread already tested the transcomputer module in their XT, and it did indeed boot. I can't recall if the L1 cache was functional though. Now I have my doubts a Cyrix 5x86 will work in the transcomputer module though. It can be pretty picky even on real 5V only 486s. A POD83 might work though.
                  "Will the Highways on the internets become more few?"

                  V'Ger XT

                  Comment


                    #10
                    Heck ya! Full Windows 3.1 running in protected/enhanced mode is finally working!

                    Yeehaaa!

                    First I installed Windows 3.0 for the Inboard/386 to a PC/DOS 2000 (7.1) CF card I booted up on my IBM 5160-based (XT-486) system. Then I copied all of the IN***.386 and IN***.DRV (Intel version) driver files onto a fully installed Windows 3.1 directory on another CF card and carried most of the same SYSTEM.INI driver modifications from the 3.0 SYSTEM.INI into the 3.1 SYSTEM.INI file EXCEPT for changing device=*vdmad, which Windows 3.1 needs to use audio drivers, so I left that one as is.

                    The result? I can boot into Windows 3.1 enhanced mode (WIN/3) with no problems whatsoever, run apps that previously would not run (such as ReachOut Windows/DOS remote control host, and others), edit in MS Office without the keyboard locking up, and return back to DOS, also without the keyboard locking up. Of course I am running the InBoard/386 with the extra memory configured as extended memory and the Cyrix 386-486 20/40 MHz drop-in CPU (with effective speed @33MHz) makes along with the CF drive makes Windows 3.1 quite usable performance-wise. I haven't yet installed Win32s - that's the next step. I also plan to try out remotely controlling the system from my laptop over TCP/IP.

                    [boot]
                    386grabber=8514.gr3
                    286grabber=vgacolor.gr2
                    shell=progman.exe
                    network.drv=
                    language.dll=
                    fixedfon.fon=8514fix.fon
                    comm.drv=comm.drv
                    sound.drv=sound.drv
                    oemfonts.fon=8514oem.fon
                    fonts.fon=8514sys.fon
                    mouse.drv=ibmouse.drv <-----
                    keyboard.drv=ibkbd.drv <-----
                    display.drv=8514.drv
                    system.drv=ibsystem.drv <-----
                    [keyboard]
                    subtype=
                    type=4
                    oemansi.bin=
                    keyboard.dll=
                    [boot.description]

                    network.drv=Network not installed
                    language.dll=English (American)
                    keyboard.typ=Enhanced 101 or 102 key US and Non US keyboards
                    mouse.drv=Microsoft Serial, Bus or Inport
                    display.drv=8514/a
                    system.drv=Inboard 386/PC System <-----
                    [386Enh]
                    ebios=*ebios
                    display=vdd8514.386
                    keyboard=ibvkd.386 <-----
                    mouse=ibvmd.386 <-----
                    network=*vnetbios, *dosnet
                    device=ibvpicd.386 <-----
                    device=*vtd
                    device=*reboot
                    ;device=ibvdmad.386 <---- Excluded this one
                    device=*vdmad <---- Left this one as it was - Win3.1 audio drivers need the Win3.1 driver version
                    device=*vsd
                    device=*v86mmgr
                    device=*pageswap
                    device=*dosmgr
                    device=*vmpoll
                    device=*wshell
                    device=ibvhd.386 <-----
                    device=ibvfd.386 <-----
                    device=*vpd
                    device=*parity
                    device=*biosxlat
                    device=*vcd
                    device=ibvmcpd.386 <-----
                    device=*combuff
                    device=*cdpscsi
                    local=CON
                    FileSysChange=off
                    CGA40WOA.FON=CGA40WOA.FON
                    CGA80WOA.FON=CGA80WOA.FON
                    EGA40WOA.FON=EGA40WOA.FON
                    EGA80WOA.FON=EGA80WOA.FON
                    [standard]
                    [NonWindowsApp]

                    Regards,
                    Mike

                    Comment


                      #11
                      Originally posted by nc_mike View Post
                      Yeehaaa!
                      ...........................
                      hello - great to hear it works nc_mike
                      ..i think you have to switch back to the original device=*vmcpd
                      the device=ibvmcpd.386 ..left me with something like "a component in win32s is not working, please reinstall win32s".

                      Actually, at one time i did run with only 3 drivers in enhanced mode - the rest were the original win3.1 drivers. Think it was the keyboard driver.drv the ibvpicd.386 and the ibkbd.drv, and the system did start! It worked just fine until i tried to read the A-drive. The information on the floppy were not readable! Some of the drivers obviously is not needed and others are.
                      /cimonvg

                      Comment


                        #12
                        hello again - some perhaps useless information
                        I did try to swap the inboard with a 4Mb add on board , and replaced it with an Inboard with 2 Mb. (used the same harddrive described above - same software setup). It did start in DOS, and started windows with the win/3 switch. It ran enhanced mode, and the FreeCell did start! And if i clicked quickly the game startede, but then the disk started swapping (constant light in the disk-diode), and the game stopped, mouse still alive though. Many minuttes later the disk still swapping, but again 640k+2,3Mb extended and 800kb free disc is properly asking for the impossible

                        2015_10_15_7394.jpg

                        on picture: above 2Mb ram card, the inboard , then inboard with 4Mb ram card mounted
                        /cimonvg

                        Comment


                          #13
                          Here's the deal with device=*vmcpd

                          Make sure the following line is in your System.ini file:
                          device=*vmcpd

                          Without this line in the System.ini file, Win32s displays the following error when you launch FreeCell or any 32-bit application:

                          Win32s - Error:
                          Improper installation. Windows requires W32s.386 in order to run. Reinstall Win32s.

                          Windows Setup installs the VMCPD VxD to handle floating point exceptions, but it is possible that another driver was installed replacing the VMCPD VxD. Win32s only needs the VMCPD driver to handle floating point exceptions if a coprocessor is present. But the Win32s setup program checks for this driver unconditionally.


                          Soooooo.maybe the best thing to do is leave the original Win32s version of vmcpd in place during Win32s install and replace it with the InBoard version after Win32s install?

                          Regards,
                          Mike

                          Comment


                            #14
                            Originally posted by nc_mike View Post
                            ...

                            Soooooo.maybe the best thing to do is leave the original Win32s version of vmcpd in place during Win32s install and replace it with the InBoard version after Win32s install?

                            Regards,
                            Mike
                            hello - no i dont know if your approach is the right way. It way work with either driver - but to find where the one or the other driver fails properly takes alot of time.
                            Today i did install Helix Hurricane v.2.03 - and it worked 99% (on my inboard+evergreen 486bl)
                            The "discover" reported high RAM speed is about 10 Mb/s in 32 bit mode !
                            /cimonvg

                            Comment


                              #15
                              Envious! That's a screamer! What is the effective clock speed?

                              Regards,
                              Mike

                              Comment

                              Working...
                              X