 | | Re: fast firmware downloader
|
|
(...) I'm willing to cover the DOS port since I'm working on a DOS->RCX comm project already. I already have my HP LX200 doing minimal comm with the RCX with hopes of having it ride alongside as a computational component. -Wes Matchett (25 years ago, 28-Oct-99, to lugnet.robotics.rcx.legos, lugnet.robotics.rcx, lugnet.robotics.rcx.pbforth)
|
| |
| | Re: fast firmware downloader
|
|
(...) Wes, A good place to start with the porting is to grab the latest NQC source code from www.enteract.com/~dbaum/nqc and take a look at the family of PSerial classes in the platform directory. Create a new class (e.g. PSerial_dos) that (...) (25 years ago, 30-Oct-99, to lugnet.robotics.rcx.legos, lugnet.robotics.rcx, lugnet.robotics.rcx.pbforth)
|
| |
| | RE: fast firmware downloader
|
|
(...) Wes and Dave, I pulled out an ancient copy of Turbo C++ 3.0 for DOS. It compiles most of the code but chokes on the >8 character file names. I might have to try Microsoft VC++ next....to make a DOS executable. I also found a DOS C Comm library (...) (25 years ago, 30-Oct-99, to lugnet.robotics.rcx.legos, lugnet.robotics.rcx, lugnet.robotics.rcx.pbforth)
|
| |
| | RE: fast firmware downloader
|
|
(...) Yeah. Not sure about the hardware interface, though. Would it be possible to run the DOS executable to generate a binary and then download it otherwise? I too am not sure what this whole discussion is about- if it is just NQC, then it is (...) (25 years ago, 30-Oct-99, to lugnet.robotics.rcx.legos, lugnet.robotics.rcx, lugnet.robotics.rcx.pbforth)
|
| |
| | Re: fast firmware downloader
|
|
I hate to admit it, but the version of Turbo C++ I just pulled out is 1.00. I departed from the Borland compiler shortly after acquiring this version and did not keep up with advances. Would I gain any advantages by finding a later version, or (...) (25 years ago, 31-Oct-99, to lugnet.robotics.rcx.legos, lugnet.robotics.rcx, lugnet.robotics.rcx.pbforth)
|
