PDA

View Full Version : Searching for Turbo C 1.0 (not C++ 1.0).



datajerk
January 29th, 2014, 01:52 PM
Does anyone here have the original Turbo C 1.0 (not C++ 1.0 that is circulating around the net) they can share?

Thanks.

FunctionalLimits
January 29th, 2014, 03:43 PM
Borland Turbo C... That brings back such fond memories! Unfortunately, the only copy I might have is packed away in a box somewhere, and I can't seem to find it online either. Hope someone has it. I'd love to get a copy too.

barythrin
January 29th, 2014, 04:12 PM
Didn't they make it free or was that just newer versions? (Just curious, I'll check my archive in a bit). This may also be a possible thing to find on that betaarchive.com site although that may just be beta versions.

FunctionalLimits
January 29th, 2014, 04:22 PM
They did make it free, but version 1.0 is so antique it seems to have vanished from the Interwebs.

krebizfan
January 29th, 2014, 04:39 PM
Is there a specific reason you need Turbo C 1.0 not the freely available Turbo C 2.01? Turbo C 1.0 was very buggy, not sure if buggier than MS C 6 but neither was exactly a shining beacon of quality code. Version 1.5 was much improved and 2.01 is reasonably solid.

FunctionalLimits
January 29th, 2014, 05:38 PM
And, OP, note that Turbo C 2.01 is available for download: http://edn.embarcadero.com/article/20841

Apparently the original ship date for this version was May 1989.

giobbi
January 30th, 2014, 02:57 AM
Of course if you asked for 1.0, probably you need 1.0 and nothing more than this, however, just in case, Vetusware.com has the 1.5 release.

https://www.google.com/search?q=borland+turbo+C+site%3Avetusware.com#q=bo rland+turbo+C+site%3Avetusware.com&start=0

You need to register, but it's for free.

--Giovi

SomeGuy
January 30th, 2014, 03:49 AM
Unfortunately, that site has been fubard for a a while, again (only the main page loads). Or is it just me?

giobbi
January 30th, 2014, 05:39 AM
Unfortunately, that site has been fubard for a a while, again (only the main page loads). Or is it just me?

oops, you're right. I downloaded and uploaded some zip files few days ago. Maybe it's just a temporary problem....

datajerk
January 30th, 2014, 06:43 AM
Is there a specific reason you need Turbo C 1.0 not the freely available Turbo C 2.01? Turbo C 1.0 was very buggy, not sure if buggier than MS C 6 but neither was exactly a shining beacon of quality code. Version 1.5 was much improved and 2.01 is reasonably solid.

I'm trying to help a friend find a C compiler to use on the HP Portable Plus. The Portable Plus has MS-DOS 2 embedded, limited memory, and is not 100% IBM compatible. Newer code often has problems. I've pointed this person to some other compilers that I think will work (e.g. Aztec C), IIRC TC 3 and TC++ 1 didn't work out for him.

Thanks.

geneb
January 30th, 2014, 07:53 AM
Unless he's stuck on C, I'd recommend Turbo Pascal 3.01A for DOS.

g.

deathshadow
January 30th, 2014, 08:31 AM
I'd also suggest if one wants to program on that device, TP3 is a fine choice... Though I'd suggest running a more recent version on a modern machine in DOSBox, then copying the executable over when done instead of programming on that in the first place.

You might try winworldpc
http://winworldpc.com

They've got Turbo C 1.5 and 2.01, as well as a few others (like Microsoft) you might try.

Is that plus the stock 256k or the loaded out 512k? If the former it really might not have enough 'room' to run a whole lot of... well... anything.

krebizfan
January 30th, 2014, 10:11 AM
Normally, I would suggest trying early QuickC for this but I don't know if the HP Portable Plus has the ability to run the debugger. When writing software for an old system, I usually write on a new system and test inside a virtual machine. That gets rid of 90%+ of the bugs before I transfer the code to the older system. Especially with an unconventional system, it helps to have a debugger on the actual hardware to catch any surprises.

FunctionalLimits
January 30th, 2014, 01:25 PM
Huh. I had never heard of that HP. It sounds interesting...and slightly quirky.

Would Small C work?

Somewhat OT (or premature), but HP had a "ROM IMAGE Development Package" for this device so that it could be used as a development system for applications stored in plug-in ROM modules (the device's ROM drawers).
The manual is here: http://www.jeffcalc.hp41.eu/hpplus/files/vger.pdf
Summary of commands, etc.: http://www.jeffcalc.hp41.eu/hpplus/files/makerom.pdf
Software: http://www.jeffcalc.hp41.eu/hpplus/files/tools.zip

Other useful info is at the same site, including the tech ref manual: http://www.jeffcalc.hp41.eu/hpplus/index.html

For misc software including a "Programmers Tool Kit" (don't know what's in this): http://www.hpmuseum.net/exhibit.php?swc=11

datajerk
January 31st, 2014, 08:56 AM
Unless he's stuck on C, I'd recommend Turbo Pascal 3.01A for DOS.

Good call. IMHO, do assembly.

datajerk
January 31st, 2014, 08:59 AM
IThough I'd suggest running a more recent version on a modern machine in DOSBox, then copying the executable over when done instead of programming on that in the first place.


That is exactly what I'd go. I cross develop for all my retro platforms as much as possible. However, there are those than enjoy the pain and frustration of coding on the metal.



You might try winworldpc
http://winworldpc.com

They've got Turbo C 1.5 and 2.01, as well as a few others (like Microsoft) you might try.

Thanks for the tip. I'll point him to this thread. Hopefully he caught this.



Is that plus the stock 256k or the loaded out 512k? If the former it really might not have enough 'room' to run a whole lot of... well... anything.

IIRC, he said 512K. I have the non plus version with about 200K. I plan to take it out this summer and do some assembly programming on it.

datajerk
January 31st, 2014, 09:01 AM
Normally, I would suggest trying early QuickC for this but I don't know if the HP Portable Plus has the ability to run the debugger. When writing software for an old system, I usually write on a new system and test inside a virtual machine. That gets rid of 90%+ of the bugs before I transfer the code to the older system. Especially with an unconventional system, it helps to have a debugger on the actual hardware to catch any surprises.

I have a Portable with all the docs, I'll have to check. Like you I do the same, use a virtual env.

datajerk
January 31st, 2014, 09:01 AM
Huh. I had never heard of that HP. It sounds interesting...and slightly quirky.

Would Small C work?

Somewhat OT (or premature), but HP had a "ROM IMAGE Development Package" for this device so that it could be used as a development system for applications stored in plug-in ROM modules (the device's ROM drawers).
The manual is here: http://www.jeffcalc.hp41.eu/hpplus/files/vger.pdf
Summary of commands, etc.: http://www.jeffcalc.hp41.eu/hpplus/files/makerom.pdf
Software: http://www.jeffcalc.hp41.eu/hpplus/files/tools.zip

Other useful info is at the same site, including the tech ref manual: http://www.jeffcalc.hp41.eu/hpplus/index.html

For misc software including a "Programmers Tool Kit" (don't know what's in this): http://www.hpmuseum.net/exhibit.php?swc=11

Thanks for all the links. I'll point my friend here.

Dave Frederickson
May 7th, 2014, 05:17 PM
Turbo C 1.0.
https://drive.google.com/file/d/0B-GPxmpKVCV0TTJoS3JlVmRwVkU/edit?usp=sharing

Dave