Marius1976

Hi

This morning my BBS computer crashed. Well... the ramdisk...

Then I picked another Atari from my good working stack, and after a few hours... same happened.

In my room it is due to hot weather around 38-40 degrees celcius (around 100-104Fahrenheid)

Is there any chance that these higher temperatures are causing trouble with my atari's.

They are moderately modded ... so I can imagine the heat from the components has a harder time leaving the machine.

Any clues?

Greetz
M.

Is this a known bug?

Try this:

1. Boot SpartaDos 3.3a from a write protected disk (or set to protected in emulator)

2. Type from the prompt this:

COPY E: D:TEST.DAT

3. Now type a short txt in the blank screen. Like"Hello World"

4. Now press CONTROL+3 to write the file 'test.dat' to your protected SpartaDos 3.3a partition

5. No error... but also no file (phew)

So the protection does work... that is nice, but there is no error message. This is rather inconvenient since I need to know my write action did actually work.

Is this also happening with other SpartaDos versions?

Greetz
M.

Hi!

Project: OS-switching LOGIC (already working), controlled by PIA (also working) and menu driven (also operational!)

I'm writing all this into a hacked version of XL/XE OS. The goal is that this OS can still be used as XL/XE OS, so I do not waste one OS slot in my EPROM.

The goal (which already works great is this)

1. Atari switches on (or user presses RESET)
2. Checks whether inverse video is pressed or not
3a. Pressed? Then show OS CHOICE menu.
3b. Not pressed then read NVRAM RTC (DS1307) (=OS CHOICE), make CHOICE and do REBOOT

Everything works great. Pressing reset + holding the inverse video key results in a little screen where the user can make the OS-choice and then reboot with the new selected OS. Works great too.

PA4, 5 and 6 are used to switch banks of OS ROM (max 1Mbit os). DS1307 RTC has NVRAM onboard, which is used to store OS setting. So even when Atari is switched on, it immediately boots the last used OS. Very handy!

But now here it comes:
On POWERUP sometimes the keyboard is not ALWAYS read out. Sometimes yes, sometimes no. This drives me crazy. Everything works great, but I can not understand why the keyboard is not read out right on powerup state. I added loops (pause), no effect. I tried holding reset longer while powerup, no effect. As far as I know it has nothing to do with IRQ's or keyboard handler, since all that is not used on this level. I simply read out the hardware-state of the keyboard-keycombination.

I changed a few things in the original OS, so let me explain what happens in my OS:

This is how my new reset routine looks like:

C2AA		  SEI
C2AB		  JMP $CB65 ; CB65 - CBFF is a not used area of the rom; great place to store custom routine!

This is my code on $CB65 and up:

			  LDX #140		; this is part of the original reset routine
RES1              DEY			  
			  BNE RES1
			  DEX
			  BNE RES1
			  CLD
			  LDX #$FF
			  TXS
LOOP              LDA #$23		; pokey must be initialized to enable keyboard circuit
			  STA $D20F
			  LDA $D209	   ; read keyboardcode
			  CMP #39		 ; 39 is inverse video
			  BEQ STILLKEY	; if inverse was last key, check if key is still down
			  DEX			 ;
			  BNE LOOP		; I thought a loop is a good idea, but it still fails on powerup
			  JMP RESTORE	 ; inverse was not pressed, then restore the 'saved' OS
STILLKEY          LDA $D20F	   ;
			  AND #$04		; check key is still down?
			  BEQ MENU		; yes? Then enable the OS menu
			  JMP RESTORE	 ; no? then restore the 'saved' OS
MENU              JSR $C484	   ; do some necessary hardware init
			  LDA #$23		; re-enable keyboard (which is disabled after hwinit)
			  STA $D20F		
			  LDA #$7F		; enable selftest rom
			  STA $D301
			  JMP $5000	   ; jmp to menu
RESTORE           JSR $C484	   ; do some necessary hardware init
			  LDA $#23		; re-enable keyboard
			  STA $D20F
			  LDA #$7F		; enable selftest rom
			  STA $D301
			  JMP $517B	   ; jump to OS restore code

(Sorry for layout, I simply do not know what is going wrong with the layout sigh; spent almost an hour to fix it, which is still not right... sigh)

Summary of question:


The code above works 100%... except for one thing. As soon as the atari is switched on (from real power off) the keyboard is not read out correct. How to fix this easily... I do not have a lot room :S

Thanks
Marius

hi!

On my iPhone I use the latest version of Tapatalk. Unfortunately it happens a lot that I can not read a topic. Tapatalk opens the topic, but does not show any txt on the screen.

Tapatalk is an app which let me visit/use this forum.

It would be nice if it worked perfect.

Is it a problem with tapatalk or with atariage?

Greetz
M.

Anyone here using tapatalk on iPhone?

It happens a lot that when I want to read a topic that there is no content shown in tapatalk. Is this known? And is there a solution?