pcb@usl.usl.edu (Peter C. Bahrs) (03/26/89)
We just changed working environments. I want to use SDK 2.1, Codeview and Windows 386. I have all of the software installed properly. I have an IBM PS/2 Model 80 with 2mb memory. Is this extended memory? (I think so...) Codeview wants a... memory manager to be loaded (I think something like emm.sys??) in order to run. Hmmmm.... Smartdrive was installed when SDK et.al was loaded and I put himem.sys in config.sys also. These two shouldn't have anything to do with it. Does anyone have Codeview under win386 running on a Model 80 (the standard configuration vga, 2MB Memory but 300mb HD) running. Am I stuck because it has extended instead of expanded memory?? Is there a *.sys driver available to correct this situation? Thanks in advance... /*-----------------------------------------------------------------------+ | Peter C. Bahrs UUCP ... !uunet!dalsqnt!usl!pcb | | The USL-NASA Project ... !cs.utexas.edu!usl!pcb | | Center For Advanced Computer Studies INET pcb@usl.usl.edu | | University of Southwestern Louisiana | | Lafayette, LA 70504 | +-----------------------------------------------------------------------*/
dennis@se-sd.sandiego.ncr.com (Dennis Foster) (03/28/89)
In article <781@usl.usl.edu> pcb@usl.usl.edu (Peter C. Bahrs) writes: > >We just changed working environments. I want to use SDK 2.1, Codeview and >Windows 386. I have all of the software installed properly. I have >an IBM PS/2 Model 80 with 2mb memory. > >Is this extended memory? (I think so...) Codeview wants a... >memory manager to be loaded (I think something like emm.sys??) in order >to run. > > ... stuff deleted ... > >Does anyone have Codeview under win386 running on a Model 80 (the standard >configuration vga, 2MB Memory but 300mb HD) running. Am I stuck because >it has extended instead of expanded memory?? Is there a *.sys driver available >to correct this situation? > > ... more stuff deleted ... You need to read through the READ ME file that came with the 2.1 SDK. Basicially, what you need to do is the following: 1) Change to your windows/386 subdirectory. 2) Rename the file WIN86.COM to WIN.COM. 3) Copy your COMMAND.COM (from wherever it's at) into a file named WIN86.COM in your windows/386 directory. Now, to use CodeView, you change directories to your windows/386 node and execute win386. After a short delay, it will look like you are running in another DOS shell. Well you are, it's just that that shell is running in a virtual machine under windows/386. Also, all your free extended memory is now expanded memory! From one of these DOS prompts, execute CodeView (i.e., cvw /2 /l frob.exe win.com frob.exe). The example would run CodeView on a secondary monitor using FROB.EXE as the source of symbol information and running FROB.EXE once windows starts up. When you leave CodeView/Windows, you may want to enter EXIT at a DOS prompt to leave the windows/386 virtual machine manager/memory manager.