🚀 go-pugleaf

George Vlahoulis (s9312643@minyos.xx.rmit.EDU.AU) wrote:
> Hi all, I just upgraded my system from a 486-33dx 8MB to a P90 with 16MB and dos 
> sessions refuse to work. every time a dos session is started a SYS3175 error is
> returned and the session is killed.

> This happens for window and full screen. Now the copy of warp i have is the 
> gamma version and so I tried the GA version of 2.1 which I have installed in 
> another partition but the same thing happens. 

> I even reinstalled the 2.1 version thinking that that will help but it didnt.

> Nothing else is wrong its only the dos sessions that dont work. Very strange...

> Some details about my new system.

> PCI P90 with 16mb of ram
> Motherboard has inbuilt EIDE hd controller; used 
> PCI cirrus logic 5430 video card
> old hd controller used for the floppy drive.
> sb16asp
> panasonic cdrom

I forgot to mention that the motherboard has an award BIOS dated Apr 1995


> BTW: when I first tried to start warp because the internal hd controller was 
> used and the hd connection on the card in the isa slot was not disabled, it 
> crashed but when it was disabled it was fine.


> Please anyone if you now what is happening do email me as I have xposted it to 
> several newsgroups and I dont have the time to check all of them.

> thanks.

> PS: is there a way to change the video driver without having os2 accessing that 
> dos program which determines the hardware? I cant change my video driver I am 
> stuck with vga and 16 colors.



> --
> -/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-
>  s9312643@minyos.xx.rmit.edu.au    George Vlahoulis at
> 				   Royal Melbourne Institute Of Technology,
> 		    	           Melbourne Victoria Australia.

>  A professor is one who talks in someone else's sleep        -- W.A.Auden
> /-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/


--
-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-
 s9312643@minyos.xx.rmit.edu.au    George Vlahoulis at
				   Royal Melbourne Institute Of Technology,
		    	           Melbourne Victoria Australia.

 A professor is one who talks in someone else's sleep        -- W.A.Auden
/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/

In <3td5f6$cd1@aggedor.rmit.EDU.AU>, s9312643@minyos.xx.rmit.EDU.AU (George Vlahoulis) writes:
>Hi all, I just upgraded my system from a 486-33dx 8MB to a P90 with 16MB and dos 
>sessions refuse to work. every time a dos session is started a SYS3175 error is
>returned and the session is killed.
>
>Nothing else is wrong its only the dos sessions that dont work. Very strange...

Just a thought - when reconfiguring the system, did you reboot, use 
Alt-F1 and then select reversion to VGA? If so, I suggest reinstalling
the VGA drivers from the selective install object. I have seen the 
behaviour you describe on other systems.

Re: reinstalling video drivers without running SVGA.EXE: I'd suggest 
trying SVGA ON DOS under DOS, then renaming the resulting SVGADATA.DOS
to SVGADATA.PMI. Then, replace the SVGA.EXE program with anything else
that will run ineffectively - maybe XCOPY.EXE or something. It will 
produce an error message but won't over-write the SVGADATA.PMI file 
you've already created and installation can then continue correctly.

An alternative technique is to replace the Warp SVGA.EXE with the 2.11
SVGA.EXE - it will still work.

