|
Archie-ology |
|
RichardH (14:29 21/11/2011) hubersn (16:43 21/11/2011) RichardH (17:16 21/11/2011) DiscoBurgess (11:29 3/1/2012) Acornut (22:30 4/1/2012) trevj (10:25 5/1/2012) Acornut (11:20 5/1/2012) trevj (08:40 6/1/2012) VincceH (09:32 6/1/2012) apacketofsweets (23:54 21/11/2011) RichardH (02:12 22/11/2011)
|
|
Richard Heggs |
Message #119352, posted by RichardH at 14:29, 21/11/2011 |
Member
Posts: 3
|
Hi, first time poster here. I'm thinking about getting back into RiscOS programming (after > 15 years, so it'll be like starting again).
My renewed interest came after discovering some disks in a box in the attic, which contained some of my early development work, in particular some software written under contract, which read interesting things from a multiplexed serial connection and did other interesting things with them. A few weeks later, I saw an A7000 at a car boot sale, for £25. So I bought it, took it home, and lo and behold! the disks were readable - all the source code from the project.
The A7000 also has a copy of Acorn Desktop C R4, and this is where my joy began to attenuate. The original software was certainly not compiled with it, and won't compile now. There are various problems, and I'm led to believe that it was a different compiler that I used back then (date on source files is 1992).
The source includes bios.h and calls bioscom(), so I'm wondering if it might have been compiled on a TurboC variety.
I'm pretty sure that it was compiled and ran on an A405 or A410.
Unfortunately the disks don't contain any of my development notes. Would anyone care to hazard a guess about which compiler I might have used? I think I'll ask Santa for an Iyonix for Christmas, so that I can play with RiscOS 5, but I'd really like to get this software working again for old-times' sake. It's not ever going to be useful for anyone (and the company it was written for no longer exists), but it would warm the cockles of my heart if I could get it working again, if only to see it complain that it can't contact its dataloggers.
[Edited by RichardH at 17:08, 21/11/2011] |
|
[ Log in to reply ] |
|
Steffen Huber |
Message #119353, posted by hubersn at 16:43, 21/11/2011, in reply to message #119352 |
Member
Posts: 91
|
I think the only "other" C compiler available back then was Easy C by Beebug. No idea if it had something like "bios.h", which sounds like DOS stuff. |
|
[ Log in to reply ] |
|
Richard Heggs |
Message #119354, posted by RichardH at 17:16, 21/11/2011, in reply to message #119353 |
Member
Posts: 3
|
Hrm. Easy C doesn't ring a bell. The program was briefly developed on x86 (that's where the _DI came from - I've just looked at the source and it's commented out for ARM). Definitely ran on an Archie, though. I wonder if I picked up a bios.h from somewhere that had been hacked to run on ARM.
This is frustrating. I really can't remember much about the programming environment I used back then. The source code is tantalising, but without my development notes I'm stuck. I might have to write it off as ancient history, but it'll be disappointing. |
|
[ Log in to reply ] |
|
Sion |
Message #119355, posted by apacketofsweets at 23:54, 21/11/2011, in reply to message #119352 |
RISC OS, too cool for Javascript.
Posts: 110
|
I think I'll ask Santa for an Iyonix for Christmas, so that I can play with RiscOS 5, but I'd really like to get this software working again for old-times' sake. If you're looking for a capable RISC OS 5 machine you might want to also have a look at the BeagleBoard and the ARMini, as they are still in production, unlike the Iyonix. Welcome back to RISC OS! |
|
[ Log in to reply ] |
|
Richard Heggs |
Message #119356, posted by RichardH at 02:12, 22/11/2011, in reply to message #119355 |
Member
Posts: 3
|
Yes, I've just had this conversation on riscosopen.org. The BeagleBoard xM looks very nice indeed, and much cheaper than a 2nd hand Iyonix.
Letter to Santa amended accordingly. Now I just need to remember how ARM assembler works... I've spent the last 15 years or so working on various Unixes and Linux, and almost exclusively in C. |
|
[ Log in to reply ] |
|
Glenn Burgess |
Message #119449, posted by DiscoBurgess at 11:29, 3/1/2012, in reply to message #119354 |
Member
Posts: 22
|
I may have the wrong end of the stick here - I don't really work in C, but I seem to recall that there was a port of GCC for RISC OS... |
|
[ Log in to reply ] |
|
Blind Moose |
Message #119456, posted by Acornut at 22:30, 4/1/2012, in reply to message #119449 |
No-eye-deer (No Idea)
Posts: 487
|
... GCC for RISC OS... This, perchance? |
|
[ Log in to reply ] |
|
Trevor Johnson |
Message #119458, posted by trevj at 10:25, 5/1/2012, in reply to message #119456 |
Member
Posts: 660
|
I thought it was GCC for RISC OS! |
|
[ Log in to reply ] |
|
Blind Moose |
Message #119459, posted by Acornut at 11:20, 5/1/2012, in reply to message #119458 |
No-eye-deer (No Idea)
Posts: 487
|
Yeah. That's current, but I thought Glenn was recalling the old version. |
|
[ Log in to reply ] |
|
Trevor Johnson |
Message #119461, posted by trevj at 08:40, 6/1/2012, in reply to message #119459 |
Member
Posts: 660
|
Ah, OK. |
|
[ Log in to reply ] |
|
VinceH |
Message #119462, posted by VincceH at 09:32, 6/1/2012, in reply to message #119353 |
Lowering the tone since the dawn of time
Posts: 1600
|
I think the only "other" C compiler available back then was Easy C by Beebug. No idea if it had something like "bios.h", which sounds like DOS stuff. The predecessor to Easy C was Desktop C - which I used for Floopy. I'd be inclined to point in that direction, although I (obviously) can't remember for certain if there was a 'bios.h'
I'd check the manual - which I did actually find during my mass clear out in the latter half of last year. The problem is, when I say 'clear out' I do actually mean clear out. I don't think I'd have kept that. |
|
[ Log in to reply ] |
|
|