fox

The single reason for this is that the current Atari800 default, jakub.act was grabbed from PAL machine, just like the previous one, real.act. If you agree here for a "correct" NTSC palette, I can upload it to the Atari800 emulator repository. Not necessarily one - there may be several NTSC palettes to choose from. *.act are plain 768-byte RGB palettes, supported by e.g. Photoshop, so you should have no problem with creating *.act from a picture where Atari colors are shown in order (dark on the left, light on the right). You can then load this *.act file into Atari800 and see how it looks in different programs.

TV displays colors in RGB, naturally. The problem is that colors differ between: PAL/NTSC Atari models and even units hue adjustment in Atari TV models monitors (especially CRT/LCD), brightness/contrast/saturation settings

AFAIK, yes or at least very similar.

Could you give some examples, please? One example would be "Muad Dib Demo" which is crypted using XL/XE OS contents - it needs the original ("old" version) OS to run. I'm sure there are many programs which use unofficial addresses in OS, not only for routines, but also lookup tables (e.g. $80,$40,$20,$10,$08,$04,$02,$01). Another class of programs is these which copy the original ROM contents to RAM and then patch it. I also doubt if Atari++'s OS emulation is 100% compatible with the original OS (including details like C flag set when returning from SIO - some programs really rely on this).

Where have you been for the last ten years? Basically, HIP is 160x239x30 shades and TIP is 160x119x256 colors. A few years ago I have posted English description of TIP to Heaven and Raster. Heaven, do you have it somewhere?

Maybe 95%, but surely not 100%. There were same typos in "his" code as in Atari800, would you believe he hasn't copied it? Anyway, the war between Atari800 team and Thomas is now history and I wish Atari++ well. Probably "most of the time" rather than "at all". Atari800 has "emuos" that is enough for running some games.

Perl rules! For those Windows users who don't want to download and install megabytes of ActivePerl: http://www.mhuffman.com/resource/perl/ Actually, for many scripts perl.exe+perl58.dll are enough. And please s/PERL/Perl/ !

There's a Perl script in cc65 that pretty prints 6502 code (and ca65 directives) in HTML. I don't know if it can change formatting or just adds HTML markup.

Not true.

It will work. Not without special drivers.

Try Atari800. I don't know if the MacOSX port correctly supports the 5200 - if not, ask the author for it, it is easy.

The game enables a POKEY timer interrupt at a very high frequency. The emulation of POKEY timer interrupts is inaccurate in Atari800 (Win). A workaround is: press F8 and type: c 10 40 cont I guess MESS doesn't emulate POKEY timer interrupts at all.

Atari800 does not emulate drive's CPU or ROM. What are these?

Not necessary. With BASIC disabled, press Shift+F5 then F5 to get BASIC.

I implemented the BASIC loader in the development version of Atari800. Ok, thanks.

How does it work? 914361[/snapback] RTFM

The above formula is for NTSC. For PAL, replace 60 with 50, or even better 49.86074561. Or maybe you want the R-Time 8 cartridge: it has a battery-powered real time clock with real date and time.

I agree the comment is misleading - especially as a group of bits are used to indicate a special value. In terms of a 16 bit integer, they are negative as the high bit is set. But these aren't 16-bit integers. IIRC, this does make sense as on the XL the help key also produces a '?' keypress. No. Help has its own keycode. I meant SPECIAL_HANDLER_MASK shouldn't be set for AKEY_HELP.

Live preview of $d20a would be entertaining, right? IIRC, I used VisualBoyAdvance. But it had GUI-based monitor too, I think. Monitors are for coders/hackers, so command-line driven interface is good. It's faster for me to type "d 8000" than to precisely drag scrollbar of disassembly window. And on Win 2k/XP the console window has history, so you can see the output of previous commands. Can you do that with GUI? I personally hate that I can't change fonts in GUI-based monitors. This is easy for console windows. And Alt+Enter rules. And you can copy/paste from the console window.

The comment is misleading, the problems are because the special values are not negative: (input_win.h) #define SPECIAL_HANDLER_MASK 0xf000 /* codes in atari.h file */ #define AKEY_OPTIONDWN 0xffe1 #define AKEY_SELECTDWN 0xffe2 #define AKEY_STARTDWN 0xffe3 #define AKEY_OPTIONUP 0xffe7 #define AKEY_SELECTUP 0xffe8 #define AKEY_STARTUP 0xffe9 #define AKEY_MONITOR 0xffea I think they should be changed to some negative values. And I don't see a reason for AKEY_HELP to be ORed with SPECIAL_HANDLER_MASK. So the above code from input_win.c should be completely removed.

Actually I'm working on Atari800 (for about 5 years or so). show d addr But you see them, don't you? antic/gtia/pokey/pia dlist uh-oh. You just want lots of numbers changing at high speed, that you can't read at all? it's already quite good, I think What?

Right, I forgot about the comma... And also '?' and '*'. Thinking of something else... Call me crazy but do you believe we could have this for programs written in other languages? No. Well, it's good but not PERFECT. I'm going to implement direct BASIC loading anyway.

Who said it can't be? I'll think about it. I'll probably reuse "Load executable". BASIC files can be easily identified (they start with two zeros). Maybe except for ASCII 0-31, 128-255 and the comma (which is commonly used to separate the two filenames for the rename command).

There's an alternative for using H: to load BASIC files. Insert the file as a tape image and type: CLOAD (you'll probably need to press a key after that) and RUN Or simply: RUN"C" This will work for filenames with spaces.

For example, only RUN"H:PACMAN is valid, not RUN"H:PAC-MAN, RUN"H:PAC MAN or RUN"H:PAC-MAN - FOX This isn't an 8-character limit. It is that H: emulation accepts only some characters in filenames. This is to make it compatible with Atari software. You can't use spaces in filenames on Atari - space denotes end of filename. As for the hyphen, it should be probably allowed. I'll fix that. Maybe spaces should be also allowed, I'll have to check if Atari DOSes use space as a delimiter, especially for the rename command. If not, H: will work with spaces, too.