In both cases, be advised that after installation, the UNPACK utility 
will have unpacked a new copy of the Warp SVGA.EXE so you'll need to 
replace it before reinstalling each time. If you have the Warp 
toolkit, you can use the PACK utility to create an updated VGA file 
(I've been meaning to get around to doing that for my own system).

--- Les

+--------------------------------------------------------+
| Les Bell                          Tel: +61 2 953 7619  |
| lesbell@ibm.net                   Fax: +61 2 953 0602  |
| lesbell@syd.interconnect.com.au   PO Box 297           |
| lesbell@acslink.net.au            Neutral Bay NSW 2089 |
| CIS: 71210,104                    Australia            |
+--------------------------------------------------------+

Les Bell (lesbell@ibm.net) wrote:
> In <3td5f6$cd1@aggedor.rmit.EDU.AU>, s9312643@minyos.xx.rmit.EDU.AU (George Vlahoulis) writes:
> >Hi all, I just upgraded my system from a 486-33dx 8MB to a P90 with 16MB and dos 
> >sessions refuse to work. every time a dos session is started a SYS3175 error is
> >returned and the session is killed.
> >
> >Nothing else is wrong its only the dos sessions that dont work. Very strange...

> Just a thought - when reconfiguring the system, did you reboot, use 
> Alt-F1 and then select reversion to VGA? If so, I suggest reinstalling
> the VGA drivers from the selective install object. I have seen the 
> behaviour you describe on other systems.

Yes I did exactly that but since I cant have a dos session I cant change 
the drivers.

> Re: reinstalling video drivers without running SVGA.EXE: I'd suggest 
> trying SVGA ON DOS under DOS, then renaming the resulting SVGADATA.DOS
> to SVGADATA.PMI. Then, replace the SVGA.EXE program with anything else
> that will run ineffectively - maybe XCOPY.EXE or something. It will 
> produce an error message but won't over-write the SVGADATA.PMI file 
> you've already created and installation can then continue correctly.

Well I did that and it said "unsuported adapter or chipset" Ha!!!!!!!!!

Why is it then that 2.1 when I reinstalled knew that it was a cirrus 
logic? and in warp its listed in the drivers supported? 


> An alternative technique is to replace the Warp SVGA.EXE with the 2.11
> SVGA.EXE - it will still work.

i'll give that a try and see what happens


> In both cases, be advised that after installation, the UNPACK utility 
> will have unpacked a new copy of the Warp SVGA.EXE so you'll need to 
> replace it before reinstalling each time. If you have the Warp 
> toolkit, you can use the PACK utility to create an updated VGA file 
> (I've been meaning to get around to doing that for my own system).

thanks a lot.

> --- Les 

> +--------------------------------------------------------+
> | Les Bell                          Tel: +61 2 953 7619  |
> | lesbell@ibm.net                   Fax: +61 2 953 0602  |
> | lesbell@syd.interconnect.com.au   PO Box 297           |
> | lesbell@acslink.net.au            Neutral Bay NSW 2089 |
> | CIS: 71210,104                    Australia            |
> +--------------------------------------------------------+


--
-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-
 s9312643@minyos.xx.rmit.edu.au    George Vlahoulis at
				   Royal Melbourne Institute Of Technology,
		    	           Melbourne Victoria Australia.

 A professor is one who talks in someone else's sleep        -- W.A.Auden
/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/

In <3tgaal$fue@aggedor.rmit.EDU.AU>, s9312643@minyos.xx.rmit.EDU.AU (George Vlahoulis) writes:
>> Just a thought - when reconfiguring the system, did you reboot, use 
>> Alt-F1 and then select reversion to VGA? If so, I suggest reinstalling
>> the VGA drivers from the selective install object. I have seen the 
>> behaviour you describe on other systems.
>
>Yes I did exactly that but since I cant have a dos session I cant change 
>the drivers.

You can install straight VGA support, since SVGA.EXE isn't run for 640
x 480 x 16, as far as I can recall.

--- Les

+--------------------------------------------------------+
| Les Bell                          Tel: +61 2 953 7619  |
| lesbell@ibm.net                   Fax: +61 2 953 0602  |
| lesbell@syd.interconnect.com.au   PO Box 297           |
| lesbell@acslink.net.au            Neutral Bay NSW 2089 |
| CIS: 71210,104                    Australia            |
+--------------------------------------------------------+

Les Bell (lesbell@ibm.net) wrote:
> In <3tgaal$fue@aggedor.rmit.EDU.AU>, s9312643@minyos.xx.rmit.EDU.AU (George Vlahoulis) writes:
> >> Just a thought - when reconfiguring the system, did you reboot, use 
> >> Alt-F1 and then select reversion to VGA? If so, I suggest reinstalling
> >> the VGA drivers from the selective install object. I have seen the 
> >> behaviour you describe on other systems.
> >
> >Yes I did exactly that but since I cant have a dos session I cant change 
> >the drivers.

Sorry I didnt make my self clear. I am running at 640x480x16 but I cant 
change to something better. 

I did what you suggested, with the 2.11 svga and I did get a svgadata.dos 
but I couldnt make it work cos it would try to start a vdm and since that 
doesnt work it reports that it didnt work and doesnt change anything.

To make things more strange, under warp gamma winos2 version rmview 
reports that the cpu is a 586, correct. when I went to install the copy 
of warp that I bought (warp for windows) rmview says its a 486 HA!!!!!

Furthermore when it migrated some of the apps it found on the hd which 
included Epic Pinball, I started Epic Pinball up and to my complete 
suprise it worked!!!!!  but typing start /dos in a vio session still 
gives me that stupid sys3176 error, as well as changing the video drivers. 
So I went and copied the Pinball 
object and made it a plain dos session and now I can have a dos win/full 
screen session only from those objects and copies of. Talking about wierd.

Since I am running out of patients with this I will try to change the 
video card (which I think might be the problem). If this doesnt work the 
motherboard goes back.

George.

> You can install straight VGA support, since SVGA.EXE isn't run for 640
> x 480 x 16, as far as I can recall.

> --- Les

> +--------------------------------------------------------+
> | Les Bell                          Tel: +61 2 953 7619  |
> | lesbell@ibm.net                   Fax: +61 2 953 0602  |
> | lesbell@syd.interconnect.com.au   PO Box 297           |
> | lesbell@acslink.net.au            Neutral Bay NSW 2089 |
> | CIS: 71210,104                    Australia            |
> +--------------------------------------------------------+


--
-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-
 s9312643@minyos.xx.rmit.edu.au    George Vlahoulis at
				   Royal Melbourne Institute Of Technology,
		    	           Melbourne Victoria Australia.

 A professor is one who talks in someone else's sleep        -- W.A.Auden
/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/

I have just read your tales of woe with regaed to installing os2.  It 
didn't mean much to me untill you mentioned that the BIOS was an AWARD 
BIOS.  I bought a P90 with AWARD BIOS toward the beginning of the year 
and found a large number of compatibity problems.  I took it back to my 
suppier and got it exchanged for a good American made board with AMI 
BIOS.  Since then the number of problems I hear about with AWARD BIOS's 
is getting greater.

If somebody askes me for advice now the first question I ask is the type 
of BIOS.  It might be a coincidence, but the number of "weired" 
compatibility faults I encounter have the AWARD BIOS.

You could try turning the External Cache off.

Hope this is of assistance.

                            David Oliver

David Oliver (doliver@ozemail.com.au) wrote:
: I have just read your tales of woe with regaed to installing os2.  It 
: didn't mean much to me untill you mentioned that the BIOS was an AWARD 
: BIOS.  I bought a P90 with AWARD BIOS toward the beginning of the year 
: and found a large number of compatibity problems.  I took it back to my 
: suppier and got it exchanged for a good American made board with AMI 
: BIOS.  Since then the number of problems I hear about with AWARD BIOS's 
: is getting greater.

*SIGH*  Time for another posting on this subject, I guess....

1) You changed the BIOS, chipset, motherboard manufacturer, and various
   and sundry other things, and ANY of these could have caused the
   problems you had.  In fact, I'd argue that the chipset is a more
   likely culprit than the BIOS, at least for generic sorts of problems
   under a multitasking, protected-mode OS like OS/2, which doesn't
   even use the BIOS for much once it's booted.
2) There is not such thing as "the" Award BIOS, or even "the" Award BIOS
   version 4.50G (the most commonly-cited "version" of "the" Award BIOS
   at the moment).  Every manufacturer which licenses a BIOS from Award
   makes various major and minor modifications to the BIOS for a variety
   of reasons, and yet the version number of 4.50G stays the same.  Some
   manufacturers have multiple revisions of "the" 4.50G Award BIOS.  Thus,
   a problem which is tracked to the BIOS on one particular machine using
   "the" Award BIOS may not exist on another machine with "the same" BIOS,
   because the BIOS is NOT the same.  Even an earlier or later revision of
   the same model motherboard may not exhibit the problem because the
   manufacturer may have revised the BIOS.
