Ion Mage

In DB, once I start loading the file, it just never loads. Its like the load time is a year. Whether its crashing or just taking literally a year is hard to say, I believe DB was still running in the task manager.

So... anyone got an answer to this new development, DB crashing on a savegame load?

Alright, since it was taking WAY to long to install SP2 on the laptop, I opted to get some DOSBox action on my desktop. I reinstalled the game, and transferred the campaign in progress to it, by copying the SAVEGAME folder over. DB worked fine until I tried loading a game. Is Apoc wierd with savegame transfers? EDIT: Belay that, I got DB working on the laptop, and it still seemed to crash at the loading of a save, and this is the original install that made said save file. I tried varying my cycles and even frameskip. Very wierd.

Well, I got the Manor, but Koch wasnt there at all! Oh well, switzerland is open to me, and from what I hear theres a random encounter there to get PKs.

Okay, according to some hearsay and FAQs, I gather that I need to capture this Koch guy to get to the Organization storehouse, wherein I get my first PKs. Now, I already finished the German Intelligence HQ, and got both clues from it. I should be getting the german manor now! But, I dont have it. I also did the mission where I get the clue detailing how to read coded messages, but that did nothing to help me on this matter. What other missions need to be done to unlock the German Manor?

Alright, I'll install SP2 when I get the chance too. ALready tried removing Zonealarm (laptops are easy to disconnect from the net, see). No go.

WinXP. Service pack 1. Was SP1 when it ran. 1.2 GHz Celeron Integrated video system 256 MB RAM Only programs that run are zonealarm and the windows update thing (which I CANNOT get to go away... should I get SP2? I heard initially there were problems but I'm hearing of that less and less). Was this way in the past. Definately not any other interfereing program, I tried ctrl-alt-deleting most of them to no avail. And yes, same deal as before, when it ran.

Alright, tried DB tonight, and this time it just plain didnt work! Just jumped straight back to the exit message. So, I tried removing the VDMSound load line from XCOM3.bat (using VDMSOund does admittedly require the no-cd patch), and the game loads... and still gives me the red text thing, as the game runs under it regardless. Of course, the red text wasnt as plentiful, but only because VDMS isnt loading alongside the game. What this means is, it isnt VDMSound doing it. I dont see why new drivers would futz with DOS games having the DOS prompt drawn over them, and actually, I believe I had some other DOS games running just fine with my current setup!

Thing is, I got the drivers to fix a video issue. Basically, heres the order of things; Installed apoc It doesnt work Installed VDMSound, and ocnfigured Apoc to autoload it It works. Surprisingly well Monitor starts failing Called tech support, and they install a whole new monitor on it. Keep in mind its a laptop, so monitors are a bit more complex for those The video drivers I had dont seem to work with said new monitor, so they send it to the warehouse to get new drivers, which DO work I get laptop back, and it works again! The monitor is functioning! Oh wait, Apoc is giving me this problem now. Wierd... So, I dont want to toy with the drivers, at least not in the area of installing new ones, in fear of my monitor failing again. As stated before, its like the DOS prompt is being drawn OVER the game, even though its running, because I can hear the sound, and hitting escape registers the 'button press' sound, and exits the game. Maybe it was just an older version of Apoc I was using, who knows. I'll try DB again, I guess. But if someone knows whats wrong, that would be swell.

I wasnt using DOSBox, just VDMSound. And I wasnt using DOSBox because said laptop is a meager 1.2 GHz Celeron, runs apoc in DOSBox VERY slow. A solution to my VDMSound issues would be preferred.

My laptop was configured to run apocalypse properly, with VDMSound, mousectl, and the no-cd and svga fixes. I got a nice campaign going. Then, I had to send my laptop away for some repairs to the monitor, which apparently included getting a new monitor all together, and reinstalling the display drivers. It has an integrated video system for a video card, fyi. Now, I tried running the game again. Loaded VDMSound and mousectl properly, but when the game fully loaded and ran, the 'text' screen stayed, and even displayed in red! By 'text', I mean the screen saying that VDMSound and mousectl are loading, you know, the DOS prompt. Thing is, while the text is red, I can hear the music just fine. And pressing escape registers the 'button press' sound, and ends the program. From the looks of it, the game is running, its just that the DOS prompt is displaying OVER the game itself! Anyone familiar with this issue?

I've had the original S2 for a while. Now, I never finished it, and was about to restart, but heres the thing; I'm about to get the expansion (hey, dont blame me for being late, blame them for not doing well at making it available in America )does the expansion affect the core game in any way? And, if so, is it possible to use a core game save pre-xpac install and benefit from xpac content, or is the new content of S3 solely for the new campaign? In other words, could I start the game now, before I have the expansion at hand (well, the gold edition as I'm going to get), and get the S3 content after I get S3, or would I have to restart again for that?

It said I act 24, I'm 19.

Heh, turns out I have THREE exams this week. Feel glad we don't have sims on the weekdays

Oh my god... its starting ack up! I have two exams THIS week, but after that I should be somewhat free. I'll try and start attending again now. We're going to need a refresher, too. Loonie, you said you would create a 'previous events' page for newbies? May be a good idea to make one now, not just for the newbies I personally remember quite a bit, but I onyl vaguely remember what the current mission we were on was about.