Amiga.org
Amiga News and Community Announcements => Amiga News and Community Announcements => Topic started by: Cosmos on February 24, 2011, 04:08:41 PM
-
New version of the exec.library v45.24 : http://eab.abime.net/showthread.php?t=57950
The exec.library was written in asm since the beginning. So, it's hard to get
a real speedup. Anyway, many bytes can be saved using some 68k tricks.
All the code are always reworked to use all the features of the 68060 with a
full 68000 compatibility. The new 020+ opcodes are used very rarely, so
special _020, _030, _040 and/or _060 functions are created when needed.
This library is now a true jewel of coding. Enjoy !
-
New version of the exec.library v45.24 : http://eab.abime.net/showthread.php?t=57950
The exec.library was written in asm since the beginning. So, it's hard to get
a real speedup. Anyway, many bytes can be saved using some 68k tricks.
All the code are always reworked to use all the features of the 68060 with a
full 68000 compatibility. The new 020+ opcodes are used very rarely, so
special _020, _030, _040 and/or _060 functions are created when needed.
This library is now a true jewel of coding. Enjoy !
I'll wait for Piru's opinion first. ;)
-
If I were to try this, would I put it before or after "cpu fastrom" in startup-sequence?
-
Like this in your StartUp-Sequence :
Loadresident force exec.library_45.24
SetPatch Quiet
Cpu fastrom
-
New version of the exec.library v45.24 : http://eab.abime.net/showthread.php?t=57950
The exec.library was written in asm since the beginning. So, it's hard to get
a real speedup. Anyway, many bytes can be saved using some 68k tricks.
All the code are always reworked to use all the features of the 68060 with a
full 68000 compatibility. The new 020+ opcodes are used very rarely, so
special _020, _030, _040 and/or _060 functions are created when needed.
This library is now a true jewel of coding. Enjoy !
@Cosmos
Commodore Amiga can host your fully patched Kickstart ROM on our Iranian servers if you want?
-
Are your servers now protected from the Stuxnet virus or is there likely to be a lot of downtime?
-
New version of the exec.library v45.24 : http://eab.abime.net/showthread.php?t=57950
The exec.library was written in asm since the beginning. So, it's hard to get
a real speedup. Anyway, many bytes can be saved using some 68k tricks.
All the code are always reworked to use all the features of the 68060 with a
full 68000 compatibility. The new 020+ opcodes are used very rarely, so
special _020, _030, _040 and/or _060 functions are created when needed.
This library is now a true jewel of coding. Enjoy !
Thanks for this effort Cosmos.
What I would personally like to see are updated libraries that are CPU targeted without any support for 68000 (eg remove 68000 compatibility completely).
Either come up with 2 library versions (020/030) and (040/060) or one single library (020/030 with 040/060 functions where needed).
-
What I would personally like to see are updated libraries that are CPU targeted without any support for 68000 (eg remove 68000 compatibility completely).
This is an interesting idea, although it may not significantly increase performance, depending on whether processor-specific routines are branched to each time the function is called or whether there's simply a jump table that gets set to the appropriate routines at load time.
-
>that are CPU targeted without any support for 68000 (eg remove 68000 compatibility completely)
Yes, of course, it's planned !
But not for now. I want an unified Kickstart ready for 68000+ with all patchs included. After that, we will see...
-
>that are CPU targeted without any support for 68000 (eg remove 68000 compatibility completely)
Yes, of course, it's planned !
But not for now. I want an unified Kickstart ready for 68000+ with all patchs included. After that, we will see...
Yes its always nice to have the option of running your new exec.library on our minimigs and A500s with harddrives.
-
Thank you Cosmos, I'll try to install in my WinUAE.
-
Thank you Cosmos for the Trillions of CPU cycles you will save us all!
I will take time to see if it has any wierd bugs, but I'm sure it will make Carl Sassenrath smile. I hope you will support NatAmis 68050,70, etc. feature/instruction sets too.
Thank you very much!!!
(...I just hope it dosen't interfere with running Mindguard...)
-
>for the Trillions of CPU cycles you will save us all!
Yes, 68k have low Mhz, so each cycles saved is good for us !
>I'm sure it will make Carl Sassenrath smile
Smile ?? He will cry when he'll see my unified autovec !!
-
Cosmos,
Quoted from Aminet:
"Autovec unified and 9 times faster (68 bytes now instead of 612 bytes)"
Wow!
I guess I'll need to strip out Decigel from my old startup-sequences.
If VBR in chipmem is 4X slower, it's still faster with your Exec!
HW wise: I thought the most responsive or _crispest_ Amiga's I(we)'ve seen have 32 bit zero waitstate memory located @ CZero (even if only 256K) even if they have megabytes elsewhere.
This was because of Kickstart adding that memory in so early (1986+ CSA accellerators) and Execbase being located there I thought.
With regular kickstarts, and your new Exec, will C0 just contain a jump instruction to where your Exec.device is placed from arguments from its launch?
I'm feeling rusty now, I need to RTFM more to understand. This is AWESOMSE!
You guys are so fucking smart!
-
Like this in your StartUp-Sequence :
Loadresident force exec.library_45.24
SetPatch Quiet
Cpu fastrom
I couldn't get this to work. My A4000 went into an endless reboot cycle with a yellow screen.
I fixed it though by using this:
LoadModule Libs:exec.library_45.24 NOREBOOT
StepPatch SKIPROMMODULES scsi.device, exec.library >NIL:
Worked a treat after that.
Weed
-
Yes its always nice to have the option of running your new exec.library on our minimigs and A500s with harddrives.
Also, some users may want to have a dual boot OS3.1/3.9 system. Since the 68020+ opcodes are created and used only for certain functions the only benefit a 68020+ exec.library is saving a few more bytes of code.
... and Cosmos would have a pretty good idea of how many bytes could actually be saved.
-
New version of the exec.library v45.24 : http://eab.abime.net/showthread.php?t=57950
The exec.library was written in asm since the beginning. So, it's hard to get
a real speedup. Anyway, many bytes can be saved using some 68k tricks.
All the code are always reworked to use all the features of the 68060 with a
full 68000 compatibility. The new 020+ opcodes are used very rarely, so
special _020, _030, _040 and/or _060 functions are created when needed.
This library is now a true jewel of coding. Enjoy !
How the library helps 68k emulation (or not) on MOS, OS4, UAE / WinUAE?
-
@vox
Other than if you use it in your emulated OS3 environment under UAE, it won't make a difference. MOS and OS4 both have newer versions of Exec written for PPC, and depend on a lot of things that are very different from OS3. Even if you could use the OS3 version, it would require emulation, and would end up slower than the native one.
It might make a difference in UAE like I said, but with buckets of CPU power available for a modern PC WinUAE setup, it's probably not that noticeable... Correct me if I'm wrong, but I see this as an improvement for a "real" 68k Amiga only...
-
After installing the new exec.library the correct way, the exec.library isn't resident.
How come the new exec.library doesn't show up in the SysInfo library list
(only the old v40.10 from ROM 3.1)?
I've tried it with several Amiga models en set-ups.
-
It works just fine in mine with custom kickstart 3.9 ROM including Cosmos Exec.library (loaded via MapROM of A630).
(Soz for the lame screenshot, but a.org accepts only 19k files - and I was bored to upload to other host atm) :)
-
It works just fine in mine with custom kickstart 3.9 ROM including Cosmos Exec.library (loaded via MapROM of A630).
Does it show up in SysInfo?
EDIT:
Never mind. You attached SysInfo pic.
-
@ mfilos
Which commandline you use in the startup-sequence? I can't get it to work
with both ROM 3.1 & 3.9. :confused:
-
Try with 'LoadResident' (in the RemApollo archive on Aminet)
-
@ mfilos
Which commandline you use in the startup-sequence? I can't get it to work
with both ROM 3.1 & 3.9. :confused:
I don't use a command to load the modules mate.
I made a custom kickstart 3.9 ROM that includes all the patches from BB3+BB4 (Cosmos exec included along with graphics.library from PeterK).
Then... I only have to kick the new ROM and voila.
Try LoadResident as Cosmos said, I remember it worked just fine pre custom kickstarts on mine.
-
I tried LoadResident, but it keeps saying that exec.library already excist.
Then I put the "REMOVE" command; "LoadResident exec.library REMOVE",
but then it's telling me that the resident list is empty?
I've tried this all in WinUAE with OS3.9.
Now, the LoadModule command works, but like I stated before; I doesn't
stay resident, only the old 40.10 exec.
-
Hmmm, do you run LoadResident before SetPatch or after?
Also what is your SetPatch declaration along with the other possible LoadModule declarations?
-
Before SetPatch:
C:LoadModule L:Ram-Handler L:Shell-seg DEVS:console.device DEVS:scsi.device LIBS:exec.library LIBS:graphics.library DEVS:trackdisk.device DEVS:misc.resource DEVS:ramlib QUIET
C:SetPatch SKIPROMMODULES ram-handler,shell,console.device,scsi.device,exec.library,graphics.library,trackdisk.device,misc.resource,ramlib QUIET
-
Put in the LoadModule declaration the exec.library first of all and then the rest.
Also keep it as first line in S-S just to test it out.
I also saw that there are some spaces in SetPatch line (in exec.library, misc.resource). Is it as you have it or it's a copy-paste mistake?
-
I don't use a command to load the modules mate.
I made a custom kickstart 3.9 ROM that includes all the patches from BB3+BB4 (Cosmos exec included along with graphics.library from PeterK).
Then... I only have to kick the new ROM and voila.
Try LoadResident as Cosmos said, I remember it worked just fine pre custom kickstarts on mine.
Is it relatively straight-forward to create a custom rom image?
I've got a Deneb to put in my A4000 so I want to make an up to date rom with Cosmos and Peter's new libs too.
-
Put in the LoadModule declaration the exec.library first of all and then the rest. Also keep it as first line in S-S just to test it out.
I've put it first in line, no change.
I also saw that there are some spaces in SetPatch line (in exec.library, misc.resource). Is it as you have it or it's a copy-paste mistake?
It was a copy paste mistake, sorry for that.
I also tried it with my A1200/060/50Mhz/OS3.1, A1200/030/50Mhz/OS3.1,
same result... No new exec.library showing up in SysInfo.
Maybe the whole thing has to do with you having a home made KickROM?
Are there any others here who's having the same problems?
-
What are your accelerator boards ? Apollo ? Blizzard ?
-
What are your accelerator boards ? Apollo ? Blizzard ?
Apollo 1260 & Blizzard 1230.
-
Is it relatively straight-forward to create a custom rom image?
I've got a Deneb to put in my A4000 so I want to make an up to date rom with Cosmos and Peter's new libs too.
I wrote an how-to guide some time ago about how to create on your own a Custom 1MB Kickstart 3.9 ROM image:
http://www.amibay.com/showthread.php?t=11935
For Deneb is even easier since you only need to load the Modules into Flash ROM and you're set :)
@Amidude
Mate, I can't reproduce the issue since on my A630 I have a custom rom kicked via MapROM, and on my A1200PPC I wrote a custom eprom as well :(
It's been a while since I messed with LoadModule or LoadResident
-
I wrote an how-to guide some time ago about how to create on your own a Custom 1MB Kickstart 3.9 ROM image:
http://www.amibay.com/showthread.php?t=11935
For Deneb is even easier since you only need to load the Modules into Flash ROM and you're set :)
Thanks, bookmarked for the weekend! :)
-
@AmiDude
Try with 'LoadModule Reboot Quiet'
And with only the exec.library !
-
@AmiDude
Try with 'LoadModule Reboot Quiet'
And with only the exec.library !
Doesn't work; With WinUAE the screen goes yellow and comes
in an endless rebooting cycle.
With A1200 there's no change; Still no new exec.library in SysInfo.
:confused:
-
I get an email from PeterK :
Version >Nil: exec.library 45 REVISION 24
If WARN
LoadResident >Nil: Libs:exec.library
EndIf
-
I get an email from PeterK :
Version >Nil: exec.library 45 REVISION 24
If WARN
LoadResident >Nil: Libs:exec.library
EndIf
Doesn't work... I'm tired of trying all kinds off possibilities. I guess this new
exec.library is only for handmade Kick-ROMs or something... :(
On the other hand, all other new librarys and devices work OK.
-
I tried under WinUAE LoadModule and LoadResident with the exec.library 45.20 (BB2) on a Kickstart 3.1 and it's not working too...
-
@AmiDude
Uploaded a new AmigaOS ROM Update with only the exec.library 45.24 specially for you here : http://eab.abime.net/showpost.php?p=743785&postcount=29
-
Would this be ok on a 3.1 system? Would it give much benefit?
-
The v45.20 (BB2) not support the 060. Will be fixed in the v45.25 !
The real benefit is coming soon : I'm working on... Colossal task, a bit of patience please...
-
@AmiDude
Uploaded a new AmigaOS ROM Update with only the exec.library 45.24 specially for you here : http://eab.abime.net/showpost.php?p=743785&postcount=29
Thanks Cosmos!:) I'll give it a try and let you know A.S.A.P.
-
Well, it works... It's now recognized by the system, but now the other
new libraries and devices aren't recognized? Very strange... :huh:
-
New version of the exec.library v45.24 : http://eab.abime.net/showthread.php?t=57950
The exec.library was written in asm since the beginning. So, it's hard to get
a real speedup. Anyway, many bytes can be saved using some 68k tricks.
All the code are always reworked to use all the features of the 68060 with a
full 68000 compatibility. The new 020+ opcodes are used very rarely, so
special _020, _030, _040 and/or _060 functions are created when needed.
This library is now a true jewel of coding. Enjoy !
I tried this on my CSPPC/060 & ALGOR.
I replaced the exec 45.20 module with Exec 45.24, and I got a yellow screen... so I skiped the ALGOR EPROM, and reinstalled the 45.20 :-(
-
I too did get a yellow screen with 45.24, so I changed it with Piru's 44.1 which runs like a Beetle.
-
Hum, I don't have any Algor at home...
Where to find some technical docs about this card ??
-
http://www.e3b.de/
There is a support section, for further technical details regarding the HW, you should contact them I suppose.
About the flashing EPROM SW : http://www.platon42.de/files/usb/Luciferin.readme
-
The upcoming v45.25 is already working with the Deneb (and on the Algor too, I hope) !
A cool surprise with this new version... mfilos will loooooove it...
-
The upcoming v45.25 is already working with the Deneb (and on the Algor too, I hope) !
A cool surprise with this new version... mfilos will loooooove it...
Do you have an ETA for v45.25?
-
What's ETA ??
-
http://en.wikipedia.org/wiki/ETA_(disambiguation)
In this case probably:
http://en.wikipedia.org/wiki/Estimated_time_of_arrival