Those have already been updated and have been with the beta testers for some time.
The first priority was to stop the crashes with an updated timesync.library.
The rest will be released when appropriate, (soon).
Search found 188 matches
- Sun May 09, 2021 11:37 pm
- Forum: General AmigaOS
- Topic: Bug in FE Update 2 Date Command
- Replies: 42
- Views: 3047
- Fri May 07, 2021 11:26 pm
- Forum: General AmigaOS
- Topic: Bug in FE Update 2 Date Command
- Replies: 42
- Views: 3047
Re: Bug in FE Update 2 Date Command
The propper fixes are in the pipeline, please try an avoid mix-n-match type solutions, you usually get more unpleasant old bugs and interactions reappearing when reverting components. This particular problem stems from erroneous documentation where different components expected different things, but...
- Wed Apr 14, 2021 11:52 pm
- Forum: General Developer Support
- Topic: How to free memory allocated by AddTrackable()
- Replies: 8
- Views: 996
Re: How to free memory allocated by AddTrackable()
If you are getting "permit without forbid" messages, then I would assume that you havn't updated all the components that interract with each other in this regard. In the path to multi-core, the kernel has changed the way it handles peeking and poking some execbase fields, and I know the ne...
- Fri Apr 09, 2021 1:51 am
- Forum: General AmigaOS
- Topic: Setting Odyssey as default tool in Deficons? (Solved)
- Replies: 8
- Views: 510
Re: Setting Odyssey as default tool in Deficons? (Solved)
I wrote the URLOpen program specifically with this use in mind, it's mentioned in the URLOpen.doc in the second paragraph. The FILE protocol is the default, you can specify other protocols that you have configured, (as in the URL Prefs tabs) if they are required, by using the PROTOCOL= keyword in th...
- Thu Apr 08, 2021 1:03 am
- Forum: General Developer Support
- Topic: How to free memory allocated by AddTrackable()
- Replies: 8
- Views: 996
Re: How to free memory allocated by AddTrackable()
You can't use this function in application software unless you know what you are doing, and, it must never be used for anything other than what YOU allocate yourself, the rest is done by other system components like DOS. Even then, you need to be carefull that your hook code segment wasn't unloaded ...
- Wed Apr 07, 2021 3:22 am
- Forum: General AmigaOS
- Topic: EXTMem
- Replies: 8
- Views: 572
Re: EXTMem
Extmem works just fine. For the ram-handler, some hardware requires it to be manually enabled, like the SAM440 and classics because they only have limited ram and won't normally be able to run out of virtual memory addresses. SAM460, A1222, X1000, X5000_20 & X5000_40 have it enabled by default, ...
- Sun Apr 04, 2021 11:38 pm
- Forum: General Developer Support
- Topic: Workbench library issue
- Replies: 8
- Views: 710
Re: Workbench library issue
You need to go to the Hyperion website; https://www.hyperion-entertainment.com/ log in with your account credentials, click on "Downloads" and go into the "AmigaOS 4.1 Final Edition" directory and get Update 2. All your problems will likely go away, and you will get the DOS SDK u...
- Sat Mar 27, 2021 11:29 pm
- Forum: General Developer Support
- Topic: Workbench library issue
- Replies: 8
- Views: 710
Re: Workbench library issue
Works for me. !! What editor are you using ? because it sounds like it may have a filehandle left open somehow. Run the "filehandlescan" program, (in SDK:c) passing it the volume name of the partition where you are compiling to, see if anything is left open. All I did here was copy your co...
- Fri Feb 26, 2021 2:24 am
- Forum: General AmigaOS
- Topic: Bug in FE Update 2 Date Command
- Replies: 42
- Views: 3047
Re: Bug in FE Update 2 Date Command
Thankyou for the report, I have managed to reproduce the bug here.
The bug is inside timesync.library V53.8 and earlier.
I have just released the fixed update (53.9) to the beta testers.
The bug is inside timesync.library V53.8 and earlier.
I have just released the fixed update (53.9) to the beta testers.
- Tue Feb 16, 2021 3:24 am
- Forum: General Developer Support
- Topic: Major memory leak in CreateNewProc()
- Replies: 6
- Views: 1317
Re: Major memory leak in CreateNewProc()
"Always always" ! If you have a look at the proto files, you will see why. Not only do they take care of implementing the various switches available to use for the type of program method you require, by pre-declaring various definitions like; __NOLIBBASE__ __NOGLOBALIFACE__ __USE_INLINE__ ...