Ultrasound Daily Digest     Sun Jun 13 00:37     Volume 4: Issue  13  

Today's Topics:
							About censors.
		   Hey Advanced GRAVIS, What about US CANADIANS!!!
							   PP2 plus
				 Prince of Persia 2 with the new Sbos
					  ULTRASOUND DAILY DIGEST V
			   Ultrasound Daily Digest V4 #11 (2 msgs)
			   Ultrasound Daily Digest V4 #12 (3 msgs)
								X-Wing

Standard Info:
	- Meta-info about the GUS can be found at the end of the Digest.
	- Before you ask a question, please READ THE FAQ.

----------------------------------------------------------------------

Date: Sat, 12 Jun 1993 10:40:28 +0501 (EDT)
From: Gunnar Swanson <gunnar@gibbs.oit.unc.edu>
Subject: About censors.
Message-ID: <Pine.3.05.9306121028.A19056-a100000@gibbs.oit.unc.edu>

To the gentleman who wrote in about a censor.  I do not think the Gravis
Digest has ever been censored I have seen stuff on here about other cards
and etc none of it seemed clipped.  It was probably just lost in the ether
as some times happens.  

Speaking of ether I have downloaded stuff from the epas and other places
in what I thought was a perfect download.  Only when I got home to
discovered that it was flawed.  This sort of thing happens and falls under
the rubric of "Shit just happens!".  So folks just be aware of this when
downloading stuff.



Gunnar Swanson

gunnar@gibbs.oit.unc.edu

end.

------------------------------

Date: Sat, 12 Jun 1993 09:07:31 -0230 (NDT)
From: Ed Reddy <ereddy@morgan.ucs.mun.ca>
Subject: Hey Advanced GRAVIS, What about US CANADIANS!!!
Message-ID: <Pine.3.05.9306120931.B3690-9100000@morgan.ucs.mun.ca>

I have yet to see any owners where I live receive their new GUS disk,
while Joe Blow in Siberia received his 2 weeks ago.
 
It's nice to know who Gravis is serving. Great to see them playing
Diplomatic pleasing. Do everything to please foreign customers, while your
local and fellow Canadians can wait... NOT!
 
Get off your butt Gravis and mail us those disks!

Any other Canadians feel the same way?

------------------------------

Date: Sat, 12 Jun 93 13:54:21 EDT
From: thduda@mosaic.uncc.edu (Tony H Duda)
Subject: PP2 plus
Message-ID: <9306121754.AA02894@mosaic.uncc.edu>

I forgot to mention in the message I just wrote, I have tried the game with emm386.exe or without the emm386.exe.  They came with the same result.

------------------------------

Date: Sat, 12 Jun 93 13:51:50 EDT
From: thduda@mosaic.uncc.edu (Tony H Duda)
Subject: Prince of Persia 2 with the new Sbos
Message-ID: <9306121751.AA02838@mosaic.uncc.edu>

It seems that the game hangs up after 3 minutes, maybe little bit longer after few digital sounds play.  I am using the new sbos download from EPAS, gus0032.zipAny body Any Ideas?  Help!

------------------------------

Date: Fri, 11 Jun 93 11:38:44 
From: john.smith@gravis.com
Subject: ULTRASOUND DAILY DIGEST V
Message-ID: <9306111138.A1212wk@gravis.com>

 -----------------------------

Date: Thu, 10 Jun 1993 14:06:39 -0700 (PDT)
From: jde@ciaran.ucr.edu (Jeff Ellis)
Subject: epas v2.06L not working
Message-ID: <9306102106.AA15701@ciaran>

>From: mike@batpad.org (mike batchelor)
>I got the 6 disks from epas, though, and can't get it installed.  It
>won't recognize disk #2 - it asks me over and over again for it.  Disk
>2 contains ultrasnd.002 and disk.id, a plain text file that claims
>that this is disk #2.  What's wrong?

>I also have seen this problem.  I thought it might have been the way I
>moved them from the Sun to the 3.5" disks to try at home. >I got them
>again today and used diffrent methods to put them on the disks. >Maybe
>it will work now, if the epas archive is not bad.

Some people seem to be having problems installing the UltraSound V2.06L
disks.  Here are some possible fixes.

1) When you unzip the 6 disks (GUS0025.ZIP thru GUS0030.ZIP) onto floppy
   disks, make sure your floppy do NOT have a disk label OR are labeled
   ULTRASND_1, ULTRASND_2, ULTRASND_3, ULTRASND_4, ULTRASND_5 and
   ULTRASND_6.

2) You will notice a file on each disk called DISK.ID. Here are the
   contents of each of the 6 DISK.ID files (one/disk).

UltraSound
2.06L
UltraSound Software Disk 1

