OLD ROMS
17 messages in this thread
You guys are going to think I'm crazy, but I need to run 1.5? ROMS and 1.3 os
on a 4000. Can I replace the 2.xx ROMS with 1.5? ROMS. This has been
sucessful on 2000's in the past.
Yes yes, I know that it would be better to make the program mods under 2.xx but
I cannot at this time. I must distribute this system as written.
Anyone know???
Ken;
Though not absolutely certain… you would have better luck growing
Redwood trees at the North Pole (and it would take less time too).
I am certain that an A2000 ROM will not work in an A4000 and almost
certain that an A3000 ROM also will not work. There are just too many
hardware differences.
-bill
Bill;
Thanks for the inevritable news. It's been literaly years since I did any
AMIGA research / development. For years (in the US) Commadore sold the A2000
and simply upgraded periferals, expansion cards etc. Obviously, the A3000 and
A4000 are hardware revisions. Assuming I can solve my other problems, are both
machines in production today, and do you know the differences between them?
Keep in mind that I would like to minimize the program mods to implement my
solution since I am porting this package to *WINDOWS* for marketing reasons
(sorry).
– Ken Gendrich, The Cadcrete Company
– CIS: 73633,446
The A3000 is no longer in production and is getting damn hard to find. If
you'd looked just a month or two, you'd have found them being blown out
cheap (which is why they are now damn hard to find).
The A4000 won't run 1.3.
— Dale L. Larson, Intangible Assets Manufacturing
— INTERNET:dale@iam.com
Ken;
I did not get the other reply to your message on this session so I imagine
that I'll be repeating that response. However, to answer… The A3000 is
a discontinued model <sob> but the A4000 is a current production machine.
Most "properly" written software that was created under any version of the
OS will run on any other version. As a practical matter, almost
everything that has been created for AmigaOS 2.x will run on any machine
that is running 2.x or above.
Unfortunately, software that uses asm code often breaks between processors
and software where the code directly accesses the hardware breaks (that is
does so without requesting the resource).
-bill
Bill:
Sorry I did not reply, thanks for the info on the A3000/A4000.
BTW, do you (or anyone) know about any problems with creating code that is not
inherently "32bit pure" using the MANX (v.so old I can't remember which it is)
C compiler? Note that there are no ASM embedded calls or any ASM code linked
in. This would be native C code (obviously with system calls). Thanks in
advance…
-Ken
Ken;
No I don't (others may though). Manx is getting a bit "long in the tooth"
now. There have been several OS releases since the last Manx upgrade.
-bill
My product, InterChange, had a bug that appeared with the introduction of
AmigaDOS 3.0 and the A4000. It had to do with the proper method of
deterimining the screen size. This was the only problem we had with AmigaDOS
3.0 and the A4000. Yes, if you're still running the same executable compiled
under Manx that was made several years ago, you might be in trouble for any
number of reasons: compiler improvements for OS compatibility, 32-bit clean
code, etc. I'd bet $100 on the former as opposed to $1 on the latter. It's
much more probable that you've got some problem with Intuition or AmigaDOS
function calls than any problem with the compiler. No sensible compiler would
have been tinkering with non-32-bit code, that's been an issue since the very
beginning with the 68020.
Do you still have the source code for your applications? It sounds like you do,
or you wouldn't be considering a port to Windows. Hire an Amiga-head
programmer and have them search for bugs…
1.5 Roms? No such thing unless I missed something <g>. I think you mean
the 1.3 Kickstart and 1.3 Workbench. You can run 1.3 on a 4000, but you
need to get a copy of SET040.LHA, and then a file image of the the 1.3
Kickstart either from a 1000 or 3000 owner.
//
\X/ John – (TechnoJunkie at heart)
So, <grin> I've attracted some fun filled remarks in regards to my 1.5 ROMS.
Gosh, maybe I should claim it was a typo…. <not>.
Thanks for the help. Who knows, maybe we will get lucky and our 1.3 code will
run better on a A4000 with 3.x than it did on the A2xxx with 2.x. If not, my
other options appear to be to break into the code; sell used 2xxx's (dont get
me wrong, I understand the value of a used 2000, but my customers have a
difficult time spending 30,000 on software, then get used equipment). ; or get
lucky with the 4000 series.
Did you mean to say, that I can "emulate" 1.3 on a 4000 with SET040A.LHA + 1.3
kickstart? ok, at least I have a last resort, thanks
— Ken
Ps. Anyone know how to rename forum message topics….. <g>
Ken,
no, you need SET040 and the Kickstart disk, not ROM. If you need the
disk, I have one that I'll never use again.
Brian
bjbart@watserv.ucr.edu
Brian,
Is SET040 in compuserves library? If not could you please upload it!!
<- James Scott ->
Automated with AutoPilot!!!! Version 1.6
James,
SET040.LHA, Lib 11, AmigaTech.
Brian
bjbart@watserv.ucr.edu
Thanks for the reply, I'll try and find it.
<- James Scott ->
Automated with AutoPilot!!!! Version 1.6
Really? You're *sure* you can run 1.3 on the A4000? And you don't loose
HD and video? I haven't tried to do it, so maybe I shouldn't have spoken,
but it sure seems like it wouldn't work well…
— Dale L. Larson, Intangible Assets Manufacturing
— INTERNET:dale@iam.com
I'm with you (I think that I would be dissappointed to learn that 1.3
would run on an A4000) but beyond that, I can't imagine that a 1.3 rom
would have even the vagues idea of how to manipulate an A4000.
-bill
John;
An A1000 kickstart won't work for an A3000 much less an A4000.
-bill