3) You may have noticed lots of posts about problems with "the" Award BIOS
   for a number of reasons:
   a) It's a popular BIOS at the moment, and so can easily wind up in
      machines with other problems.
   b) You've been sensitized to it by your bad experience with a machine
      having that BIOS.
   c) These types of posts tend to feed on themselves, drawing comments
      relaying similar (or dissimilar) experiences.

I certainly can't deny the possibility that the original poster's 
problems are related to his BIOS, but I feel compelled to point out that 
picking on the BIOS is frequently unjustified, or at least insufficiently 
justified.  FWIW, I've got a motherboard with a variety of Award 4.50G 
BIOS [it's an Asus PCI-486SP3G], and I have no BIOS-related problems with 
it.  I've seen other posts from others with the same (and other) 
motherboards with Award BIOSes that have no problems.  I therefore 
conclude that problems in machines that use Award BIOSes:

1) May be due to problems in the motherboard or other components unrelated
   to the BIOS;
2) May be due to problems in specific revisions of the BIOS introduced by
   the problem board's manufacturer, or in the original code and not fixed
   by some manufacturers but fixed by others;
3) May be due to a combination of 1 & 2 -- a bug in the BIOS which interacts
   with a hardware design.

--
					--Rod Smith
					  RSMITH@PSYCH.COLORADO.EDU

