Post - Forum - Plus/4 World



	Home Search Games Tapes Covers Cheats Maps Software New Stuff Hall Of Fame HVTC Game Endings Solutions Remakes Publications Magazines Effects Top List Members Groups Features Plus/4 Encyclopedia Hardware Tools Options Forum Home Search Games Tapes Covers Cheats Maps Software New Stuff Hall Of Fame HVTC Game Endings Solutions Remakes Publications Magazines Effects Top List Members Groups Features Plus/4 Encyclopedia Hardware Tools Options Forum	Login

Forum Help

Post Your Message

Previous Messages

Posted By

KiCHY
on 2010-11-14
17:40:58

Re: 1541 unexpected behaviour

Finally, I found the problem. My code used $0A address in zeropage which belongs to I/O functions of kernal. So yes, the kernal routines really went crazy

Posted By

SVS
on 2010-11-07
14:15:11

Re: 1541 unexpected behaviour

It sounds like you used $FFCF Kernal routine and it went crazy...

Posted By

KiCHY
on 2010-11-07
06:35:18

1541 unexpected behaviour

Hi There,

I'm in trouble with reading blocks from disk with 1541. I try to read a full block into memory with a similar command: "u1:02 0 03 00". At another stage of my program I try to read drive status (answer should be "00, ok,00,00"). In most cases everything works fine, but sometimes something goes wrong.
In response of reading drive state I get only a $0D (return) character. In block reading my loop reads lots of $0D characters.
I experienced that when I get $0D for drive state, and I repeat reading drive state, I get the correct "00, ok,00,00" result. But it is an ugly hack to solve the problem.
Did anyone of you meet this behaviour and found a correct solution?

Cheers,
K.