![]() |
Quote:
Just assembled your text and wrote it to a blank adf but it doesn't boot ... dunno why ... if you say that.... |
Quote:
EDIT: or attach here, zipped is really tiny :) |
Nothing on disk, so you fail before the CC write
(which, however, is calculated and written properly ;)). Sure your WS is working? But now :sleep |
Quote:
I just entered WS.... and did everything the way you told me.... if u are asleep now ... don't worry about .... we can sort it out tomorrow I guess ... many thanks buddy.... goodnite! |
2 Attachment(s)
Did you try that bootblock.s from the archive? It's already set up and displays some text. It is also set up so that you can test the code under AsmOne before writing to the bootblock.
|
Quote:
many thanks redblade ... the code you have attached works fine when I assemble and start by the ASM-One but I don't know why ... once again ... the disk won't boot after writing the bootblock ... ross told me that maybe something goes wrong when I write the bootblock to the disk ... I'm out of my depth here ... hope we can sort it out.... |
Quote:
|
2 Attachment(s)
Today I tried to do not use a custom disk created at the moment for this purpose ...
So, got an .adf file as DOpus v4, I performed the test of writing the assembled source as revised by ross on its boot block. I made, also, a screen capture, for the occasion, of the .adf as it appears in WinUAE before and after launching the WS command. This was done with the purpose of examine what is going on the disk and if the WS procedure makes his job correctly.... Starting the disk it, once again, it do not want to listen to boot... What are your conclusions about all this? |
Quote:
|
Quote:
what's left over for me ross? :guru |
Quote:
What version of ASM-One do you use? What happens when you type WS? Do you see drive activity after entering the parameters required by WS? |
ASM-One V1.20, KS/WB 1.x version version downloaded from TFA site, I use WinUAE with KS1.3...
when I type WS,RAM PRT>bb, DISK PTR>0, LENGTH>2, CC and I see activity on disk... |
try with another program (megamon,boot master...)
if same problem, it's winuae : don't use turbo mode on df0: with megamon for example : open megamon, load the file, compute checksum and write the boot : L boot.bin 40000 b 40000 >b 40000 0 2 if exe file, skip hunk : boot start at $40020 |
Quote:
You shoud see activity on disk also after inserting "2". WS give you the prompt: "RAM PRT>", you respond with "bb". Then ASM-One prompt "DISK PTR>", you "0"; then prompt "DISK PTR>", you "2"; disk activity. You "CC", disk activity. I can't help you more than that :D |
Quote:
Now I am using ASM-One V1.48 and something new has happening... because after WS, RAM PRT, DISK PRT examining the bootblock I see something changed but it left for me to launch correctly the CC because I have Illegal operator..... |
1 Attachment(s)
Now I should have your setup ASM-One v1.49RC2 ... see what happens?
Will some of you tell me what's going on? Am I cursed maybe? |
End of the story... I now can assume that what caused all this mess was a feeble control of the disk writing process ... All was sorted out just starting WinUAE as administrator...
Thanks to any of you for helping me.... |
Quote:
Did you assemble the program in chip or fast ram? Because, IIRC, trackdisk.device in KS 1.3 can write/read data only from chip ram. |
Quote:
in Fast ram... |
Ok, there are two solution:
- use a KS 2.0+ (just to assembleand disk writing) - assemble the program in chip-ram |
All times are GMT +2. The time now is 12:00. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2019, vBulletin Solutions Inc.