Closed SteveH-1 closed 3 years ago
@SteveH-1 Thank you so much for your report and I am sorry it doesn't work on X1000, but we will find a way to fix the issue.
Can you please tell me:
Sorry for all these questions but I need to find where the problem is, and your feedback would help me a lot.
@SteveH-1 Can you please have a test on the following binary if it works for you? Just copy the binary to the MediaVault folder replacing the old binary. You might get some output at a shell window but it should start fine.
Hi George, Thanks for the swift reply; I will get back to you shortly with answers to your questions, below, and I will also try the new binary you’ve send me. Regards, Steve
From: George Sokianos @.> Sent: 30 May 2021 19:30 To: walkero-gr/mediavault @.> Cc: Harrison, Steve @.>; Mention @.> Subject: Re: [walkero-gr/mediavault] MediaVault won't launch on X1000 (#9)
@SteveH-1https://hes32-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2fgithub.com%2fSteveH%2d1&umid=b0d27f66-29bb-48df-b7b6-40548da6b8de&auth=768f192bba830b801fed4f40fb360f4d1374fa7c-9038da46487f340778461029ae72e07f9537df4d Thank you so much for your report and I am sorry it doesn't work on X1000, but we will find a way to fix the issue.
Can you please tell me:
Sorry for all these questions but I need to find where the problem is, and your feedback would help me a lot.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://hes32-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2fgithub.com%2fwalkero%2dgr%2fmediavault%2fissues%2f9%23issuecomment%2d851041654&umid=b0d27f66-29bb-48df-b7b6-40548da6b8de&auth=768f192bba830b801fed4f40fb360f4d1374fa7c-760cf126ddbb26e7f9938321d5bb53d2124da9e6, or unsubscribehttps://hes32-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2fgithub.com%2fnotifications%2funsubscribe%2dauth%2fAUJCBLZIHWTN72JOFXIHPNDTQJ72HANCNFSM45ZRLSXA&umid=b0d27f66-29bb-48df-b7b6-40548da6b8de&auth=768f192bba830b801fed4f40fb360f4d1374fa7c-c7bb383fc785581c0dd1dd95c49b385819cee4d1.
Important Notice: Liverpool John Moores University was established as a Higher Education Corporation under section 121 of the Education Reform Act 1988. Further information about Liverpool John Moores University can be found at https://www.ljmu.ac.uk/about-us The information in this email and any attachments is for the sole use of the intended recipient(s). If you are not an intended recipient, or a person responsible for delivering it to an intended recipient, you should delete it from your system immediately without disclosing its contents elsewhere and advise the sender by returning the email or by telephoning a number contained in the body of the email. No responsibility is accepted for loss or damage arising from viruses or changes made to this message after it was sent and the recipient must ensure that the email (and attachments) are virus free. The views contained in this email are those of the author and not necessarily those of Liverpool John Moores University. We will use the personal data information provided by you to respond to your email. For information about how we process personal data and monitor communications please see our Privacy Notice. https://www.ljmu.ac.uk/legal/privacy-and-cookies
I have tried the test binary but I get an output windoww with the following message: "Error::Can't open amisslmaster.library version 4.9 and above" I have v4.2 of amisslmaster.library installed in SYS:Libs I'm using FE Update2 with Enhancer 2 partially installed (no XDock installed). Next, I will try an earlier version.
Can you please update the AmiSSL to latest version 4.9 and try that again? This is necessary because it has a lot of fixes. You can download it from https://www.ibrowse-dev.net/2.5/download.php
Thank you so much.
I've installed v4.9 of AmiSSL but still can't launch MV or the test binary. When I try to launch your test binary, Snoopy reports: "00012 : test_MediaVault : FAIL = GetVar("EXEC_IMPORT_LOCAL",0x5DFEED18,8,0x00000200) [5uS]".
When I try to launch v1.2.0, the Snoopy output is "00014 : MediaVault : FAIL = GetVar("EXEC_IMPORT_LOCAL",0x5DF48D18,8,0x00000200) [4uS]"
Steve
@SteveH-1 Thank you so much for your help. Is it too much to ask you to try the v1.1.1 (https://github.com/walkero-gr/mediavault/releases/tag/v1.1.1) and tell me if it works?
I am afraid v1.1.1 will not load, either; I will email my Snoopy log to you in case that helps (I can't attach it here). I am now wondering if there is an issue with my OS4 installation, as after trying to launch MV, I notice some programs will no longer open (such as Odyssey and MultiEdit). I think I may need to revert some recently-intsalled components and see if that solves the problem.
@SteveH-1 I am not sure if there is an other issue with you setup. I asked at https://www.amigans.net/modules/xforum/viewtopic.php?forum=3&topic_id=8530&post_id=125428#forumpost125428 if anyone uses MediaVault with X1000.
It should work fine, because there is no hardware specific usage at any point in MediaVault. But I am interested to investigate further with your help on the issue.
Do you use any of the Enhancer AKDatatypes?
It would be great if you could prepare a basic AmigaOS 4.1 FE with both updates installed, and the AmiSSL, where you can test MediaVault, so to be sure that nothing else is involved.
Thank you so much for your help.
Hi, I'm waiting on an external HD to replace one which recently died, so I will be able to test on a fresh OS4.1FE install once that arrives. I'm pretty sure I have at least some of the Enhancer datatypes installed, having updated to Enhancer v2.0 a few days ago - I can check later today when I'm back at my Miggy.
Hello @SteveH-1 . Take your time. Yesterday talked with a couple of X1000 owners and they confirmed MediaVault works fine on their machines. So it is not a hardware issue.
Also, I released v1.2.1 with a few bug fixes.
Today, I will try to use on my system the AKDatatypes and anything else that might interfere with MediaVault and see if I can replicate the problem you mention. I will keep you updated.
Thank you for your help to make MediaVault even better.
Hello @SteveH-1 Can you please test this debug version of MediaVault. It is not different from the public version, it just has some output strings that will appear in a shell window. If you don't see the messages, try to run it from a shell.
If you see those messages, can you please send me the full output?
I unpacked the archive to RAM: and tried running it from there; then I renamed the executable to "MediaValut_debug" and copied it to the existing MediaValut drawer on my WORK: partition and ran it fom there. The result was the same in both cases - the following output appeared in a shell:
dbg: before OpenLibs dbg: before open application.library dbg: before open intuition.library dbg: before open utility.library dbg: before open jansson.library dbg: before open amisslmaster.library dbg: before open oo.library
Also (and I don't know if this is relevant) I noticed after trying to run MediaVault (any version), I cannot launch v1.13 of MultiEdit although v1.12 does launch OK. Strange ...
@SteveH-1 Thank you for your fast report.
It seems there is something wrong going on with oo.library, and after that failure drives the system unstable. That's why you had issues with other machines as well.
I am in contact with the developer to find the bug and fix it. Unfortunately, I am not able to replicate that behavior on my machine. Please allow me to send you more debug versions.
@SteveH-1 Hello again. Can you please check if you have oo.library in libs: folder, as well as under the MediaVault/libs folder? If you have it on both, first check the versions and send them to me.
After that remove the ones that are under libs: or move the ones from MediaVault/libs folder to libs: and then reboot. Then retry to start MediaVault and please tell me if it starts as it should.
Looking forward to hearing from you.
I did have v1.13 of oo.library already in in LIBS: so I removed the one in MediaVault/libs and rebooted. I tried to start the debug version of MediaVault. It did not open and the shell output is:
dbg: before OpenLibs dbg: before open application.library dbg: before open intuition.library dbg: before open utility.library dbg: before open jansson.library dbg: before open amisslmaster.library
BTW, if I delete the oo.library from LIBS: and instead use the one on MediaVault/libs, then the debug text reverts to:
dbg: before OpenLibs dbg: before open application.library dbg: before open intuition.library dbg: before open utility.library dbg: before open jansson.library dbg: before open amisslmaster.library dbg: before open oo.library
@SteveH-1 Thank you once more for your fast report. You help me a lot.
There is one more person at amigans.net that has similar problems with MediaVault and the above steps made the app work, although it is weird.
I still wait for info from oo.library developer on the matter. I will be back to you as soon as I have any news.
Thank you again for your help.
Like the person on Amigans.Net, I have tried deleting the entire LIBS drawer from MediaVault but this did not work for me (the programme still will not launch). I checked there was no other version of oo.library on my system using "which libs:oo.library all" and it only found the one in SYS:libs
I have now tested on a clean OS4.1FE install (Kickstart v 53.70, WB 53.18) with oo.library v1.13 and jansson.library 2.12 in SYS:Libs (having deleted the MediaVault/libs drawer). I am using v4.9 of amisslmaster.library and there is no other version of oo.library installed on this partition. MediaVault still does not launch; the debug version gives this output:
dbg: before OpenLibs dbg: before open application.library dbg: before open intuition.library dbg: before open utility.library dbg: before open jansson.library dbg: before open amisslmaster.library
@SteveH-1 Thank you for doing that. Can you please run in a shell the command NVGetVar and send me the output? Also, do you happen to have a serial connection to an other computer to see if you get something there, after you run MediaVault?
Here is the serial output when I try to open the debug version of MediaVault:
[DOS] Starting DOS 54.114 -- Kernel debug level is 4
HD audio card failed to init :-(
CMI8738 found! :-)
CS4281 DRIVERINIT
No card present.
No cards found! :-(
No SOLO_ONE found! :-(
No SB128 found! :-(
No FM801 found! :-(
No Envy24 found! :-(
Function test::Obtain not implementedFunction test::Obtain not implemented
And here is the results of running NVGetVar: 11.System:> NVGetVar name=options little-endian?= bootargs=console=ttyS0,115200 root=/dev/sda3 ETH0_HWADDR=00:50:c2:20:d9:84 MENU_0_COMMAND=boot -fs=amigafs ide0.1:amigaboot.of MENU_0_LABEL=AmigaOS 4.1 MENU_TIMEOUT=3 MENU_DEFAULT=0 STARTUP=set pmu -astate=A4 ; menu os4_commandline=serial munge debuglevel=4 framebuffer=800/600/8/0x90000000/832 BOOT_CONSOLE=pcconsole0 CFE_VERSION=PAS-2.0.30 CFE_BOARDNAME=NEMO CFE_MEMORYSIZE=2048
@SteveH-1 Thank you so much. I will investigate more the info you provided and be right back to you.
@SteveH-1
I was curious about the Function test::Obtain not implementedFunction test::Obtain not implemented
, so I had a look on my machine output at the serial, and I get the same line as well. So doubt this has anything to do with the underline problem.
Hello @SteveH-1. Can you please check the attached oo.library if it works and MediaVault starts? oo.library.zip
Hi George, I am away on holiday for the next few days, and so will be away from my Amiga :( I will test as soon as I return.
Hi guys! I can help with this issue. I have an X1000, and i can build and debug with Codebench and db101 if necessary. What are the SDK requirements: gcc version and 3th party libraries?
@alfredone Thank you so much. I use GGC 8 and the third party libraries needed are jansson and oo. both available at os4depot. if you clone the project on you machine, prefer to use code based on releases tags and not the master branch, because there are things committed that break the application.
I have tried the new version of oo.library but without success. I still get the following output from the debug version of MV: dbg: before OpenLibs dbg: before open application.library dbg: before open intuition.library dbg: before open utility.library dbg: before open jansson.library dbg: before open amisslmaster.library dbg: before open oo.library
Hello @SteveH-1 Welcome back. Are you sure that the oo.library 1.15 is the only one on your system, either inside libs: or inside MediaVault/libs folders?
Thank you for your valuable help.
I can confirm the only version of oo.library on my system is the one you sent in your link, above - however, that is v1.14, not v1.15
OK, I can see that oo.library v1.15 is on OS4Depot, so I have installed that - it is the only version on my system. I still can't launch MV, but this time the output from the MV debug version is: dbg: before OpenLibs dbg: before open application.library dbg: before open intuition.library dbg: before open utility.library dbg: before open jansson.library dbg: before open amisslmaster.library
@alfredone Thank you so much. I use GGC 8 and the third party libraries needed are jansson and oo. both available at os4depot. if you clone the project on you machine, prefer to use code based on releases tags and not the master branch, because there are things committed that break the application.
I'm, using the SDK 53_33 with GCC 8 from the last adtools package on OS4Depot. I have compiler errors on openssl headers, e.g.:
/SDK/include/include_h/openssl/x509_vfy.h:559: error: expected declaration specifiers or '...' before 'u_int32_t' /SDK/include/include_h/openssl/x509_vfy.h:561: error: expected '=',',',';', 'as,' or 'attribute' before 'X509_VERIFY_PARAM_get_inh_flags'
Do I need to install a specific SDK package for amissl?
Mediavault doesn't use anything from AmiSSL and openssl. You don't need AmiSSL SDK. It just opens AmiSSL library to see if this is available.
Are you using the included Makefile to compile the app?
Are you using the included Makefile to compile the app?
Sorry, i was using the Codebench project. The Makefile is OK, thanks.
I started to debug with db101. It calls IExec->OpenLibrary("oo.library",1), than nothing happens. Same issue with the examples provided by the OO package.
I booted from the Aos4. 1 Fe update 2 partition, with the kickstart modules of the beta partition and mediavault starts without issues. So the kickstart modules are not the problem.
Moreover I discovered that if I backup the envarc: directory and reassign envarc: to the new directory, mediavault starts.
Steve, could you try this from shell?
copy SYS:Prefs/Env-Archive SYS:Prefs/Env-Archive.Backup assign ENVARC: SYS:Prefs/Env-Archive.Backup then launch mediavault?
Hi - Yes, that works! After entering those commands into a shell - although "Env-Archive" is spelled "En-Archive" in the second line :) - I have been able to launch MV. I am now off to happily play around with it. I still don't understand what the issue was, though - why does it launch now?
I think this is a mystery that Hyperion needs to solve.
Now there is a fresh problem! MV will now launch but when I double click on the name of any radio station, nothing plays - Snoopy log attached, Snoopy_Output.txt Also - if I hit "Discover" without entering any text into the "Name" field, I get a DSI error.
MV will now play radio stations as long as I have previously launched AmigaAmp (I suppose it isn't in APPDIR: until then).
Note that if you reassign ENVARC: to the original SYS:Prefs/Env-Archive, it continues to work.
Thank you so much guys for all the tests and investigation you are doing. To be honest I haven't though to ask @SteveH-1 to test oo.library example programs if they work at all.
@alfredone This thing with envarc: does it keep working after a reboot?
MV will now play radio stations as long as I have previously launched AmigaAmp (I suppose it isn't in APPDIR: until then).
Yeah, it needs for now to have amigaamp3 in appdir:. Later versions will allow the user to set the player path, and preferred player.
"@alfredone "This thing with envarc: does it keep working after a reboot?"
Not for me, no - I need to run the command in a shell after each reboot.
"@alfredone "This thing with envarc: does it keep working after a reboot?"
"Not for me, no - I need to run the command in a shell after each reboot."
I confirm. I need to run the command after each reboot.
Can you please guys confirm that when you start your computer, do the examples from oo.library archive work? Also, have you compared your startup-sequence against the one from a clean installation to see if there is something involved with envarc? And while you are there, did you check the user-startup in case something changes the envarc: assign?
There is nothing in startup-sequence referencing ENVARC which differs from a clean install - the only reference is the line: Makelink RAM:Disk.info ENVARC:Sys/def_RAM.info SOFT I have nothing in user-startup referring to ENVARC I can't run the oo.library examples as I don't have a SDK installed on my beta or vanilla partitions.
MediaVault 1.2.0 is installed on my X1000 but won't launch. Snoopy gives the following error:
MediaVault: FAIL = GetVar("EXEC_IMPORT_LOCAL",0x5DF0AD18,8,0x00000200) [4uS]
Steve