UltraSound
2.06L
UltraSound Software Disk 2

UltraSound
2.06L
UltraSound Software Disk 3

UltraSound
2.06L
UltraSound Software Disk 4

UltraSound
2.06L
UltraSound Software Disk 5

UltraSound
2.06L
UltraSound Software Disk 6


If you have any more problems with the install feel free to leave
me mail.

 -----------------------------
 -----------------------------

Date: Thu, 10 Jun 93 10:12:22 BST
From: "James Andrews, User Support" <james@sol1.east-london.ac.uk>
Subject: Re: Gus upgrade disks
Message-ID: <29686.9306100912@uk.ac.uel.sol1>

>The other day I got version 2.06 disks direct from gravis- which seemed
>to have a manual that had chapters on powerchords and midisoft studio,
>but no powerchords/midisoft disk with it on. I might be wrong about the
>2.06 disks not containing the long awaited sequencer software, as I
>havent bothered to install it yet.

MidiSoft and Power Chords are built INTO the 2.06 disks.

 -----------------------------

Date: Thu, 10 Jun 93 20:19:44 +0300
From: Shmuel Gazit <keeper@ccsg.tau.ac.il>
Subject: New disks & Probs
Message-ID: <9306101719.AA12961@ccsg.tau.ac.il>

>Well, to add to the reports the float in - I got mine yesterday !
>Nice to know Israel is on Gravis' map  - great to hear from u guys !!

Heard from Isreal and Japan in the same day.  Now if people on the West
Coast of Canada could only get their upgrades I'd be happy <grin>
 -----------------------------

Date: Fri, 11 Jun 1993 14:48:55 +0930 (CST)
From: SCARMAN@hfrd.dsto.gov.au (Gavin)
Subject: Patch Creating
Message-ID: <930611144855.5ba9@hfrd.dsto.gov.au>

>And one for Gravis: have you considered multiple patch configuration
>files? I mean having only one is a bit limiting, esp. with patchman.

Already in the works

 -----------------------------

Date: Thu, 10 Jun 1993 10:06:04 -0500
From: ken@austin.ibm.com (Ken Goach IBM)
Subject: tremstr patch problem SOLVED
Message-ID: <9306101506.AA21757@daedalus.austin.ibm.com>

>The problem is there's a patch missing - or the DEFAULT.CFG is
>wrong. The new DEFAULT.CFG identifies patch 45 as tremstr. There's
>no such patch. In previous versions of the DEFAULT.CFG file, the
>following was done:

Yep. We removed TREMSTR and I forgot to change DEFAULT.CFG.  It has been
fixed.  So the next time I build a set of disks it'll be in there.

 -----------------------------

That is it for now from Gravis HQ.

C'ya and have a good weekend. Time to go see the new Jeresic (sp) Park
<g>)

John
---
 ~ QMPro 1.02 05-8925 ~ /l{TTh7$ C~hanks for hanging up, dear.

------------------------------

Date: Sat, 12 Jun 93 07:44:45 PDT
From: mike@batpad.org (mike batchelor)
Subject: Re: Ultrasound Daily Digest V4 #11
Message-ID: <mike01626930512074445@batpad.org>

> From: jde@ciaran.ucr.edu (Jeff Ellis)
> Subject: epas v2.06L not working
> 
> >From: mike@batpad.org (mike batchelor)
> >I got the 6 disks from epas, though, and can't get it installed.  It
> >won't recognize disk #2 - it asks me over and over again for it.  Disk
> >2 contains ultrasnd.002 and disk.id, a plain text file that claims
> >that this is disk #2.  What's wrong?
> 
> I also have seen this problem.  I thought it might have been the way I moved
> them from the Sun to the 3.5" disks to try at home.
> I got them again today and used diffrent methods to put them on the disks.
> Maybe it will work now, if the epas archive is not bad.

Thanks to the several people who wrote back telling me to remove the
volume label from the diskettes I copied the epas ZIPs to.  That did
the trick, 2.06L installed without much trouble.  During Windows
installation, I did get a sharing violation when Install tried to
remove the old driver, but I took care of that afterwards, and also
edited the old entry out of system.ini.

Suggestions:
Install should inform the user that it will be starting Windows.  I
usually boot up with VIDRAMEMS on my QEMM device, and Windows will not
go into 386enh with that parameter active.  I remembered this about
half-way through copying the patches, and had to abort and start over
to avoid Windows' error about "Device conflict" in the video area.

Check for share, tell the user to uninstall it.



				   ///////////////////////////////
					//// Mike Batchelor ///////////
					 //// mike@batpad.org //////////
					  //// Mar Vista, California ////
					   ///////////////////////////////

------------------------------

Date: Sat, 12 Jun 93 08:03:52 PDT
From: mike@batpad.org (mike batchelor)
Subject: Re: Ultrasound Daily Digest V4 #11
Message-ID: <mike01626930512080352@batpad.org>

> From: ken@austin.ibm.com (Ken Goach IBM)
> Subject: Need advice on new motherboard
> 
> Hey GUS people,
> 
> Well, as some of you have read, I'm still having some weird things
> happen with MIDI on my GUS. So I'm considering getting a new
> motherboard to try and remedy the problem.
> 
> First off, let me tell you what I have. I have a Packard Bell Legend
> 300 SX. It's a 386, 25 mhz machine with 4 meg RAM (two soldered on
> the motherboard, two that I added). It's a smaller motherboard (the
> case is smaller). It has a riser with three expansion slots (all are
> 16-bit, I believe).
> 
> So, that's what I want to replace.

