Jaz on 20/10/2004 at 20:41
Did anybody ever get Battlespire to run under Win XP?
If so, how?
I tried all the tricks described in all the various threads about getting older Elder Scrolls games to run under XP, everything but re-installing my comp with a dual boot option. Spire ran perfectly well under Win98, but my old secondary machine died of a HDD failure only recently, luckily after I did a backup of the save games. I'm just too short on HDD space to waste good MB on a second OS, and I need XP for work... buying either another comp or a third HDD is not an option, money is tight nowadays.
The best result I got when trying out all those tricks was an occult DOS extender error message ('unrecoverable exception') with VDMS... all other methods just gave me nothing at all, just a game that wouldn't run.
So... who got Spire to run under XP? Please don't tell me that there's no hope :(.
Thanks in advance
Jaz
P.S.
On another note, here's my modern day rendition of Battlespire's Imago Storm:
(
http://www.schuhmacher-net.de/~nicole/kazdevil4.jpg) Click me if you want to. I liked him a lot in Battlespire, so I chose to remake him under the influence of the Morrowind Dremoras (it's just a 5-minute, unfinished photoedit of the screencap of a character from another game, so please don't expect too much). It's highly unlikely we'll meet him again in Oblivion I guess, but still...
Auriel on 21/10/2004 at 07:52
hmm you haven't mentioned it in your post, have you tried dosbox??
Jaz on 21/10/2004 at 13:29
Yes, I tried DOSBox 6.0 and 6.1, with no result.
Jaz on 5/11/2004 at 06:17
Bumped to relate the final result. It is NOT possible, period. At least I didn't get it to work, no matter what. I managed to scrounge some old computer parts off my local trader last week, however, and built me an incredible PII 400 with Win98.
It works on that set-up, of course.
Ania on 5/11/2004 at 19:17
I like Win 98. I'm still using it on my PC. If it ain't broke, why fix it?
I found that Daggerfall is not too good on 98- can't levitate properly. I now wish I still had a Win 95 PC (in addition to my current one, of course!)
Jaz on 6/11/2004 at 17:07
Quote Posted by Ania
If it ain't broke, why fix it?
Because under Win95/98 we can't do all the office networking the way we need to (my 'private' comp No. 1 is part of a family business office network). But game-wise, I absolutely agree.
uk_john on 11/2/2008 at 20:33
Thanks to a nice UK/American guy - there is a fix at the website below. Just delete, move or rename your current DOSBox 0.72 and download his CVS version form the site. Then, if necessary, download the 1.5 patch from the same page. Finally click on the fix link and copy the text then save it to a text box and name it 'play.bat', copy this play.bat into your game directory.
(
http://www.dvdvideogame.org/battlespireV2.html)
Go into the DOSBox Conf and change cycles to 25-40,000 (I have mine at 40000)
Change the details at the bottom of the Conf under 'autoexec' to point to your game folder.
For ease you can do what I do, which is create a DOSBox shortcut on my desktop and make a copy of the DOSBox Conf, renaming it Battlespire. Then change my DOSBox shortcut icon, by using the icon in your Battlespire game folder and changing the name. Now you have a Battlespire desktop icon called Battlespire. Go into the properties and at the end of the DOSBox exe put -conf Battlespire.conf
as in: "C:\Program Files\DOSBox-0.72 -conf Battlespire.conf"
double click on the icon and DOSBox will open, type CD Batspire (or whatever name you called the folder, or just type 'Play' (from the fix you did earlier - remember?!) NOT 'Spire' if you are already in the game folder (depending how you set the autoexec part!
I did the above and I now, for the first time, having spent days looking for a fix, or finding fixes that didn't work, have a working Battlespire!
Leave comments here saying if it worked for you or not and I will contact the author for you. We have emailed, and he's a nice English guy living in the U.S.!
CheeseshireCat on 12/2/2008 at 13:51
Frankly, the link is 404 :(
