Technical documentation scans to PDF

[Technical documentation scans to PDF]

Yes.

I have used the PDF files which contains the scans provided by Lars Hannig.

I did some proof reading, but cannot guarantee the OCR is perfect.

[Technical documentation scans to PDF]

Good evening,

 

Just a quick note about the scaned technical documentation, the ones found in the PDF,

I have done an OCR action on one of them (Technical Overview) to see the feasability to have a clean PDF file. I wanted to give you the result of this action.

What do you think about the results?

 

Thanks,

 

02-TechnicalOverview_10-18.April.1995.pdf

[GCC and Visual Studio error reporting integration]

Hello,

For the people using the Windows environement,

I've found a Perl script to fix an issue when working with GCC and Visual Studio (2013 Express in my case).

The problem came from the format error reporting between GCC and VS, there are not compatible so we can see the error messages in the VS Output window but we cannot interact with them. So, you have to look manually for the line(s) and file(s) to see the errors.

This script takes the output produced by a batch file and converts the error messages. The following line has to be added in the NMake section of your project configuration properties for the : Build, Rebuild All, and Clean Command Line.

build.bat 2>&1 | c:\Perl\bin\perl.exe gccfilt.pl

The Zip file contains the script and a screen capture from VS.

I'm not the author of the script and the original link is here : http://www.codeproject.com/Articles/370890/GCCFilter-A-script-for-compiling-with-GCC-in-Visua

Thanks,

gccfilt.zip

[A new linker for Atari Jaguar programming]

Thank you for the contact. I'm in touch with Seb about the issue. I'm using Vlink now but Jlinker deserves reporting as well. :-)

[A new linker for Atari Jaguar programming]

Hello,

 

I'm using Jlinker on Windows and I meet an issue reported as "unsupported relocation information in Absolute COFF export".

 

I use C (m68k-aout-gcc) and ASM (smac).

My compiler options are -c -m68000 -Wall -Werror

My ASM options are -fb -rp -v

Jlinker options are -v -w -e -rp -a 802000 x 4000

 

Could you point me on directions to know where the problems may come from?

 

Thanks.

[Jagulator with debugger]

Hi Shamus,

Great you still consider the tracing. If we can start by tracing the 68K only, it can be useful, And, hopefully it can reduce the amount of work?

Beside tracing, do you have some additional stuff improvements in mind?

Thanks,

[Jagulator with debugger]

Hi,

Do you think we have a chance to see a tracing support in the future? I can serve as tester if it can help a little.

For the moment, I have only the emulator to check the .cof and no (serious) tools to debug yet. But I do not complain, the emulator is cool and this is just a hobby.

Thanks,

[Jagulator with debugger]

Sounds good. I'm able to see the registers, memory, etc. Do you know by any chance how we can trace the code? Thanks.

[Jagulator with debugger]

Hi All,

 

I have heard about a Jagulator version with an integrated debugger. I've looked for it and was out of luck so far.

Do you know if such version exists and where it can be downloaded?

 

Also, I wanted to thank you for all the valuable informations you have put in this site over the years.