AmigaGuide: Can I launch a WHDLoad game from it?

[mihcael]

Originally Posted by Zetr0

@mihcael

thinking about it I do doubt it...

anyone know which ones are required for amigaguide / multiview?

amigaguide.library for a start

Best to find out using snoopdos if you can, i dont appear to have it installed ATM.

[Konrad]

If this doesn't work out try running IPrefs before AmigaGuide/MultiView

[Zetr0]

I really appreciate your help guys!

I have been soldiering on and even with adding the newer amigaguide.library (ver 45.x) to the ClassicWB68k install there is still the problem of it nor parsing the Macro code.

I tried running IPREFs and still no difference was made

so here is a very meager result from SnoopDos


Here is the same from CWOS39


and here is it running on CWOS39


I wonder if the 68k one is limited on string length of the Macro? that being said though surly with the same program / libraries and even the same multiview this limmitation wouldn't exists would it?

man this is a weird one!

[killergorilla]

Just a quick mention...

Your macro won't work for all my whdload games as some of them do not have slave names which match the foldername.

Games with multiple icons/multiple slaves for example.

Just thought I'd let you know now

[Zetr0]

Thanks for the heads up KG,

I am hoping those "some are a few" lol - In the worst case my friend, I can work around that with a kludge on some entries - yeah its a lot of manual work, but the users are worth it - but I am a lazy coder so I will just write another macro that allows me to specify the whdload slave component separately =)

At the moment the Macro isn't working in a Base CLI and or ClassicWB68k environment - this is its primary purpose - I have even tried beating the datatypes into submission - still no joy and no buttons being rendered.

I know that Macro's / buttons are working as the text appears formatted as such and buttons work when hard coded - however this macro is just not working.. perhaps some string-length tests....

worse case scenario is back to the REXX =(

you now it would be so much easier if the PRELOAD option could be switched globally, to something like - AUTO (comply with icon) or OFF - a forced OFF mode for much lesser 2MB machines.

well gonna grab a coffee and some breakfast

[TCD]

Originally Posted by Zetr0

you now it would be so much easier if the PRELOAD option could be switched globally, to something like - AUTO (comply with icon) or OFF - a forced OFF mode for much lesser 2MB machines.

Hmm, have you read Wepl's answer to your request : http://eab.abime.net/showthread.php?p=729574#post729574 ?

[Zetr0]

in fact I just did..

my experience, is contrary to what he states.... I am very confused to Wepl's statement, should there be no difference between PRELOAD and non-PRELOAD, they why even make the option in for it in the first place?

why is it - that by not using PRELOAD games that didn't load before now do - perhaps I confused the question?

Either way its a chewbacca living on Endor moment

[ppill]

The way I understand it (Welp's statement) is that PRELOAD works where there's enough memory and doesn't when there isn't. There's no need to change it if the game supports it because it will work one way or the other.

But again I think that's not how it works. I had games refuse to load with preload, but worked fine without it.

[TCD]

@Zetr0
Guess that extra info will be useful for Wepl to have a look. Maybe you even have an example or two for him to check?

[Zetr0]

@TCD

yep - even uploaded some pics =)

@ppill

I find that within a 2MB (chip only environment) any WHDLoad Game that is essentially 2 disks or more - bombs out with the PRELOAD option enabled - generally complaining it cannot find Disk.1

most (not all) 1 disk games seem to work however.

[Zetr0]

I have discovered the issues with the PRELOAD not working as it should - the

DOS 205# error
Disk.1 not found

Is a bug in WHDLoad 16.9, apparently WHDLoad 17.0 beta doesn't have this bug, so I shall be testing this out later tonight.

[Zetr0]

Update

WHDLoad17.0 beta rox! and works as intended, small games seem to preload into a 2MB, where as larger games didn't preload (like ProjectX and Stardust)

So we have this sorted - Smart Preloading! great stuff (thanks to Wepl and the Team)


Now, I have discovered that the problem with the AmigaGuide is when the program interprets its script - specifically when dealing the " \ " (backslash symbol) within a MACRO.

say I use it in general text like including quotes

it was a happy day that \"bliggle\" was enjoying

This is parsed fine however even when created as a MACRO

@MACRO Heading "@\"{b}{fg shine}$1@{fg text}@{ub}\""

@{Heading "Behold the program title!"}

this prints on the page

"Behold the program title!"

so the " \" " can be Parsed in a Macro - however

when I try to use this with a SYSTEM command

@MACRO Game "@{\"$1\" SYSTEM \"wbrun a-games:p/$1/$1\"}"

@{Game "ProjectX"}

Nothing is rendered - infact the MACRO is ignored..

with exception of when you run the script under ClassicWorkbench 3.9 (boingBag 1&2)

if you run this amigaguide script under the following ClassicWorkbench distro's-

ClassicWorkbench 68k - no buttons are generated
ClassicWorkbench Lite - no buttons are generated
ClassicWorkbench FULL - malformed button no text - no link
ClassicWorkbench ADV - no buttons are generated
ClassicWorkbench 3.5 - malformed buttons
ClassicWorkbench 3.9 - malformed buttons

ClassicWorkbench 3.9 + Boing bag 1 & 2 - all buttons formed and executes system commands

I believe I have copied all the files needed for AmigaGuide, including
Devs:datatypes/amigaguide.datatype
Libs:amigaguide.library
multiview
amigaguide

and still there is a parse error in the script =(

Unfortunately I am at wits end as to figure out why and what makes CWOS3.9+BB1&2 work but none of the others =(