|
|
|
Win 3.11 Problem - Program Manager
|
Original Message
|
Name: cates2
Date: October 4, 2005 at 11:26:41 Pacific
Subject: Win 3.11 Problem - Program ManagerOS: Win 3.11CPU/Ram: Pentium; 16MB RAM |
Comment: Just inherited PC running DOS 6.22 & Win3.11 & iRMX. The PC has irreplaceable (no disks) medical software that apparently only runs with Win 3.11. DOS runs fine. I had to add DEVICE=C:\DOS\EMM386.exe to config.sys to be able to load Win 3.11. Windows now loads and the unit powers up to the Program Manager screen. Here are my problems so far: 1) There is a program icon for the medical software but clicking it does nothing - nor can I start it from File Manager. 2) I can run some apps (e.g., Solitaire) fine. I can open Word but cannot close it - it hangs. 3) I cannot close Program Manager. I have to power off or exit to DOS and power off. 4) My program groups keep disappearing. If I try to add a group, I can name it but when I select OK, I get a message that the group is damaged/corrupt. Even if I copy over the original progman.ini (saved to floppy before starting this effort) file, it doesn't seem to work.
I don't know if these are all related issues. I also don't know where to start debugging. I was thinking I needed to "reinstall" Win 3.11 but I don't have the disks (looking on eBay) and I don't want to "mess up" the medical software. ANY HELP would be appreciated. THANKS
Report Offensive Message For Removal
|
|
Response Number 1
|
Name: alexanrs
Date: October 4, 2005 at 13:33:33 Pacific
|
Reply: (edit)Well, start the DOS version of Windows Setup (by navigating to the WINDOWS folder and running SETUP.EXE in plain DOS) and rever back to the generic drivers (VGA, MSMouse, and so on). Start windows. If problems still occur, try to see what is starting up with your windows: check WIN.INI section [windows], lines LOAD and RUN and Program manager STARTUP group. Also, try running SCANDISK and running even Physical tests. If things are still the same, try to see if it runs in standard mode. In regular Windows 3.1(1) you can start in standard mode by running either "WIN /s" or "WIN /2", in Windows for Workgroups 3.11 it is oficially impossible to use Standard mode, but you can actually use the undocumented "WIN /D:T" to do it. By the way, why did you put the EMM386 in config.sys? Windows is meant to be runnable without it (and it is the default, if you installed DOS 6.22 and Windows 3.11 in a row without modifying any settings)?
Report Offensive Follow Up For Removal
|
|
Response Number 2
|
Name: cates2
Date: October 4, 2005 at 16:29:58 Pacific
|
Reply: (edit)Hi! Thanks for the reply. The reason I added that line was because I tried everything else that I knew of and I couldn't load Windows. 1) Is there a "problem" having that in the config.sys file? 2) If so, could that be causing the ProgManager problem? 3) My original messages on startup were: "SMARTDRIVE cannot be loaded because the XMS driver, HIMEM.sys is not loaded. Check the config.sys file for a DEVICE=HIMEM.sys command line. Your computer cannot run Windows in either standard or 386 enhanced mode." The config,sys file had that line; I replaced HIMEM.sys with a newer version, but still couldn't start the PC. When I added that line it started. I can send autoexec & config files for your review if needed. Maybe it was just coincidence that adding that line worked!! THANKS - Cate
Report Offensive Follow Up For Removal
|
|
Response Number 3
|
Name: jboy
Date: October 4, 2005 at 17:26:36 Pacific
|
Reply: (edit)To run windows properly (enhanced mode), you do require HIMEM.SYS & EMM386.EXE to be loaded from c:\config.sys (and in a specific order) - something like: DEVICE=C:\DOS\HIMEM.SYS DEVICE=C:\DOS\EMM386.EXE NOEMS DOS=HIGH,UMB You can also use the c:\windows versions of those files if desired, although the DOS622 versions are newer We live in a society exquisitely dependent on science and technology, in which hardly anyone knows anything about science and technology
Report Offensive Follow Up For Removal
|
|
Response Number 4
|
Name: cates2
Date: October 5, 2005 at 10:59:37 Pacific
|
Reply: (edit)THANKS for the input. So the line with EMM386.exe is needed and is why I was able to start Win 3.11 after adding it. NOW.... Does anyone have any idea on why my Groups are becoming corrupt in Program Manager (see the text of the initial thread)??
Report Offensive Follow Up For Removal
|
|
Response Number 5
|
Name: jboy
Date: October 5, 2005 at 11:45:01 Pacific
|
Reply: (edit)Not really. In order for Win31 to run well, the DOS must be properly setup first. This also assumes that there are no hardware issues - bad or failing memory can generate all sorts of problems (for instance). Running any version of Windows without the installation disk(s) is a gamble We live in a society exquisitely dependent on science and technology, in which hardly anyone knows anything about science and technology
Report Offensive Follow Up For Removal
|
|
Response Number 6
|
Name: cates2
Date: October 5, 2005 at 12:14:03 Pacific
|
Reply: (edit)THANKS for the post. I'm going to try to run MemTest on the system.... I have some old RAM but don't know yet if it will be compatible....
Report Offensive Follow Up For Removal
|
|
Response Number 7
|
Name: alexanrs
Date: October 7, 2005 at 10:51:05 Pacific
|
Reply: (edit)jboy: EMM386.EXE is NOT needed to run Windows 3.11, just HIMEM.SYS is. In fact once I had problems installing Windows 3.11 (setup kept freezing) and it was solved by disabling EMM386.exe. EMM386.EXE is just needed to use UMBs, so you will have more Conventional Memory for DOS apps, and to provide EMS memory (again, to DOS apps, especially games). Windows 3.11 itself can run WITHOUT it, and in fact I recomend not using it unless you need UMBs or use plain dos (a Windows DOS box has EMS memory even without EMM386, like in Windows 95/98/ME). You could post your AUTOEXEC.BAT and CONFIG.SYS so it will be easier to help. These are mine generic startup files to run windows well, backup your current startup files and use mine in the exact order to avoid problems. There are comments in italic (with a ';' before them), do not copy them, but read them carefully: CONFIG.SYS: DOS=HIGH FILES=40 BUFFERS=10 STACKS=9,256 DEVICE=C:\DOS\HIMEM.sys /TESTMEM:ON DEVICE=C:\DOS\SETVER.EXE ;some hds do not work properly in 386 enhanced mode without the following line DEVICE=C:\DOS\SMARTDRV.EXE /DOUBLE_BUFFER ;use the following line only if your windows is windows FOR WORKGROUPS DEVICE=C:\WINDOWS\IFSHLP.SYS AUTOEXEC.BAT: @ECHO OFF ;the following two lines are absolutely not needed, i like to use them so it will be easy to see if you're in a DOS box or in Plain DOS SET PROMPT=[MS-DOS] $p$g SET WINPMT=[WINDOWS] $p$g ; make sure that you have a C:\TEMP folder. If not, create it (recommended) or skip the followinf two lines SET TMP=C:\TEMP SET TEMP=C:\TEMP ;you may want to check your current path and add other direcotries to the following line SET PATH=C:\WINDOWS;C:\DOS; ;check your current codepage (with the "mode con cp /STATUS" command) and replace 437 (English codepage) with it, not really needed mode con cp prepare=((437) C:\DOS\EGA.CPI) mode con cp select=437 ;modify if your keyboard is not a default english one, not really needed keyb us,,C:\DOS\KEYBOARD.Sys SMARTDRV /X If you need networking with Windows FOR WORKGROUPS, use the following line, if you do not need or your windows is not FOR WORKGROUPS, skip it NET START END after copying these ones (and modifying them as needed as the comments say), reboot. See if there are not error messages. Anyway, try booting in Windows, it will probably work well. Also, chave you already reverted to the default drivers (VGA, MS Mouse, and etc.)? If not, do it, it is really a important step. Check before whether you have a himem.sys in your DOS folder. If there is none, replace "DEVICE=C:\DOS\HIMEM.SYS" with "DEVICE=C:\WINDOWS\HIMEM.SYS, as windows ships an older version of this file that will be enough as long as you do not have more than 64MB (the one that ships with DOS also have this flaw). If everything fails, post your config.sys, autoexec.bat and SYSTEM.INI
Report Offensive Follow Up For Removal
|
Use following form to reply to current message:
|
|

|