Who's Online |
56 user(s) are online ( 38 user(s) are browsing Forums)
Members: 0
Guests: 56
more...
|
|
Headlines |
-
amissl-sdk.lha - development/misc
Mar 23, 2023
-
unext.lha - game/platform
Mar 23, 2023
-
mce.lha - game/utility
Mar 23, 2023
-
amissl.lha - library/misc
Mar 23, 2023
-
nm2mw.lha - utility/misc
Mar 23, 2023
-
vamp.lha - video/play
Mar 23, 2023
-
amigemini.lha - network/browser
Mar 20, 2023
-
petsciirobots.lha - game/action
Mar 19, 2023
-
terri-fried.lha - game/misc
Mar 19, 2023
-
seq.lha - audio/misc
Mar 18, 2023
|
|
|
|
Re: Ramdisk failing on X5000
|
|
Just can't stay away 
|
@colinw
Sorry, my bad. I don't have access to it. Let's just end the discussion here.
|
|
|
|
Re: Ramdisk failing on X5000
|
|
Just can't stay away 
|
@abalaban @colinw
Versions :
- dos.library.kmod.debug 54.121 - kernel.debug 54.56 - ram-handler.kmod 54.26
I don't have a serial hook up, so I can't see serial output during boot.
|
|
|
|
Re: New verson of CLiB2 from Andrea (afxgroup)
|
|
Just can't stay away 
|
@afxgroup Quote: while they are unloaded with NO DEBUG.... That makes no sense. Have your checked the debug output of elf.library to see, why they fail to load?
|
|
|
|
Re: New verson of CLiB2 from Andrea (afxgroup)
|
|
Just can't stay away 
|
@afxgroup
Just a thought : The file constructor, that you are talking about - is it instantiated inside libc.so or in the main executable?
|
|
|
|
Re: New verson of CLiB2 from Andrea (afxgroup)
|
|
Just can't stay away 
|
@afxgroup How is the file constructor instantiated? Can you post the code here? Quote: Of course I can't debug it because no serial output.. Sashimi??
|
|
|
|
Re: New verson of CLiB2 from Andrea (afxgroup)
|
|
Just can't stay away 
|
@afxgroup
Sure. I took about 1 1/2 year (one-and-a-half year) to solve the pointer equality issue. Maybe you can do it a little faster? ;-D
I am here to support, if you pinpoint a problem with the binary loader.
|
|
|
|
Re: New verson of CLiB2 from Andrea (afxgroup)
|
|
Just can't stay away 
|
@afxgroup
Maybe an -fPIC issue? I am having trouble picturing the problem, when I don't know, what your code looks like.
The .ctors/.dtors code is quite solid now, so I doubt, that the problem is here. There could be some strange link problem, that we don't know about yet.
|
|
|
|
Re: New verson of CLiB2 from Andrea (afxgroup)
|
|
Just can't stay away 
|
@afxgroup Quote: ... while if I disable debug I have a DSI ... Well, obviously something is responsible for either setting the value, or you have overlooked something? If you set it to zero (0) just before it is used, what happens then? EDIT : Since it works (...) with static link, then perhaps it is a constructor issue, that we overlooked? Are you using still .ctors, or have you progressed to .init_array? Remember, there is also .pre_init_array, and this is not implemented. Neither is .init_array for the main executable.
|
|
|
|
Re: Ramdisk failing on X5000
|
|
Just can't stay away 
|
@colinw
Hi Colin, thanks for the assistence!
I am trying to upgrade ram-handler.kmod to version 54.26 (latest).
This one pops up requesters at boot. First 'Unknown volume RAM:', and then when pressing 'Mount', it says 'Failed to load DEVS:mountlist'.
I can see, that there is indeed no file called DEVS:mountlist.
Also, I can see in DEVS:DOSDrivers/, that there is no entry for RAM.
Is this a manual assignment now? I am not sure how to correctly create the entry for RAM.
Also I am curious : What is the ramdrive.device.kmod for ?
EDIT : I can boot from installation CD, and then the ramdisk seems to be fine.
|
|
|
|
Ramdisk failing on X5000
|
Posted on: 2/24 16:53
#10
|
Just can't stay away 
|
Hey guys,
I have huge problems with my drives at the moment. At first I thought it must be because of a blow on the machine about 1/2 year ago.
BUT now the ramdisk is starting to fail. I cannot read simple executables from it.
SO I remembered, that I updgraded dos.library and ramlib.kmod some weeks ago.
Does anyone of the betatesters know, if there are issues with versions of those two entities?
I think it is a better bet than both my usb stick and harddrive going bust at the same time. The machine boots fine 19 out of 20 times, and the last time I assume it is an issue with my beta elf.library.
|
|
|
|
Re: Qt 6 progress
|
Posted on: 2/21 12:14
#11
|
Just can't stay away 
|
@afxgroup
Yes. I have a music gig tomorrow, so I need to spend a little time preparing. But Thursday I should be around again.
|
|
|
|
Re: Qt 6 progress
|
Posted on: 2/21 11:47
#12
|
Just can't stay away 
|
@elfpipe And we have a winner : Qt6 Network http
|
|
|
|
Re: Qt 6 progress
|
Posted on: 2/20 18:10
#13
|
Just can't stay away 
|
@elfpipe I found this snippet in Qt4 : Quote: //ISocket->SocketBaseTags( // SBTM_SETVAL(SBTC_CAN_SHARE_LIBRARY_BASES),TRUE, // TAG_END);
Is this something to use?
|
|
|
|
Re: Qt 6 progress
|
Posted on: 2/20 17:36
#14
|
Just can't stay away 
|
@afxgroup
Nopy. I can't even get that far (ISocket->connect comes before handshake). I am suspecting, that it is an issue with threads.
EDIT : I remember there being an issue with sharing sockfds across threads in Qt4. I thought, the solution would be to use bsdsocket.library instead of newlib calls, but maybe even that is not enough.
Do we have a network api that allows for sharing socket descriptors across threads?
|
|
|
|
Re: Qt 6 progress
|
Posted on: 2/20 16:32
#15
|
Just can't stay away 
|
@afxgroup
I think I found the right place to put them.
BUT no matter what server I try and connect to, the call to
ISocket->connect()
fails. I get a working ip address with QHostInfo(), and the port is correct (either 80 or 443).
Is there any good way to test http/https access without having to play with firewalls? I can use the same Qt6 app on my pc, and it gives bonus, but on the amiga all connect calls fail.
EDIT : connect to 127.0.0.1:80 fails, so probably my socket is not sane. Any advice?
|
|
|
|
Re: Qt 6 progress
|
Posted on: 2/20 14:19
#16
|
Just can't stay away 
|
@elfpipe
Ok. Plugins load fine now. I don't know what to do with the certificates. I just want to hook up with google. What shall I do?
|
|
|
|
Re: Qt 6 progress
|
Posted on: 2/20 11:09
#17
|
Just can't stay away 
|
@thread So I got this far. The problem is the macro Q_GLOBAL_STATIC_WITH_ARGS. It seems it is never instantiated : qglobalstatic.h at githubWhen instantiated, it looks like this :
Q_GLOBAL_STATIC_WITH_ARGS(QFactoryLoader, loader,
(QTlsBackend_iid, QStringLiteral("/tls")))
Any cues/clues?
|
|
|
|
Re: Qt 6 progress
|
Posted on: 2/19 17:50
#18
|
Just can't stay away 
|
@Skateman
Looks nice. Is this part of enhancer software or something else?
|
|
|
|
Re: Qt 6 progress
|
Posted on: 2/19 17:49
#19
|
Just can't stay away 
|
@afxgroup
Openssl. And I know, what the problem is (sort of). It is the Qt6 plugin system, that is not functional yet.
|
|
|
|
Re: Qt 6 progress
|
Posted on: 2/19 17:08
#20
|
Just can't stay away 
|
@elfpipe After having stashed my old Qt6 install on the (failing?) hd, I managed to run the test app with a fresh install. I can get as far as this with https download : Quote: qt.network.ssl: No functional TLS backend was found qt.network.ssl: No functional TLS backend was found qt.network.ssl: No TLS backend is available qt.network.ssl: No functional TLS backend was found qt.network.ssl: No functional TLS backend was found qt.network.ssl: No functional TLS backend was found qt.network.ssl: No functional TLS backend was found qt.network.ssl: No TLS backend is available qt.network.ssl: No functional TLS backend was found qt.network.ssl: QSslSocket::connectToHostEncrypted: TLS initialization failed [### ] 0.0 bytes/sec Failed: TLS initialization failed Any cues/clues?
|
|
|
|