2k intro boot... - Page 2

W4r3DeV1L · 25 September 2019, 23:48

Quote:

Originally Posted by ross

Did you use the version I posted? (post #16)
Notice the commented code.

I assure you that it works.

Just assembled your text and wrote it to a blank adf but it doesn't boot ... dunno why ... if you say that....

ross · 25 September 2019, 23:49

Quote:

Originally Posted by D4Ni3L3

Just assembled your text and wrote it to a blank adf but it doesn't boot ... dunno why ... if you say that....

Upload your ADF to the Zone.

EDIT:
or attach here, zipped is really tiny

ross · 26 September 2019, 00:00

Nothing on disk, so you fail before the CC write
(which, however, is calculated and written properly

).

Sure your WS is working?

But now

W4r3DeV1L · 26 September 2019, 00:02

Quote:

Originally Posted by ross

Nothing on disk, so you fail before the CC write.

Sure your WS is working?

But now

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!

redblade · 26 September 2019, 00:20

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.

W4r3DeV1L · 26 September 2019, 00:56

Quote:

Originally Posted by redblade

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.

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....

mr.spiv · 26 September 2019, 02:42

Quote:

Originally Posted by ross

Booblock itself is only 1KB so you have to load the 2 additional sectors.
I have no idea if there is a special tool, but if you want I will do it for you

If the disk is used for anything else than just to show off the 2KB boot you want to reserve space for the additional 2 sectors from the disk bitmap. Otherwise the chances are that some random file overwrites those sectors not in 2 reserved sectors for the bootblock. DiskMon or equivalent tool allows bitmap manipulation with a easy to use GUI.

W4r3DeV1L · 26 September 2019, 20:29

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?

ross · 26 September 2019, 20:45

Quote:

Originally Posted by D4Ni3L3

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....

What are your conclusions about all this?

That WS for some reason do not works for you

W4r3DeV1L · 26 September 2019, 20:57

Quote:

Originally Posted by ross

That WS for some reason do not works for you

what's left over for me ross?

ross · 26 September 2019, 21:08

Quote:

Originally Posted by D4Ni3L3

what's left over for me ross?

Describe your situation exactly.
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?

W4r3DeV1L · 26 September 2019, 21:42

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...

heavy · 26 September 2019, 21:52

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

ross · 26 September 2019, 21:57

Quote:

Originally Posted by D4Ni3L3

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

I'm on very different setup: ASM-One v1.49RC2 (require KS>2), KS3.1.

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

W4r3DeV1L · 26 September 2019, 22:10

Quote:

Originally Posted by ross

I'm on very different setup: ASM-One v1.49RC2 (require KS>2), KS3.1.

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

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.....

W4r3DeV1L · 26 September 2019, 23:47

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?

W4r3DeV1L · 27 September 2019, 00:06

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....

DrCinicus · 27 September 2019, 00:07

Quote:

Originally Posted by D4Ni3L3

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...

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.

W4r3DeV1L · 27 September 2019, 00:16

Quote:

Originally Posted by DrCinicus

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.

in Fast ram...

DrCinicus · 27 September 2019, 09:46

Ok, there are two solution:
- use a KS 2.0+ (just to assembleand disk writing)
- assemble the program in chip-ram

26 September 2019, 20:29	#28
W4r3DeV1L Registered User Join Date: Feb 2008 Location: somewhere Age: 52 Posts: 326	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? Attached Thumbnails Last edited by W4r3DeV1L; 26 September 2019 at 20:52.

26 September 2019, 21:42	#32
W4r3DeV1L Registered User Join Date: Feb 2008 Location: somewhere Age: 52 Posts: 326	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... Last edited by W4r3DeV1L; 26 September 2019 at 21:50.

26 September 2019, 23:47	#36
W4r3DeV1L Registered User Join Date: Feb 2008 Location: somewhere Age: 52 Posts: 326	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? Attached Thumbnails

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Intro ;)	diskers	Member Introductions	2	19 September 2012 14:29
Intro	tomse	Member Introductions	7	04 July 2010 09:40
no-intro?	Marcuz	project.TOSEC (amiga only)	10	25 August 2008 22:30
What's the intro?	xtc	request.Demos	4	14 February 2008 09:47
Can you name this intro?!	Quickbeam	Retrogaming General Discussion	3	17 May 2003 10:54

26 September 2019, 00:00	#23
ross Defendit numerus Join Date: Mar 2017 Location: Crossing the Rubicon Age: 53 Posts: 4,476	Nothing on disk, so you fail before the CC write (which, however, is calculated and written properly ). Sure your WS is working? But now

26 September 2019, 21:52	#33
heavy noodle Join Date: Jun 2007 Location: europe Posts: 247	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

27 September 2019, 00:06	#37
W4r3DeV1L Registered User Join Date: Feb 2008 Location: somewhere Age: 52 Posts: 326	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....

27 September 2019, 09:46	#40
DrCinicus Registered User Join Date: Oct 2008 Location: Assemini/Italy Age: 51 Posts: 23	Ok, there are two solution: - use a KS 2.0+ (just to assembleand disk writing) - assemble the program in chip-ram

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)