Jump to content
Sign in to follow this  
pichorra

Command & Conquer winDOwS MOD!

Recommended Posts

speaking of which, is RA dos more similar to ra95 than cnc dos to cnc95?

Edited by Sonarpulse

Share this post


Link to post

Seeing as C&C95 is an actual win95 re-release of the older DOS C&C, while RA95 and DOS RA were developed together, the answer to that is definitely yes.

Share this post


Link to post
Seeing as C&C95 is an actual win95 re-release of the older DOS C&C, while RA95 and DOS RA were developed together, the answer to that is definitely yes.

That's what I thought, Just double checking. I had heard from making scenarios that RA-dos is sometimes LESS buggy.

 

Good luck finding the function.

Share this post


Link to post
That's what I thought, Just double checking. I had heard from making scenarios that RA-dos is sometimes LESS buggy.

 

Good luck finding the function.

 

Because DOS RA simple do not crashes when tries to read/write an memory reserved to another thing. It always runs in real mode (or protected?, i don't remember)

Share this post


Link to post

DOS simply doesn't care if a program writes outside its designated memory, since it doesn't do multi-tasking. Windows is much stricter in controlling that. So (in Windows) as long as the erroneous memory writes and reads are still in the memory reserved for the DOS shell, it will indeed not crash.

 

This does not mean that the game works correctly though. When it succeeds in reading data from an illegal memory address, it uses that data to continue the game, meaning that technically, the game gets corrupted a little bit more each time that happens. This obviously means that there is a chance this will cause a fatal game crash at a later moment, when doing something that seems unrelated to the thing that went wrong, but is the ultimate effect of a cascade of small errors produced by it.

Share this post


Link to post
DOS simply doesn't care if a program writes outside its designated memory, since it doesn't do multi-tasking. Windows is much stricter in controlling that. So (in Windows) as long as the erroneous memory writes and reads are still in the memory reserved for the DOS shell, it will indeed not crash.

 

This does not mean that the game works correctly though. When it succeeds in reading data from an illegal memory address, it uses that data to continue the game, meaning that technically, the game gets corrupted a little bit more each time that happens. This obviously means that there is a chance this will cause a fatal game crash at a later moment, when doing something that seems unrelated to the thing that went wrong, but is the ultimate effect of a cascade of small errors produced by it.

 

Then we get a blue screen of dead! :P (jk... DOS simple freeze)

Share this post


Link to post

You usually get the Runtime Error written on the screen going over whatever was there, in huge-sized terminal-font letters, in whatever colour was on the colour spot normally occupied by the system text colour (in RA1, usually brown) :P

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.

×