George Vlahoulis (s9312643@minyos.xx.rmit.EDU.AU) wrote:
: Hi all, I just upgraded my system from a 486-33dx 8MB to a P90 with 16MB and dos 
: sessions refuse to work. every time a dos session is started a SYS3175 error is
: returned and the session is killed.

I made some changes to my system and I think I was getting the same 
SYS3175 error.  I deleted and recreated the 2  ini files and rebooted 
WARP.  This took care of the problem.  The command was makeini.  The ini 
files were os2.ini and os2sys.ini.  They are made from the ini.rc and 
inisys.rc files.  Try this and let  me know how it works.  Also, 
remember, to backup FIRST!  Todd

Todd Morgan (todd@marlin.ssnet.com) wrote:
> George Vlahoulis (s9312643@minyos.xx.rmit.EDU.AU) wrote:
> : Hi all, I just upgraded my system from a 486-33dx 8MB to a P90 with 16MB and dos 
> : sessions refuse to work. every time a dos session is started a SYS3175 error is
> : returned and the session is killed.

> I made some changes to my system and I think I was getting the same 
> SYS3175 error.  I deleted and recreated the 2  ini files and rebooted 
> WARP.  This took care of the problem.  The command was makeini.  The ini 
> files were os2.ini and os2sys.ini.  They are made from the ini.rc and 
> inisys.rc files.  Try this and let  me know how it works.  Also, 
> remember, to backup FIRST!  Todd

well a complete reinstall would have fixed it dont you think? BTW: thats 
(sys3175) on GA 2.1 on warp it sys3176.....

--
-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-
 s9312643@minyos.xx.rmit.edu.au    George Vlahoulis at
				   Royal Melbourne Institute Of Technology,
		    	           Melbourne Victoria Australia.

 A professor is one who talks in someone else's sleep        -- W.A.Auden
/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/

In article <3tjmkp$dnl@oznet03.ozemail.com.au>
           doliver@ozemail.com.au "David Oliver" writes:

> I have just read your tales of woe with regaed to installing os2.  It 
> didn't mean much to me untill you mentioned that the BIOS was an AWARD 
> BIOS.  I bought a P90 with AWARD BIOS toward the beginning of the year 
> and found a large number of compatibity problems.  I took it back to my 
> suppier and got it exchanged for a good American made board with AMI 
> BIOS.  Since then the number of problems I hear about with AWARD BIOS's 
> is getting greater.
> 
> If somebody askes me for advice now the first question I ask is the type 
> of BIOS.  It might be a coincidence, but the number of "weired" 
> compatibility faults I encounter have the AWARD BIOS.
> 
> 
>                             David Oliver
You should send info about this to the Good, Bad, and Ugly (GBU) hardware
list that is kept about compatability of hardware with OS2.  You can 
find it on the major OS2 ftp servers (hobbes, cdrom) its called GBU###.zip
where ### is its current version number.  I forget what dir its in it though.
 
-- 
Scott A Wymer     ***Scott@wymer.demon.co.uk***
***Be happy for you have been given 
  the two greatest gifts            
  LIFE and the TIME to live it ***   

s9312643@minyos.xx.rmit.EDU.AU (George Vlahoulis) writes:

>Hi all, I just upgraded my system from a 486-33dx 8MB to a P90 with 16MB and dos 
>sessions refuse to work. every time a dos session is started a SYS3175 error is
>returned and the session is killed.

>This happens for window and full screen. Now the copy of warp i have is the 
>gamma version and so I tried the GA version of 2.1 which I have installed in 
>another partition but the same thing happens. 

Hi,
	I had a similar problem when I upgraded to Warp Blue Box from Warp Beta
I.  The way I FINALLY found to fix this was to turn ON (not OFF, as my the Warp
manual recommends) Video BIOS shadowing and 256Kb remap (old AMI BIOS) in my
extended BIOS options.  After that - not one problem with DOS sessions!  Hope
this helps!


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% Brad van Eps                              E-Mail: vaneps@elec.uq.edu.au     %
% Ph: (07) 365 7592                                                           % 
%                                           "I don't need my fortune told     % 
% Department of Electrical                   The future's already known       %
%  and Computer Engineering                  I got my cover                   % 
% The University of Queensland               Sisters and Brothers             %
% QLD,  4072                                 To keep me from burning in Hell" %
% Australia                                     "Stepping On Toes", X-Sinner  %
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

In <3tdc8a$fe0@aggedor.rmit.EDU.AU>, s9312643@minyos.xx.rmit.EDU.AU (George Vlahoulis) writes:
>George Vlahoulis (s9312643@minyos.xx.rmit.EDU.AU) wrote:

>> PS: is there a way to change the video driver without having os2 accessing that 
>> dos program which determines the hardware? I cant change my video driver I am 
>> stuck with vga and 16 colors.

I had this problem and called OS/2 tech support.  Their answer:  open a 
full screen DOS session and run svga.exe -status in the \os2 directory.
This will tell you the chipset of your display card.  Then, if the EXACT 
chipset is not supported within OS/2, you must get the drivers from the
manufacturer.  Usually you can call the manufacturer's BBS to download
these drivers.  Otherwise the display will say "Unknown hardware 
configuration" and you'll be stuck in standard VGA mode with 16 colors.

Of course, in order to access svga.exe, you must get your DOS session problem
fixed first.

Good luck to you.

In <3tvgl7$h7g@dingo.cc.uq.oz.au>, vaneps@s4.elec.uq.edu.au (Brad van Eps) writes:
>s9312643@minyos.xx.rmit.EDU.AU (George Vlahoulis) writes:
>
>>Hi all, I just upgraded my system from a 486-33dx 8MB to a P90 with 16MB and dos 
>>sessions refuse to work. every time a dos session is started a SYS3175 error is
>>returned and the session is killed.
>
..SNIP...
>Hi,
>	I had a similar problem when I upgraded to Warp Blue Box from Warp Beta
>I.  The way I FINALLY found to fix this was to turn ON (not OFF, as my the Warp
>manual recommends) Video BIOS shadowing and 256Kb remap (old AMI BIOS) in my
>extended BIOS options.  After that - not one problem with DOS sessions!  Hope
>this helps!
>
He's right, you know, remapped and shadowed memory plays havoc with 
protected-mode OS's; besides, these features only work well with stuff that relies
on BIOS calls.
!===/!=*  !=!-*==!-*==!***=*=======/==========================================!
!  / ! !* ! !  ! !  ! !     *   / / bosch@mcs.com OR abosch@elca.org          !
! /**! ! *! !  ! !-*  !**    * / /                                KA9VYG      !
!/   !=!  *=!-*==!==*=!***====/=/===========================Member ARRL&IEEE==!

brharris@umr.edu wrote:
> In <3tdc8a$fe0@aggedor.rmit.EDU.AU>, s9312643@minyos.xx.rmit.EDU.AU (George Vlahoulis) writes:
> >George Vlahoulis (s9312643@minyos.xx.rmit.EDU.AU) wrote:

> >> PS: is there a way to change the video driver without having os2 accessing that 
> >> dos program which determines the hardware? I cant change my video driver I am 
> >> stuck with vga and 16 colors.

> I had this problem and called OS/2 tech support.  Their answer:  open a 
> full screen DOS session and run svga.exe -status in the \os2 directory.
> This will tell you the chipset of your display card.  Then, if the EXACT 
> chipset is not supported within OS/2, you must get the drivers from the
> manufacturer.  Usually you can call the manufacturer's BBS to download
> these drivers.  Otherwise the display will say "Unknown hardware 
> configuration" and you'll be stuck in standard VGA mode with 16 colors.

> Of course, in order to access svga.exe, you must get your DOS session problem
> fixed first.

> Good luck to you.

Thanks well I am changing my motherboard to an AMI one so I really hope 
all problems will go away. 

And I was thinking to spend my two weeks off school programming os2.

Oh well!

--
-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-
 s9312643@minyos.xx.rmit.edu.au    George Vlahoulis at
				   Royal Melbourne Institute Of Technology,
		    	           Melbourne Victoria Australia.

 A professor is one who talks in someone else's sleep        -- W.A.Auden
/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/

On 14 Jul 1995 brharris@umr.edu wrote:

> In <3tdc8a$fe0@aggedor.rmit.EDU.AU>, s9312643@minyos.xx.rmit.EDU.AU (George Vlahoulis) writes:
> >George Vlahoulis (s9312643@minyos.xx.rmit.EDU.AU) wrote:
> 
> >> PS: is there a way to change the video driver without having os2 accessing that 
> >> dos program which determines the hardware? I cant change my video driver I am 
> >> stuck with vga and 16 colors.
> 
> I had this problem and called OS/2 tech support.  Their answer:  open a 
> full screen DOS session and run svga.exe -status in the \os2 directory.
> This will tell you the chipset of your display card.  Then, if the EXACT 
> chipset is not supported within OS/2, you must get the drivers from the
> manufacturer.
> 
> Of course, in order to access svga.exe, you must get your DOS session problem
> fixed first.

SVGA.EXE is a dual-mode program which will also run in "real" DOS... now 
where did I put that DOS 5 boot floppy? :-)

Gary
--
gwoodman@pcug.org.au        OS/2 Warp: Mac easy, Unix strong, PC heritage!
gwoodman@sma.gov.au

bosch@mcs.com wrote:
>In <3tvgl7$h7g@dingo.cc.uq.oz.au>, vaneps@s4.elec.uq.edu.au (Brad van Eps) writes:
>>s9312643@minyos.xx.rmit.EDU.AU (George Vlahoulis) writes:
>>
>>>Hi all, I just upgraded my system from a 486-33dx 8MB to a P90 with 16MB and dos 
>>>sessions refuse to work. every time a dos session is started a SYS3175 error is
>>>returned and the session is killed.
>>
>..SNIP...
>>Hi,
>>	I had a similar problem when I upgraded to Warp Blue Box from Warp Beta
>>I.  The way I FINALLY found to fix this was to turn ON (not OFF, as my the Warp
>>manual recommends) Video BIOS shadowing and 256Kb remap (old AMI BIOS) in my
>>extended BIOS options.  After that - not one problem with DOS sessions!  Hope
>>this helps!
>>
>He's right, you know, remapped and shadowed memory plays havoc with 
>protected-mode OS's; besides, these features only work well with stuff that relies
>on BIOS calls.

Well I did try turning all those off and that didnt help. Anyway I changed the motherboard to a
AMI bios and now there is no problem. I am curious though as to why rmview says that its a 486.

the gamma version of warp with windows said that the award bios one was a 586, but it said it
only once. Hmmmmm.....


Would warp install differently if it knew that it was a pentium? And what differences are you
talking about?
-- 
-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-
 s9312643@minyos.xx.rmit.edu.au    George Vlahoulis at
				   Royal Melbourne Institute Of Technology,
		    	           Melbourne Victoria Australia.

 A professor is one who talks in someone else's sleep        -- W.A.Auden
/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/

George Vlahoulis (s9312643) wrote:
> bosch@mcs.com wrote:
> >In <3tvgl7$h7g@dingo.cc.uq.oz.au>, vaneps@s4.elec.uq.edu.au (Brad van Eps) writes:
> >>s9312643@minyos.xx.rmit.EDU.AU (George Vlahoulis) writes:
> >>
> >>>Hi all, I just upgraded my system from a 486-33dx 8MB to a P90 with 16MB and dos 
> >>>sessions refuse to work. every time a dos session is started a SYS3175 error is
> >>>returned and the session is killed.
> >>
> >..SNIP...
> >>Hi,
> >>	I had a similar problem when I upgraded to Warp Blue Box from Warp Beta
> >>I.  The way I FINALLY found to fix this was to turn ON (not OFF, as my the Warp
> >>manual recommends) Video BIOS shadowing and 256Kb remap (old AMI BIOS) in my
> >>extended BIOS options.  After that - not one problem with DOS sessions!  Hope
> >>this helps!
> >>
> >He's right, you know, remapped and shadowed memory plays havoc with 
> >protected-mode OS's; besides, these features only work well with stuff that relies
> >on BIOS calls.

> Well I did try turning all those off and that didnt help. Anyway I changed the motherboard to a
> AMI bios and now there is no problem. I am curious though as to why rmview says that its a 486.

> the gamma version of warp with windows said that the award bios one was a 586, but it said it
> only once. Hmmmmm.....

> Would warp install differently if it knew that it was a pentium? And what differences are you
> talking about?

Well curiousity got the better of me and I made the startup disk for the 
gamma version of os2 with winos2 and checked what rmview said the system was.

Well its a 586!!!! Which kind of makes sense. The board bios is dated oct 
'94 which is about the time warp for windows came out, which means it 
most likely wouldnt have known about my new motherboard.

George.

--
-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-
 s9312643@minyos.xx.rmit.edu.au    George Vlahoulis at
				   Royal Melbourne Institute Of Technology,
		    	           Melbourne Victoria Australia.

 A professor is one who talks in someone else's sleep        -- W.A.Auden
/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/