Not easy.  Since it uses a "riser" as you call it, for three slots
that sit horizontally, you are going to have a hard time finding a
board that has a riser in the same physical location relative to the
opening on the case, for the backplanes of your expansion cards to show
through.  These risers plug into (usually) proprietary slots on the
motherboard - there's no standard for how they are constructed.

> Second, what all is involved in doing this? How hard is it? Do I just
> buy the motherboard, put it in, and bingo, it works? Do I move my
> 386 CPU over to the new board? What other things need to be moved?
> Does this affect the BIOS? etc. etc. etc.

Assuming you find a board that fits your case, you can exchange CPUs
without trouble.  Just make sure you get a CPU puller from your dealer
- they are not more than $10.  The new board will come with a new BIOS
that is appropriate for the chipset it uses.  You would only have to
exchange the CPU and your expansion cards, hard drives, etc.  You may
also find that the power supply and LED leads to the motherboard won't
reach, but that can be fixed by splicing in new lengths of wire.
Hopefully, the connectors on your Packard Bell power supply are of the
standard type.

> Is there a detailed explanation of how to do this anywhere?

Walden Books and the rest of the mall bookstore chains have lots of
books on PCs, I know I have seen several on PC hardware maintenance.
One of them will tell you what you need to know.

> Lastly, if anyone is running a GUS successfully in a Packard Bell
> Legend 300SX, please email me. Maybe there's a workaround I haven't
> tried yet.

Start from the bottom and work your way up:  Make a test boot floppy
that has only himem.sys, dos=high, files=30, buffers=20 and
ultrinit.sys, of course.  If you have disk compression software like
Stacker, you can load it, too.  The test autoexec.bat should have only the
path and prompt in it, and the set statements for the GUS.  Boot up
this simple configuration, and start Windows, holding down the SHIFT
key as soon as you see the Windows logo (this will prevent your
startup group from running).  Does it work?  If so, you can build on
this configuration, adding back device drivers and TSRs one at a time
until it fails again - if we know what device causes the conflict,
perhaps a workaround can be figured out.  The Packard Bells are pretty
standard except for the case and motherboard layout - they use VLSI
chipset and Phoenix BIOS; shouldn't be a compatibility problem with
anything, just a drag to upgrade the motherboard. :)

I assume that the GUS Install program says your GUS settings are OK
and free of conflicts?



				   ///////////////////////////////
					//// Mike Batchelor ///////////
					 //// mike@batpad.org //////////
					  //// Mar Vista, California ////
					   ///////////////////////////////

------------------------------

Date: Sat, 12 Jun 93 2:44:38 CDT
From: ddebry@itchy (Dave DeBry)
Subject: Re: Ultrasound Daily Digest V4 #12
Message-ID: <9306120844.AA08544@itchy>

	Replies, replies, replies...


> From: "Timmy (Y.T.) Chan" <timchan@bnr.ca>
> Subject: Are GUS mail edited?? 
> 
> I sent an e-mail to this users group on June 10 and it showed up
> with the latter half of my mail taken out on June 11.  Is this
> by intent (purposely edited out)
> or by accident (half my message got lost during the transfer).

	No, I don't edit anything.  Occasionally, if I get bored, I'll
read the postings for the upcoming digest (before any of you do! bwa
ha ha!), but I never edit them.  (Unless someone mails me specifically
to remove one of their own posts before it gets mailed out.)

	There are a couple of things that would make your message get
eaten, and they have to do with standard mail protocol:

	1] If the first thing on ANY line is "From " (no colon, case
sensitive), then mail transfer daemons and the digestifier will think
this is the start of a new message.  So be careful.

	2] If the first thing on a line is a ".", that will signal the
mail daemons to end your mail, and it will be truncated right there.
So be careful again.

