Anonymous edits have been disabled on the wiki. If you want to contribute please login or create an account.


Warning for game developers: PCGamingWiki staff members will only ever reach out to you using the official press@pcgamingwiki.com mail address.
Be aware of scammers claiming to be representatives or affiliates of PCGamingWiki who promise a PCGW page for a game key.

Difference between revisions of "The Elder Scrolls II: Daggerfall"

From PCGamingWiki, the wiki about fixing PC games
Line 10: Line 10:
 
== Patches ==
 
== Patches ==
 
===DAG213.EXE===
 
===DAG213.EXE===
Latest, greatest, and last patch. Copy into your Daggerfall directory and execute. This patch contains all previously released patches as well so this is all you need to update from any previous version.
+
Latest, greatest, and last patch. Copy into your Daggerfall directory and execute. This patch contains all previously released patches as well so this is all you need to update from any previous version.
 +
 
 +
===ADDQUEST.ZIP===
 +
The CompUSA Special Edition Patch. This patch adds 16 new quests and additional artifacts to the game. One may consider applying this patch should do so before applying DAG213.EXE.
 +
 
 +
 
 +
==Obsolete Patches==
 +
These patches are outdated and probably aren't much use to anyone.
  
 
===DAG200.EXE===
 
===DAG200.EXE===
Line 24: Line 31:
 
Old Patch v1.77. Copy to the DAGGERFALL directory and execute. You don't need this patch to upgrade to patch v1.79 or greater.
 
Old Patch v1.77. Copy to the DAGGERFALL directory and execute. You don't need this patch to upgrade to patch v1.79 or greater.
  
 +
===DAGDEMO.ZIP===
 +
This patch was used to make one of the few Daggerfall demos. This specific patch creates a demo that allows you to explore one of the game's dungeons.
 +
 +
===DFBETONY.ZIP===
 +
This patch was used to make one of the few Daggerfall demos. This spefic patch creates the much larger, and rarer, Daggerfall Betony demo which allows you to adventure briefly outdoors.
 +
 +
 +
'''*Props to http://www.uesp.net for archiving and documenting patches. Download them from http://www.uesp.net/wiki/Daggerfall:Files.'''
 +
 +
==Avoiding Corrupted Savegames==
 +
 +
The majority of corrupted savegames are caused by memory issues. Therefore, the best way to avoid such problems is by replacing the memory extender that comes with the original game with a more advanced one.
 +
 +
One such Memory Extender is DOS32A.
 +
 +
* To setup the program, read the documentation on the program's original web-page or the else read the article on the DOSBox wiki.
 +
* Use DOS32A whenever you run Daggerfall, preferably from the start of a new game. Players have reported that by doing so you can effectively prevent corrupted savegames from occurring.
 +
* This Memory Extender should also be used when running DOS programs other than Daggerfall, including other DOS games that use a memory extender such as the once-popular DOS4GW.
 +
 +
 +
==Workarounds for Corrupted Savegames==
 +
 +
There are some workarounds for corrupted savegames:
 +
 +
Use the DOS32A Memory Extender (discussed above).
 +
Very often an apparently corrupt savegame can be run again when using DOS32A. In this case, you will need to always run DOS32A to keep your savegames working.
 +
Delete all ATF and ATM files from the ARENA2 directory, as well as the BIO.DAT, MAPSAVE.SAV and the RUMOR.DAT files, also located in the ARENA2 directory.
 +
Run Daggerfall using DOS32A and load the savegame. If this doesn't work, see step 3
 +
If this step did work, you must do this procedure from now on whenever you start the game from DOS, but you only need to delete the ATF and ATM files.
 +
You can write a small shell program (BAT-file) which does this task for you and starts the game afterwards, for example:
 +
        @ECHO OFF
 +
        del ARENA2\*.AMF
 +
        del ARENA2\*.ATF
 +
        dos32a fall.exe z.cfg
 +
If you have tried step 2 and you couldn't load the savegame, run Daggerfall again using DOS32A, this time without deleting any files.
 +
If you used the workaround mentioned in step 2 for some time and you get corrupted savegames again, you must not delete the files listed in step 2 anymore. Just start the game using DOS32A and load the savegame as you would normally do.
  
'''*Props to http://www.uesp.net for archiving and document patches. Download them from http://www.uesp.net/dagger/files/dagfiles.shtml.'''
+
If none of these steps worked, the savegame is corrupted beyond any known workarounds. Use a savegame dated earlier than the corrupted one and use DOS32A from now on.
  
  
===Hacks/Tweaks===
+
==Hacks/Tweaks==
==Running without CD==
+
===Running without CD===
 
*Daggerfall can be run without the CD to improve game speed and prevent the annoyance of having to switch CDs when playing various games.
 
*Daggerfall can be run without the CD to improve game speed and prevent the annoyance of having to switch CDs when playing various games.
 
    
 
    
Line 40: Line 83:
 
   
 
   
  
Information retrived from: http://www.uesp.net/dagger/daghack.shtml#nocd
+
Information retrived from: http://www.uesp.net/wiki/Daggerfall:Running_without_Cd
  
  

Revision as of 19:46, 11 March 2012

DOSBox or other compatibility/visualization is required to run the game on modern OS'. The game has been released by Bethesda as a free download on http://www.elderscrolls.com/daggerfall/ Template:Infobox

Patches

DAG213.EXE

Latest, greatest, and last patch. Copy into your Daggerfall directory and execute. This patch contains all previously released patches as well so this is all you need to update from any previous version.

ADDQUEST.ZIP

The CompUSA Special Edition Patch. This patch adds 16 new quests and additional artifacts to the game. One may consider applying this patch should do so before applying DAG213.EXE.


Obsolete Patches

These patches are outdated and probably aren't much use to anyone.

DAG200.EXE

Old Patch v2.00. Copy to DAGGERFALL directory and execute. You don't need this patch to upgrade to patch v2.12 or greater.

DAG195.EXE

Old Patch v1.95. Copy to DAGGERFALL directory and execute. You don't need this patch to upgrade to patch v2.00 or greater.

DAG179.EXE

Old Patch v1.79. Copy to DAGGERFALL directory and execute. You don't need this patch to upgrade to patch v1.95 or greater.

DAG177.EXE

Old Patch v1.77. Copy to the DAGGERFALL directory and execute. You don't need this patch to upgrade to patch v1.79 or greater.

DAGDEMO.ZIP

This patch was used to make one of the few Daggerfall demos. This specific patch creates a demo that allows you to explore one of the game's dungeons.

DFBETONY.ZIP

This patch was used to make one of the few Daggerfall demos. This spefic patch creates the much larger, and rarer, Daggerfall Betony demo which allows you to adventure briefly outdoors.


*Props to http://www.uesp.net for archiving and documenting patches. Download them from http://www.uesp.net/wiki/Daggerfall:Files.

Avoiding Corrupted Savegames

The majority of corrupted savegames are caused by memory issues. Therefore, the best way to avoid such problems is by replacing the memory extender that comes with the original game with a more advanced one.

One such Memory Extender is DOS32A.

  • To setup the program, read the documentation on the program's original web-page or the else read the article on the DOSBox wiki.
  • Use DOS32A whenever you run Daggerfall, preferably from the start of a new game. Players have reported that by doing so you can effectively prevent corrupted savegames from occurring.
  • This Memory Extender should also be used when running DOS programs other than Daggerfall, including other DOS games that use a memory extender such as the once-popular DOS4GW.


Workarounds for Corrupted Savegames

There are some workarounds for corrupted savegames:

Use the DOS32A Memory Extender (discussed above). Very often an apparently corrupt savegame can be run again when using DOS32A. In this case, you will need to always run DOS32A to keep your savegames working. Delete all ATF and ATM files from the ARENA2 directory, as well as the BIO.DAT, MAPSAVE.SAV and the RUMOR.DAT files, also located in the ARENA2 directory. Run Daggerfall using DOS32A and load the savegame. If this doesn't work, see step 3 If this step did work, you must do this procedure from now on whenever you start the game from DOS, but you only need to delete the ATF and ATM files. You can write a small shell program (BAT-file) which does this task for you and starts the game afterwards, for example:

       @ECHO OFF
       del ARENA2\*.AMF
       del ARENA2\*.ATF
       dos32a fall.exe z.cfg

If you have tried step 2 and you couldn't load the savegame, run Daggerfall again using DOS32A, this time without deleting any files. If you used the workaround mentioned in step 2 for some time and you get corrupted savegames again, you must not delete the files listed in step 2 anymore. Just start the game using DOS32A and load the savegame as you would normally do.

If none of these steps worked, the savegame is corrupted beyond any known workarounds. Use a savegame dated earlier than the corrupted one and use DOS32A from now on.


Hacks/Tweaks

Running without CD

  • Daggerfall can be run without the CD to improve game speed and prevent the annoyance of having to switch CDs when playing various games.
  1. Install the game with the largest install size.
  2. Copy all the files from the DAGGER/ARENA2 directory on the CD to the ARENA2 directory on your hard drive where you installed the game. There are some large files which are not installed by the largest install size.
  3. Install the latest patch as desired.
  4. Edit the Z.CFG file in your Daggerfall directory. Change the PATHCD value to match that of the PATH value.
  5. To run the game don't use DAGGER.EXE as you would normally, but instead run the command FALL.EXE Z.CFG. You can create a batch file to prevent having to type it each time, but don't name it DAGGER.BAT.
  6. Note: Some say you need to add the line set dos4gvm=@dagger.vmc to your Autoexec or your custom batch file, though the game will run without it.


Information retrived from: http://www.uesp.net/wiki/Daggerfall:Running_without_Cd


System Requirements

Template:SysReq