HDTenEightyP/NetNews huggingface dataset:
From: centaur@terminus.gatech.edu (Anthony G. Francis)
Subject: Re: Windows 3.1 Bugs - Threat or Menace?
Keywords: windows 3.1 bug
Organization: Georgia Tech College of Computing
Date: Wed, 8 Apr 1992 21:18:27 GMT

vargish@sura.net (Nicholas Vargish) writes:
>In article <centaur.702709253@cc.gatech.edu> centaur@terminus.gatech.edu (Anthony G. Francis) writes:
>>Under Windows, I run BACKDESK as my shell, with Screen Peace, Change Cursor,
>>Wired For Sound, and File Manager. Loading Windows under these conditions
>>has produced the following bugs:

>>Spontaneous Crash of BigDesk, usually after some other winapp goes down
>>Crash of Backmenu on Windows Exit
>>Crash of WinGif on 256 color BMPs
>>Crash of Program Manager (!!!) when I attempt to delete empty program groups,
>>      plus one spontaneous crash
>I've seen this, but I thought it was related to the SuperStor problem,
>or possibly NDW 1.0.

These all appear related. Booting Progman as the shell causes WINGIF to merely
report "could not read image description" on the attempted load of any GIF,
and Progman groups will now delete. It's probably an interaction between
the new Progman and Backmenu's own access of the Progman groups