> From: john.smith@gravis.com
> Subject: PP2 AND GUS0032
>
> Seems I was mistaken about PP2.  THe problems weren't do to the -O1
> switch but to EMM386.  Haven't tried it with other memory managers,
> but if you don't remove EMM386 the game will hang as soon as you get
> to the quick sand (just past the ship).  You still need the -O1
> switch.  I've updated GUS0032.ZIP today (06/10/93) to include the -O1
> in SBOS.CFG and also made a note in the README file about PP2.

	Will this fix the problems I'm having with Populous II?  I
can't get it to work with the GUS/SBOS at all.

	In fact, running SBOS will often result in the following
message: 

] I/O card parity interrupt at xxxx:xxxx.
] Type (S)hut of NMI, (R)eboot, other keys to continue.

	Sometimes it won't wait for a key, and then disable NMI by
itself (what is NMI anyway?).  Sometimes it will just completely lock
up my system; even ctrl-alt-del won't work.  (And some idiot at
Packard Bell designed my box without a reset button.  I *HATE* that.
I guess I have a project for the weekend. :)

	And if I get that message, SBOS refuses to free itself from memory.

	Real annoying.

	I am using emm386 (populous 2 requires a lot of ems), 4dos,
sbos 2.08, smartdrv, and so on.  386sx (packard bell should be shot
for leaving off that reset button... I'm not bitter), 8 meg ram...

	Any info here, anyone?

> From: Bill Norton <wbn@merit.edu>
> Subject: Re: Ultrasound Daily Digest V4 #11 
> 
> I tried to unzip wcharts.zip from the archives today and failed.  Has
> this happened to anyone else:

	Get a newer version of unzip.  Preferably the Info-ZIP
version.  Look on oak.oakland.edu.

-- 
Dave  ddebry@ debry@   \ 
DeBry dsd.    peruvian. | "Do you think it's easy doing nothing all day?"
	  es.     cs.utah.  |
	  com     edu      /  

------------------------------

Date: Sat, 12 Jun 93 08:48:23 PDT
From: mike@batpad.org (mike batchelor)
Subject: Re: Ultrasound Daily Digest V4 #12
Message-ID: <mike01626930512084823@batpad.org>

> From: john.smith@gravis.com
> Subject: PP2 AND GUS0032
> 
> Seems I was mistaken about PP2.  THe problems weren't do to the -O1 switch but
> to EMM386.  Haven't tried it with other memory managers, but if you don't
> remove EMM386 the game will hang as soon as you get to the quick sand (just
> past the ship).  You still need the -O1 switch.  I've updated GUS0032.ZIP today
> (06/10/93) to include the -O1 in SBOS.CFG and also made a note in the README
> file about PP2.

At Quarterdeck, we have found some problems with EMM386's DMA
buffering.  The default should be D=16, I believe, but increasing it
may not always help.  Seems that EMM386 will often locate its DMA
buffer in a place that a SCSI host, like Adaptec 1542x, would step on.
If you don't want to get a different memory manager, you can try
different versions of EMM386 (DOS 5, Win31, DOS 6).  QEMM and 386MAX
do not have this problem.  You may also be able to work around it by
loading ASPI4DOS.SYS low with the /W switch, but this will eat 64K of
conventional memory.

No problem here with POP2 and QEMM 6 or 7.  I use -O1 as well.


				   ///////////////////////////////
					//// Mike Batchelor ///////////
					 //// mike@batpad.org //////////
					  //// Mar Vista, California ////
					   ///////////////////////////////

------------------------------

Date: Sat, 12 Jun 93 19:36:05 EDT
From: n4zfd!frodo@rylos.n2idf.ampr.org (Jim Blakely)
Subject: Re: Ultrasound Daily Digest V4 #12
Message-ID: <u3225B1w165w@n4zfd.UUCP>

Re: Flight Simulator 4

FS4's native sound is to the PC speaker only. Are you trying to use
the Sound, Graphics, Airplanes upgrade package?

I was able to get FS4 with SGA to work with the 2.06L SBOS by setting
SGA's sound control panel for Adlib with Soundblaster digitized
sounds. I used -x2 for SBOS.

------------------------------

Date: Sat, 12 Jun 93 15:45:21 WET DST
From: Steve <gei055@rowan.coventry.ac.uk>
Subject: X-Wing
Message-ID: <4276.9306121445@rowan.coventry.ac.uk>

I've just installed x-wing by LucasArts onto my PC (all 14 megs of it).  I'm
having problems trying to get the sound to work properly.  It seems to be
playing at strange speeds, some parts sound O.K. but others don't.  Also the
digitised speech plays sometimes but not others.  Has anyone with experience of
this game come across any similar problems or know of a cure? 

I've running it on a 486DX-33, SBOS v2.06 (i.e. the latest update) from a
stacked drive (if this makes a difference).

Cheers

Steve

------------------------------

End of Ultrasound Daily Digest V4 #13
*************************************
