[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference 7.286::atarist

Title:Atari ST, TT, & Falcon
Notice:Please read note 1.0 and its replies before posting!
Moderator:FUNYET::ANDERSON
Created:Mon Apr 04 1988
Last Modified:Tue May 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1433
Total number of notes:10312

1228.0. "MEGA2 DIFF FROM ST??????" by SCAACT::BROWNL () Wed Jan 08 1992 13:08

    OK here's astrange one...
    
    I bought a copy of 'times of Lore' and brought it home. To my
    sadness (it was on sale, so no refunds) It won't boot on my system.
    I called Origin systems and they said the problem was due to a
    difference in the way my Mega 2 does things 9As apposed to an ST.)
     
    I was very surprised that this was a problem. They claimed that I/O
    changed between the two systems and that the MEGA 2 "probably" won't
    be able to do anything with it. 
    
    Now the question......Is there something I can run to emmulate the ST
    (So I can run the game?) Or is there some configuration program I could
    write to make it compatible?
    
    Has anyone else run up against this? And should I trade in my MEGA for
    an ST with more memory so I won't have anymore problems?
    
    Any comments or suggestions are appreciated!
    
    Thanks - Len
    
T.RTitleUserPersonal
Name
DateLines
1228.1You could put in TOS 1.0 and give up Blitter accessYNGSTR::WALLACEWed Jan 08 1992 15:109
The problem is with the different version of TOS. If you buy a 1040ST and
upgrade from TOS 1.0 to TOS 1.2 (or any other version, but 1.2 is what comes,
or at least used to come, in a MEGA) you will have the same problem. It
doesn't affect all games but it affects some.

The problem is that some memory locations that these programs used moved when
TOS was updated.

	Ray
1228.2How about disk based TOS from a 1.0 ROM set?VFOVAX::PATTERSONThe world is flat, it's the universe thats roundWed Jan 08 1992 23:0513
>The problem is with the different version of TOS. If you buy a 1040ST and
>upgrade from TOS 1.0 to TOS 1.2 (or any other version, but 1.2 is what comes,
>or at least used to come, in a MEGA) you will have the same problem. It
>doesn't affect all games but it affects some.
>
>The problem is that some memory locations that these programs used moved when
>TOS was updated.

    Is it possible to create a disk based TOS from the 1.0 ROMs?

    If yes, what would you have to do?

    Jim Patterson
1228.3RUTILE::BISHOPThu Jan 09 1992 03:339
	Len,

	  I believe it is highly illegal for a shop to claim "No refunds on
	Sale Items". If you  don't find a solution and end up getting stuck
	with this, maybe a quick pop down the  local Citizens Advice Bereau
	would help.


				Lewis.
1228.4Not a solutionYNGSTR::WALLACEThu Jan 09 1992 10:536
>    Is it possible to create a disk based TOS from the 1.0 ROMs?
I wouldn't thinks so, but don't know for sure. Even if you did you would have
the same problem where particular memory locations (Joystick x/y etc...) are
at different address' than what the program is expecting.

	Ray
1228.5I will play with creating a bootable disk based TOSVFOVAX::PATTERSONThe world is flat, it's the universe thats roundThu Jan 09 1992 11:4016
>>    Is it possible to create a disk based TOS from the 1.0 ROMs?
>I wouldn't thinks so, but don't know for sure. Even if you did you would have
>the same problem where particular memory locations (Joystick x/y etc...) are
>at different address' than what the program is expecting.

    I have a NEW STE at TOS V1.62, and a OLD 1040 STFM at TOS V1.0.

    I will look and see if I can find a disk of mine that does not work, if
    I can I will see if I can create a bootable disk with TOS 1.0 on it.

    Now, I know I can use the TOS 1.0 on it because I own both machines, but
    does anyone know what the copyright restictions are on someone with just
    one machine, using a disk based copy of my roms?  The person did buy a
    machine and pay for the newer TOS version.

    Jim Patterson
1228.6TOS 1.0 is available nowDONVAX::PETERSDon Peters, CTC2-1/C14, 287-3153Fri Jan 10 1992 13:3021
>>    Is it possible to create a disk based TOS from the 1.0 ROMs?
>I wouldn't thinks so, but don't know for sure. Even if you did you would have
>the same problem where particular memory locations (Joystick x/y etc...) are
>at different address' than what the program is expecting.

    You don't have to create a disk based TOS 1.0 - one already exists. I
    and others used it way back when the ST first came out (1985). In fact,
    I still use it now, since my 520 was upgraded to TOS 1.4, and ROGUE
    thinks you are a pirate if you try running it under 1.4. The solution -
    I first boot up with my TOS 1.0 disk, then pop in the ROGUE disk and
    run ROGUE. Works great.

    All the system memory locations should be the same, so you shouldn't
    have any problem.

    Actually, one problem would be if you have to boot from the game disk
    rather than running it under TOS. The boot would probably cause you
    to lose the just-installed 1.0, and revert back to whatever TOS you have.

    I don't think there is a problem giving out TOS 1.0, since it only
    enables you to run what you rightfully own.
1228.7Hmmm...maybe I could use a tos 1.0 boot diskSCAACT::BROWNLSat Jan 11 1992 14:367
    What are the odds that I could access the disk and manually load the
    game, as opposed to letting it autoload on it's own???
    
    Would I be aBle to access the disk on TOS 1.4?  Or do the
    differences between the two versions also effect the disk access?
    
    Len
1228.8Two ideas to solve thisVFOVAX::PATTERSONThe world is flat, it's the universe thats roundSun Jan 12 1992 15:1012
>    What are the odds that I could access the disk and manually load the
>    game, as opposed to letting it autoload on it's own???
    
    That depends on the game.  I can think of several things that might
    be able ot be done:

	1) Create a disk with a bootable TOS 1.0, and modify it to prompt
	   you to insert a disk to be booted.

	2) Create a program that reads a floppy and simulates the actions
	   of TOS booting.  For example executing the boot sector if it has
	   code in it.