>>Failure of the DOS program Eye of the Beholder to load
>In a window or full screen? Trying to run a game as fancy as EOB under
>Windows is asking for trouble. Most games are less carefully debugged
>than most apps (although I'm beginning to wonder...), and many of them
>do "unexpected" things to wring the max performance from a system.
>Windows may not be able to handle this. [Wing Commander II can be
>multi-tasked under OS/2 ok, though! or so I've been told... :^)]

Full screen; it locks up. Haven't tried EOB ][ yet; since it won't run
under Win 3.0, maybe it will run under 3.1; of course, it could be an
interaction between Window's sound driver and EOB's, which is simply
not acceptable behavior on Windows' part; EOB worked just fine with
_two_ sound drivers running under Windows 3.0.

-Anthony Francis
--
Anthony G. Francis, Jr.  - Georgia Tech {Atl.,GA 30332}
Internet Mail Address: 	 - centaur@cc.gatech.edu
UUCP Address:		 - ...!{allegra,amd,hplabs,ut-ngp}!gatech!prism!gt4864b
-------------------------------Quote of the post------------------------------ 
"Cerebus doesn't love you ... Cerebus just wants all your money" 
		- Cerebus the Aardvark, from a _Church and State_ T-shirt
------------------------------------------------------------------------------
From: gordons@coopsol.com (Gordon Storga)
Newsgroups: comp.windows.ms
Subject: Re: HELP! Win 3.1 dies in setup mode
Date: 13 Apr 92 16:23:32 GMT
Distribution: usa
Organization: Stay Awake Software

<3000@cvbnetPrime.COM> kanderse@cvbnet.prime.com (Kurt Andersen x3056 5-2) said:
>In article <1992Apr7.052129.28470@beach.csulb.edu>, bwong@beach.csulb.edu (Bradley Wong) writes:
>|> I can NOT get past the 93% second diskette setup mode where win 3.1
>|> goes from DOS setup to windows setup. 
>|> 
>|> All I get is:
>|> 
>|>    Standard Mode: Fault in MS-DOS extender
>|>    EC=0000 CS=0053 IP=232F ...
>|> 
>I get the same error Error.  The error actual comes from program
>WINDOS/SYSTEM/DOSX.EXE.  I can't find any documentation on what
>this program does (I think it is a dos extender/memory manager used
>for starting windows during setup).  The 3.0 version of DOSX works fine.
>Also when I remove the 3.0 DOSX, Windows 3.0 works fine without it.
>
>I'm using a Gateway 486 (33Mhz genisis/microcronics) with 8m memory.
>300 Meg ESDI harddisk.  I'm currently using DRDOS 6.0 with QEMM 6.0.
>
>Any help would be appreciated.

Check the manual.  It specifically recommends that you use the HIMEM.SYS
and the EMM386.EXE that came with 3.1.  I had the same problems until I
rebooted with these two things installed.  Unfortunately I had to do it
myself with EXPAND because the process aborted too early.  A pretty piss
poor setup if you ask me, because I was using DOS 5.0 HIMEM.SYS and EMM386
and they didn't work either.  Jeez, if MS can't even keep consistent with
their own software...

Also, I haven't noticed one bit of performance improvement.  In fact, it
takes 2 seconds longer to load MS Word2.0 than it did with 3.0.


Gordon
-- 

The opinions expressed are my own, and not the beliefs or opinions
of whatever company you think I work for.  So there, thhhbbbt!
Message to Kodak:  Freedom for Dan Bredy.
Newsgroups: comp.windows.ms
From: hu@helios.physics.utoronto.ca (Min Hu)
Subject: help needed in using faxmodem under win3.0
Organization: University of Toronto Physics/Astronomy/CITA
Distribution: University of Toronto
Date: Mon, 13 Apr 1992 01:26:02 GMT

      Recently I bought an Aceex9624 internal FaxModem. It works fine
under DOS.
      But under window3, it does not work for both terminal and doswindow.
Plus, if I use window first and then use modem, it does not work also.
I have to reboot(reset) the system again to make modem works. It seems
to me that the communication port for modem is disabled somehow by 
window. 
     I used com4 for my modem. Com1 is used by mouse. And I use bitcom
communication software. (By the way, I have tried com2, com3, they do
not work for me)
     Anybody out there, know how to solve this problem. Your help will
be greatly appreciated. Thank you. 

			MIN HU
From: rh0i+@andrew.cmu.edu (Richard Warren Harris)
Newsgroups: comp.windows.ms
Subject: 3.1 Driver installation screwed up, or am I?
Date: 7 Apr 92 12:07:23 GMT
Organization: Senior, Social & Decision Sciences, Carnegie Mellon, Pittsburgh, PA

Hi,

I'm *trying* to install the AdLib sound card driver onto 3.1.  I'm not
having much luck.

I go through the whole procedure with clicking open the Control Panel
and opening Drivers, and then using Add to load the AdLib driver
(msadlib.drv), but all it does is physically copy the driver file into
the system directory.  It doesn't actually reconfigure anything
(though it does allow me to restart windows as if it had).

More puzzling, still, is that going into the system.ini file, and
changing

sound.drv=mmsound.drv (the default) 

to

sound.drv=msadlib.drv (what *seems* to be the thing to do)

obviously is *not* the thing to do, since windows aborts during
startup when I do that.

Has this problem already been solved here?  If so, could somebody tell
me what the solution was?

Thanks,
- Rick

-------------------------------------------------------------------------------
Rick Harris 		| 	Information & Decision Systems/Computer Science
Senior.  Finally.	|	Social & Decision Sciences Department
rh0i+@andrew.cmu.edu	|	Carnegie Mellon (so hire me)
------------------------------------------------------------------------------

	"I not only want a car that is built in accordance with the basic 
	principles of physics and in light of an empirically verified, 
	well-winnowed tradition of automobile design, but I also want it 
	screwed together right."

		- Edward W. Constant II, "The Social Locus of Technological 
		      Practice:  Community, System, or Organization?"
From: grohol@novavax.UUCP (John Grohol)
Newsgroups: comp.windows.ms
Subject: Re^2: AmiPro 2.0 and Win 3.1
Date: 16 Apr 92 16:47:54 GMT
Organization: Nova University, Fort Lauderdale, FL


If you're having problems running Ami Pro 2.0 minimized, do it the
old 3.0 way, which I have been doing successfuly since I've
gotten 3.1:

Simply put Ami Pro in the "load=" statement at the beginning
of your win.ini file. This has always worked fine for me.

Remember to take it out of the startup group also though!
Put it back in the Main group or somewhere else...


-- 
 "And everybody used to hang around him.  ::  John M. Grohol, M.S.
  And I know why. They said:              ::  Cntr for Psychological Studies
  There but for the grace of the angels   ::  Nova Univ, Ft. Lauderdale, FL  
  go I." -- Laurie Anderson               ::  grohol@novavax.nova.edu
Newsgroups: comp.windows.ms
From: Iskandar Taib <ntaib@silver.ucs.indiana.edu>
Subject: Re: When DR scams, it's ok?  Was Re: Win3.1/DR DOS 6.0/SuperS...
Organization: Indiana University
Date: Thu, 9 Apr 1992 20:19:44 -0500

In article <8APR199218274573@zeus.tamu.edu> rfs0838@zeus.tamu.edu (SCHAFFTER, RODNEY FRANK, JR) writes:

>	Why would you expect parts of DR-DOS to work with MS-DOS?
>Just last night I tried to xcopy a disk that has XCOPY on it from MS-DOS
>3.31( a lovely operating system in its day-probably MS's best work!).
>Naturally, it tried to run the xcopy program on the disk, which didn't work.
>Did I curse MS or DR for this "incompatability"? No!

You know, I wonder if the SETVER utility works on various DOS
applets from older versions? It sure works for NET4...





-- 
-------------------------------------------------------------------------------
Iskandar Taib                          | The only thing worse than Peach ala
Internet: NTAIB@SILVER.UCS.INDIANA.EDU |    Frog is Frog ala Peach
Bitnet:   NTAIB@IUBACS                 !
-------------------------------------------------------------------------------
From: dsferrel@uncc.edu (Derek Sean Ferrell)
Newsgroups: comp.windows.ms
Subject: Re: Windows 3.1 Review
Date: 14 Apr 92 16:38:07 GMT
Reply-To: dsferrel@uncc.edu
Organization: University of NC at Charlotte

In article 44316@mentor.cc.purdue.edu, rusbasan@sage.cc.purdue.edu (Bob Rusbasan) writes:
>
>I'm surprised no on has reviewed Windows 3.1 yet.  Since I've had time 
>to play with it for a while, I thought I'd do the honors...
>

thanks....it was needed.


>Windows 3.0 really made it clear that it was a non-preemptive 
>environment 

hmmm, true in a sense. But don't leave out the fact that Windows 3.1 (and 3.0) preemtively multitasks DOS applications on a '386 or better, which I find performs remarkably well with Win 3.1. Case in point: I started a DOS session and ran Alltype to convert some of my postscript fonts to Truetype (a time-consuming process at best). I opened another DOS session and ran Qmodem 4.5 and performed a 40-minute download from a local BBS. I then ran W4W and typed a letter. In 45 minutes, I had my fonts, my downloa




ded file, and had typed my letter and printed it, thus I was able to go to bed early for the first time in months and still feel like I had met my "computer-geek" obligations for the day :)



>(I'd say "operating system," but then a bunch of anal-
>retentive weenies with nothing better to do would freak out, change 
>the subject to "Windoze an OS?  (Was: Windows 3.1 Review)",  crosspost 
>it to the OS/2 groups, and flame away). 

hehehehehehehehe. Good one!



>In short, I heartily recommend it.  I am very happy with it. 


me too!  (and I use Stacker 2.0.......GASP!)



Derek S. Ferrell
From: sexonbd@sage.cc.purdue.edu (Benjamin David Sexson (Ben))
Newsgroups: comp.windows.ms
Subject: Re: Why go to 3.1 if 2.0 works
Date: 11 Apr 92 17:49:59 GMT
Article-I.D.: mentor.44908
Organization: Purdue University Computing Center

He has a good question.  Which is better Windows 3.1 and DOS 5.0
or OS/2 2.0.  OS/2 has many advantages from what I know, but Windows
has the Apps behind it.  My question is when will someone make an OS
for the Intel chip in assembly language.  I don't have the 15 to 30 MB
it takes for OS/2 and I barley have the system for Windows.  I wonder if
Geoworks would make an OS and more Apps. If they would I would probably 
switch.
					Ben Sexson
I would request any flames through e-mail, and any intelligent responses
through the news.  I am open to different opinions.
					sexonbd@sage.cc.purdue.edu
From: ehrlich@bucknell.edu (David Ehrlich -- BSCS '92)
Newsgroups: comp.windows.ms
Subject: CTRL-D Thing & Windows 3.1 Surprise
Date: 6 Apr 92 20:32:44 GMT
Distribution: world
Organization: Bucknell University, Lewisburg, Pa.

I just printed a paper on our SunOS network which was written using WFW 2.0, and Windows 3.1.  I set the paper up assuming printing on an Apple Laserwriter.  I printed the paper to an EPS file, transferred the file to the network and sent the print job directly to the printer.  Two important notes:  I had to include the header as part of the job to print correctly.  I also had to turn off the Control-D printing in my win.ini file.  This was done by adding the following line in win.ini:
		ctrld=off

The file printed perfectly.

I'm very pleased with the new version of Windows -- it finally allows my machine (an old 16 mhz 386) to properly multitask several dos sessions.  I think this has something to do with the new method of setting up the permanent swap file -- something 3.0 couldn't do on my machine (for some unknown reason).  Overall, I've been very impressed with the speed enhancements and other minor fixes.  

Now, if only the new versions of himem.sys would function properly with my machine......


			David

-- 
------------------------------------------------------------------------
David Ehrlich		|  						|
Box C-0888		| 		No Comment   			|
Bucknell University	|  						|
Lewisburg, PA  17837	|   Bleary eyes inhibit creative minds.     	|
717-523-4294		|  						|
------------------------------------------------------------------------
From: dmd2@ra.msstate.edu (David Dumas)
Newsgroups: comp.windows.ms
Subject: HELP!--How do you delete files in AMI PRO 2.0?
Date: 7 Apr 92 23:47:58 GMT
Article-I.D.: ra.1992Apr7.234758.25726
Organization: Mississippi State University

How in the world do you delete file names in AMI PRO?  I have gone in and
deleted the files with the File Management option from the DOCS directory, but
I can't get rid of the file names of the files that I have created and saved
from the File Menu.  They are listed at the bottom of the menu after the Exit
command.  How do you get rid of these?

The files no longer exist because I can click on these names and nothing comes
up.  They are just names.

Has anyone had this problem?

Thanks,

David Dumas
dmd2@isis.msstate.edu


-- 
David Dumas
dmd2@Isis.MsState.Edu
From: jblanda@cbnewsg.cb.att.com (joseph.blanda)
Newsgroups: comp.windows.ms
Subject: IS SUPERPRINT 2.2 THAT GOOD?
Date: 9 Apr 92 19:59:46 GMT
Distribution: na
Organization: AT&T

Has anyone had any experience running Beta copies of SuperPrint 2.2
(assuming Zenographics distributed Beta releases) under Win 3.1?  If
so how does the performance fare against TrueType w/Win 3.1 and ATM
w/Win 3.1.  

I have used earlier releases of SuperPrint w/Win 3.0 and can vouch that
the queuing and font scaling is extremely fast.  However, SuperPrint
tends to be flakey when dealing with multiple font types and graphics
processing.

Any performance info on SuperPrint or other font management software
would be appreciated.

Thanx,
Joe
Newsgroups: comp.windows.ms
From: dan@ni.umd.edu (Dan Burns)
Subject: Gateway 2000 Upgrades
Organization: University of Maryland, College Park
Date: Thu, 9 Apr 1992 23:02:52 GMT


I called Gateway 2000 today and ordered my WINDOWS 3.1 upgrade.  They told
me it is in stock, since Monday, but they are two to three weeks behind in
upgrade orders.  BTW, the price, including shipping is $40.00 without the
extra fonts, or seventy-something with the font pack.

They are still working with IBM on the possiblility of selling OS/2 upgrades
according to the salesperson I spoke with.
From: pgleason@ncratl.AtlantaGA.NCR.COM (Pat Gleason)
Newsgroups: comp.windows.ms
Subject: Re: Trident New Drivers?
Date: 15 Apr 92 12:59:10 GMT
Distribution: comp
Organization: NCR Engineering and Manufacturing Atlanta -- Atlanta, GA

<12297@tamsun.tamu.edu> <12310@tamsun.tamu.edu>

>>>But recently I switched to Win 3.1 and I can't use my 256 color drivers
>>>anymore.  Do I need a new driver from Trident?  I tried calling Trident
BBS.

The April 26 Pc magazine states that you can use Win 3.0 OEM Driver disks
in Win 3.1 by renaming all files on the disk named SETUP.INF to OEMSETUP.INF.
Newsgroups: comp.windows.ms,bit.listserv.win3-l
From: bwong@beach.csulb.edu (Bradley Wong)
Subject: HELP! Win 3.1 dies in setup mode
Summary: What's the problem with "standard mode?"
Organization: Cal State Long Beach
Date: Tue, 7 Apr 1992 05:21:29 GMT

I can NOT get past the 93% second diskette setup mode where win 3.1
goes from DOS setup to windows setup. 

All I get is:

   Standard Mode: Fault in MS-DOS extender
   EC=0000 CS=0053 IP=232F ...

Naturally, there's not enough 3.1 to run in real or enchanced mode.

I've tried going from no config.sys or autoexec.bat files to my normal
ones w/o success in standard mode. I've tried both the original himem.sys
and emm386 programs and the "updated" ones posted to many BBSs.

This is on a Microgeneration 486-33 ETEQ-motherboard w/Mr. Bio and 
16Mb ram (and currently Windows 3.0a with MPC extentions).

I went back and un-tarred my 3.0 backup and noticed that 3.0 gives me
a standard mode abort message of:

   Protected-mode violation;
   try running in real mode.

This, again with both max and minimum config.sys and autoexec.bat files.

So, I reloaded DOS 5.0 from the distribution disks and reloaded the
original 3.0 diskettes, and still get the protected mode violations.

Last time I can remember having run in standard mode OK was with DOS 3.1.

Help!  Any body got a hint? MS's help line is BUSY, BUSY, BUSY!
From: rh0i+@andrew.cmu.edu (Richard Warren Harris)
Newsgroups: comp.windows.ms
Subject: Win 3.1 and Adlib
Date: 9 Apr 92 21:01:27 GMT
Organization: Senior, Social & Decision Sciences, Carnegie Mellon, Pittsburgh, PA

Hi,

Has anyone successfully installed msadlib.drv?  If so, how?  I'm in
touch with numerous poeple who can't get it to work, myself included.

The Drivers program copies it off the disk and into the system
directory, but it doesn't actually configure the system to use it.
Putting 'sound.drv = msadlib.drv' in SYSTEM.INI makes windows very,
very angry.

What is to be done?!  Who is to blame?!  (Well, actually I have a pretty
good idea on that second question :-)

Thanks,
- Rick

-------------------------------------------------------------------------------
Rick Harris 		| 	Information & Decision Systems/Computer Science
Senior.  Finally.	|	Social & Decision Sciences Department
rh0i+@andrew.cmu.edu	|	Carnegie Mellon (so hire me)
------------------------------------------------------------------------------

	"I not only want a car that is built in accordance with the basic 
	principles of physics and in light of an empirically verified, 
	well-winnowed tradition of automobile design, but I also want it 
	screwed together right."

		- Edward W. Constant II, "The Social Locus of Technological 
		      Practice:  Community, System, or Organization?"
From: saf@netcom.com (Steve A. Feinstein)
Newsgroups: comp.windows.ms
Subject: Re: SoundBlaster Pro Drivers for Win 3.1
Date: 15 Apr 92 06:34:43 GMT
Article-I.D.: netcom.9syj5w+.saf
Organization: Netcom - Online Communication Services  (408 241-9760 guest)

In article <BMpA02.MGA@world.std.com> gunther@world.std.com (Gunther W Anderson) writes:
>In regards to posting the drivers files to some archive site, the readme's
>in the package specifically prohibit this.  Normally, I would ignore such
>legalisms, but since Creative Labs are such neat people, I feel compelled
>to honor their request.  Just keep being persistent at their BBS number or
>Tech Support number, and you'll get through.  I did, and I'm no one special.
>
>By the by, they will send you the drivers for something like $7 to cover
>shipping, media, and bribing government officials.
>
>Gunther

I too saw that message, so I spent the entire evening redialing the
BBS.  If it's any consolation a buletin on the system said that they
were going to upgrade their BBS with more lines.  As it is now I was
unable to get in 'till ~4:00 in the morning, and then I could only
connect at 1200bps (no error correction).  but I got the driver and it
was worth the trouble.
-- 
Steve A. Feinstein   | saf@netcom.com | Will whomever stole my real .signature
360 Cowper St #9     | (415) 326-8224 | please return it?  No questions asked!
Palo Alto, CA  94301 |
From: hahm@iscsvax.uni.edu (Ronald Hahm)
Newsgroups: comp.windows.ms
Subject: Where is CICA?
Date: 12 Apr 92 04:43:07 GMT
Article-I.D.: iscsvax.1992Apr12.094307.3755
Organization: University of Northern Iowa

Does anyone have any idea when CICA is supposed to be back on-line?

-- 
+-------------------------------------------------------------------------+
|Ronald Hahm               INTERNET ADDRESS:  HAHM@ISCSVAX.UNI.EDU        |
+-------------------------------------------------------------------------+
From: ulisses@ldgo.columbia.edu (ulisses mello)
Newsgroups: comp.windows.ms
Subject: Best win3.1 upgrade strategy with NDW
Keywords: win3.1 & NDW
Date: 10 Apr 92 17:23:35 GMT
Organization: Lamont-Doherty Geological Observatory


   
	Based on the recent posts and on the PC magazine Win3.1 Tips the
best strategy to upgrade the win3.1 is to install it from the scratch in
a new directory and to keep the groups intact the program.ini should be
edited (to change or add the *.grp files). It seems that the new file
manager is still no replacement for the NDW, so I am gonna stick with NDW.
However, I want a painless upgrade (like everyone else). What would be
the best upgrade strategy to keep the groups intact, use NDW as file manager
and program manager and install win3.1 from the scratch ? I wouldn't like
to spend hours reconfiguring everything again.


	Any hint will be appreciated.

ulisses.
---------
ulisses@lamont.ldgo.columbia.edu
From: nuspljj@mentor.cc.purdue.edu (Joseph J. Nuspl Jr.)
Newsgroups: comp.windows.ms
Subject: Word for Windows is the greatest. (Not at Microsoft)
Date: 7 Apr 92 04:25:54 GMT
Organization: Purdue University



Microsoft says that Word for Windows is the greatest thing since Windows.
"With W4W, there is no need for a desktop publishing program."

Yet, 

--Taken from the press release from Microsoft--

%!PS-Adobe-3.0
%%Creator: Windows PSCRIPT
%%Title: PageMaker 4.0 - NTWIN32.PM4
%%BoundingBox: 14 9 597 784
%%DocumentNeededResources: (atend)
%%DocumentSuppliedResources: (atend)
%%Pages: (atend)
%%BeginResource: procset Win33Dict 3 1
/Win33Dict 290 dict def Win33Dict begin/bd{bind def}bind def/in{72
mul}bd/ed{exch def}bd/ld{load def}bd/tr/translate ld/gs/gsave ld/gr/grestore


Interesting.


Joseph J. Nuspl Jr.
nuspljj@mentor.cc.purdue.edu
From: din@grad1.cis.upenn.edu (Clarence Din)
Newsgroups: comp.windows.ms
Subject: Problem with Win3.1 and Postscript
Date: 10 Apr 92 14:59:19 GMT
Organization: University of Pennsylvania

My Ami Pro docs printed fine under Win 3.0 using a Kyocera Postscript
printer.  Now the standard Times Roman PS I use ends up looking like
a squashed Courier on paper.  Onscreen, the text looks fine.  I have
ATM 2.0 installed as well.  Is there a conflict between TrueType and
ATM???  Also, when I switch to regular Times Roman and print my text,
nothing appears on paper!  Why??!!
---------------------------------------------------------------------------
Clarence K. Din                                                   "scholar"
Programmer Analyst II, Language Analysis Center, University of Pennsylvania
"Flame me, not my employer.  My opinions are my own!"
din@grad1.cis.upenn.edu
Newsgroups: comp.windows.ms