🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: alt.games.diablo
Article #1510

Re: What the new patch to DIABLO will fix (list)

#1510
From: oul... Sworn Defender
Date: Thu, 27 Feb 1997 00:00
277 lines
9862 bytes
Great job BLIZZARD!!!!!!!!!!!!!!!!!!!!!!!!!


On Wed, 26 Feb 1997 11:24:59 -0700, Gordon K Wilson
<gkwi...@ix.netcom.com> wrote:

>--------------------------------------------------------------------
>                        PATCH 1.02 -- 02/25/97
>--------------------------------------------------------------------
>
>This file contains information about the fixes contained in the patch
>that upgrades Diablo to version 1.02.  Additionally, this file contains
>updated troubleshooting tips.
>
>--------------------------------------------------------------------
>                              Contents
>--------------------------------------------------------------------
> I. FIXES	=
>
>
> II. TROUBLESHOOTING
>
>    1. Video
> =
>
>    2. Sound    =
>
>
>    3. Multiplayer
>
>    4. General Tips
>
>----------------------------------------------------------------------
>I.                               FIXES
>----------------------------------------------------------------------
>   1. Corrects the NULL cell buffer errors and other draw problems
>
>   2. Fixes intermittent crash in Join Game screen
>
>   3. Fixes data corruption problem which could cause a player to
>      get locked out of Battle.net when creating a new channel
>
>   4. Improves error handling for dropped network packets
>
>   5. Provides more descriptive messages when unable to join a game
>
>   6. Fixes the problem with some equipped items not being seen =
>
>      by other players in multiplayer games
>
>   7. Prevents Lazarus's red portal from disappearing after =
>
>      leaving his lair
>
>   8. Fixes the Level Advance Indicator remaining on screen after
>      character attributes are maxed =
>
>
>   9. Fixes inaccurate display of game creation time
>
>  10. Games shown in the list of public games on Battle.net will
>      not disappear anymore.  The list will be refreshed only if the
>      user closes and reopens the Join Game dialog.
>
>  11. Fixes problem with soundcards that do not support the Set
>      Format command (i.e. ESS1888)
>	=
>
>  12. Fixes problems writing to system registry
>
>  13. Numerous fixes to item integrity
>      NOTE: With this patch, when the game detects duplicate items they
>            will be removed from the game.
>
>  14. Improves error correction related to line noise in modem games
>
>----------------------------------------------------------------------
>II.                         TROUBLESHOOTING
>----------------------------------------------------------------------
>  1. VIDEO
>
>	NOTE:  The first step that should be taken in isolating video
>	problems is ensuring that you have the most current drivers from
>	your video card manufacturer.
>
>	A. Problems with cut scenes:
>	If video playback is slow or choppy on your system, you can =
>
>	adjust the size of the playback window using the VidSize utility,
>	which is installed in the Diablo directory.  (Large or Small, =
>
>	Default is large)
>
>	B. Video problems:
>	If you have problems when exiting out of Diablo, or with video =
>
>	after getting into Diablo (i.e. it is freezing up, or it is doing
>	something strange with the video) set the video display properties
>	to 640x480x256 before playing Diablo.  DirectX has a problem with
>	certain video cards, and it is causing this to occur.
>
>	C. S3 Video Drivers:
>	"http://www.s3.com"
>
>	D. CHIPS & TECHNOLOGIES video Drivers:
>	"http://www.chips.com"
>
>	E. Matrox Video Drivers:
>	"http://www.matrox.com"
>
>	F. Matrox Millennium:
>	Video doesn't display properly =
>
>	(rolling screen images, overlapping screen images or a blank screen) =
>
>	1)Right-click on the Windows 95 desktop background.
>	2)Click on the Properties menu item - MGA Monitor tab - MGA Monitor =
>
>	option button.
>	3)From the MGA monitor list, select the monitor model you're using. =
>
>	If your monitor model does not appear in the list, select monitor =
>
>	that runs at 60 Hz at 640 =D7 480 (for example, Standard Monitor Types
>	 - Vesa 1024X768 @60Hz). For more information on MGA monitor =
>
>	selection, see the on-line documentation for MGA PowerDesk.
>	4)Click OK to confirm your selection
>
>	G. ATI 3DExpression PCI Mach64
>	Problem: After installing Dx3.0a from the Diablo CD & rebooting the
>	computer, you get a black screen with green lines.
>	Fix: =
>
>	1.) Boot into safe mode by: Rebooting the computer, pushing F8 when
>	you see the words starting Win95, select safe mode.
>	2.) Click on start -> settings -> Control Panel -> Display =
>
>	-> Settings -> Change Display Type -> Click on "Change..." under =
>
>	Adapter Type -> show all devices -> Manufactures: Standard Display
>	Types.  Models: Standard Display Adapter (VGA) then click OK =
>
>	-> close -> Apply & Close then Yes to Restarting the computer.  =
>
>	(let the computer boot normally)
>	3.) Click on start -> settings -> Control Panel -> Display -> Settings
>	-> Change Display Type -> Click on "Change..." under Adapter Type =
>
>	-> Have Disk -> Browse to "X:\win95drv\display\atigt\macxw4.inf" =
>
>	(X=3Dcdrom drive) & click on OK twice -> Select ATI 3DExpression PCI =
>
>	mach64 (Direct Draw) & click on OK -> Close -> Apply & Close then =
>
>	Yes to reboot the computer, this should fix the problem.
>
>	H. Alliance Promotion:
>	Download the DirectX 2 at: "http://www.blizzard.com/support/d-directx.ht=
>m"
>	Download the DirectX 2 compatible driver for the alliance promotion vide=
>o
>	card at: "http://www.alsc.com"
>	NOTE: These drivers are also available from the Alliance BBS at (408)383=
>-4994
>	If you have the DirectX 3 drivers installed and the manufacturer's Direc=
>tX 2 =
>
>	driver, you might see two hands.
>
>	I. Virge Video Drivers:
>	If a Direct X application asks to overwrite the preinstalled drivers, =
>
>	answer NO.  Currently, there is not a diskette release of the Virge grap=
>hics
>	drivers/Direct X drivers, so if you overwrite the Virge drivers with a =
>
>	Direct X application, you will have to run the QuickRestore utility to g=
>et
>	the preinstalled drivers back.
>
>  2. SOUND
>
>	NOTE:  The first step that should be taken in isolating sound
>	problems is ensuring that you have the most current drivers from
>	your sound card manufacturer.
>
>	A. SB Sound Cards:
>	"www.creaf.com"
>	As of 2/13/97 the latest version is "4.35.00.0018"
>
>	B. Fatal exception ** has occurred at: (with SB 16/32/64)
>	The problem was linked to a old version of the sound driver.  If you do =
>not
>	have at least version "4.35.00.0018" dated 2/13/97 then download it at:
>	"http://www.creaf.com/wwwnew/tech/faqs/drv0001.html"
>
>  3. MULTIPLAYER
>
>	A. Trying to get onto Battle.net:
>	1.) If you are using a third party TCP/IP implementation, try installing=
>
>	Microsoft's TCP/IP protocol (use Add/Remove Programs in the Control Pane=
>l)
>	2.) Use the Telnet program to test your connection to Battle.net.  From =
>a
>	command prompt, type:
>		telnet battle.net 116
>		telnet battle.net 118
>	If Telnet can't connect to Battle.net, contact your Internet provider or=
>
>	network administrator about opening up those ports.
>	3.) Delete the file "Bncache.dat" from the Diablo directory.  This file
>	contains cached data that has been downloaded from Battle.net.  Deleting=
> it
>	will remove any data that may have been corrupted during download.
>	4.) Verify that the Diablo directory is writeable, and that there is ple=
>nty
>	of free disk space on the drive that holds the Diablo directory.
>
>	B. Retail to Spawn:
>	1.) One player can create the game but the other can't see the game to j=
>oin.
>	Make sure ALL are playing spawn or ALL playing retail copies!
>	Spawn cannot play retail.
>
>	C. Can't see the other person on the network (IPX Games):
>	1.) Make sure that everyone is logged into the network.
>	2.) Make sure everyone is using the retail version.
>	3.) Make sure everyone has upgraded to the patched version.
>	(Version 1.02 cannot play against version 1.00)
>	4.) Make sure the IPX frame type is correct.
>	Click on start -> settings -> control panel -> network -> IPX/SPX -> pro=
>perties =
>
>	-> advanced -> frame type: Make sure all people playing have their frame=
> type =
>
>	set to the same value.  Then set the Max Sockets to 32 and the Max Conne=
>ctions =
>
>	to 16.  Click on OK and reboot the computer, then try to start the netwo=
>rk game.
>
>  4. GENERAL TIPS
>
>	A. Is there anything I can do to boost game performance?
>	To speed up game play on slower systems, turn off music by bringing up t=
>he
>	Diablo Options menu and setting the Music Volume all the way to the left=
>=2E =
>
>	Also, clearing up hard drive space can improve performance on systems wi=
>th =
>
>	low memory.
>
>
>THE FIRST TRANSPORT IS AWAY!	=
>
>
>++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>                                DIABLO
>
>   Copyright (c) 1996 BLIZZARD ENTERTAINMENT, All rights reserved
>
>   Diablo and Battle.net are trademarks and Blizzard Entertainment
>          is a trademark of Davidson and Associates, Inc.
>
>
>             For news and updates visit WWW.BLIZZARD.COM =
>
>
>++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
Technical Details
Message-ID: <3314e8e9.984227@news.nbnet.nb.ca>
Path: mbox-mo1.pugleaf.net!unknown!not-for-mail
References: <33147FFB.575A@ix.netcom.com>

Show Full Headers
Complete Article Headers
From: oul...@nbnet.nb.ca (Sworn Defender)
Subject: Re: What the new patch to DIABLO will fix (list)
Date: 1997/02/27
Message-ID: <3314e8e9.984227@news.nbnet.nb.ca>
X-Deja-AN: 221706669
References: <33147FFB.575A@ix.netcom.com>
Organization: NBNet.nb.ca
Newsgroups: comp.sys.ibm.pc.games.rpg,alt.games.diablo
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit