@wawa

So far, your prediction has been 100% accurate.

@Ezrec

;)
you can trust me. im almost always right! should recruit as some sort of prophet if there was such a job opportunity available somewhere. have to check adverts from the beloved land.

btw, jason, as far i observed, deadwood has not yet commited owb sources into aros depo, im not sure if this is going to happen or what the agreement with fab is, but apparently nothing prevents 68k compile except perhaps missing dependencies (cairo?). im not insisting as there are other tasks, but could you give it a try?

@franko& other blizzard owners

here what ive just received from toni what concerns aros bootstrap on blizzard :

Quote:

> Done. Now most of the rom is loaded to fast ram, only about 80k remains > in chip ram. (This may also get improved in future) One more update, now ForceFast option forces complete rom image to fast ram. Only works with some boards, for example Blizzard 1260.

what concerns support its best to contact toni wilen via eab.abime.net or mail from wiuae homepage, i dont think he has an account here. zerohero, sorry, nothing personal.

Last edited by wawa on 16-Mar-2012 at 08:26 PM.

@wawa

Quote:

wawa wrote: @franko& other blizzard owners here what ive just received from toni what concerns aros bootstrap on blizzard :

Cheers for that Wawa & Toni...

I take it that the latest "nightly download" is where I can find this version !!!

Going to have to dig them miggies out again and give it another go, hopefully it'll work a bit better this time and leave enough chip ram to actually be able to runs things and put it through it's paces...

_________________

@Franko

wait for tonights nightly. i hve not seen it commited yet.
if you want to check the commit status list you can go here:

http://repo.or.cz/w/AROS.git

@wawa

Cheers Wawa, i'll check it out during the night...

_________________

@all_who_follow_to_icon_rescaling_developing

Is rescaling controled via wandarer options ? I.e. can we set as on os4 lets say "size are: 64x64" and so, every icon will fits to need it size, and they can be and small, and big, just as users wish ? Or currently only functionaly added, not visual prefs for ?

Last edited by kas1e on 16-Mar-2012 at 11:04 PM.

_________________
Join us to improve dopus5!
zerohero's mirror of os4/os3 crosscompiler suites

@kas1e
i dont think this is currently already implemented, the feature is not complete. perhaps you could talk to jason directly about your suggestions or open a dedicated thread on aros exec.

i think icon scaling still isnt acting as it should, but mapping kickstart on blizzard might:
Quote:

3 hours ago twilen ForceFast also puts supervisor stack in fast ram. Also... commit | commitdiff | tree | snapshot (tar.gz zip) 5 hours ago twilen Use AckInterrupt to clear A600/A1200 IDE interrupt... commit | commitdiff | tree | snapshot (tar.gz zip) 5 hours ago twilen Added optional interrupt busdriver interrupt acknowledg... commit | commitdiff | tree | snapshot (tar.gz zip) 16 hours ago twilen ForceFAST option is back. Now forces complete ROM image... commit | commitdiff | tree | snapshot (tar.gz zip) 16 hours ago twilen Added support for non-MEMF_KICK fast ram boards (Mainly... commit | commitdiff | tree | snapshot (tar.gz zip) 16 hours ago twilen More information added to MMU logging. commit | commitdiff | tree | snapshot (tar.gz zip) 16 hours ago twilen Support non-MEMF_KICK fast ram boards (Blizzard A1200... commit | commitdiff | tree | snapshot (tar.gz zip) 16 hours ago twilen Disabled spurious interrupt message. A1200 generated...

sound like blizzard boards should be detected by default, or use forcefast option.

for simplicity sake i copy some of tonis commit comments as how to use the updated bootstrap code on real hardware:
Quote:

Support non-MEMF_KICK fast ram boards (Blizzard A1200 accelerators) in arosbootstrap mode. Requires also updated arosbootstrap version. Most of the rom image loads to fast RAM now. [...] defaults to plain non-MEMF_KICK Fast RAM if available. Replaced with ForceCHIP that forces all modules to chip RAM. Mainly for debugging. Only kernel.resource, exec.library, expansion.library and diag init modules require MEMF_LOCAL RAM (RAM that never disappears during reset), in worst case it means Chip RAM. (Requires only about 80k, will become smaller in future) ForceFAST option is back. Now forces complete ROM image to fast RAM, even if RAM type is not MEMF_LOCAL. (A3000/A4000 mainboard fast is most common MEMF_LOCAL Fast RAM). This only works with some non-autoconfig RAM expansions, one example is Blizzard 1260 Fast RAM. ForceFast also puts supervisor stack in fast ram. Also detects Blizzard A1200 accelerators and automatically enables forcefast for best performance.

would be interesting if someone might check, if the current bootstrap process is still working on a4k series of machines both with oroginal cpu boards and accels. beware that csppc will likely still not be able to boot from its wide scsi. im without any amiga hardware here.

Last edited by wawa on 17-Mar-2012 at 12:47 PM.
Last edited by wawa on 17-Mar-2012 at 12:47 PM.

just in case, anyone was still interested.

aros68k boots now from cybppc.device (wide scsi) on csppc. likely it will also boot on blizzardppc.
the icons are scalable, on my machine it cold boots form power on to full wanderer in less than a minute. so whoever wants to check it out might have look again now.