DOSBOX installation failed

edmaul69

Deleted

BuZz

@edmaul69 Their router could be "blocking" the URL - this happened before when someone had some anti malware from trend micros on their router and one of our URLS got incorrectly blacklisted.

edmaul69

@buzz you beat me to deleting my post. I just saw your last post.

BuZz

@edmaul69 please don't delete - it breaks the discussion - rather you just left your post, or can edit and strike through. It may well still be their internet still since the URL seems fine on the trend micros website for example.

edmaul69

@retrofreak89 here are the settings in the dosbox config you want for maximum performance. one of the memsize needs to be added as it isnt in the config by default.

language=
machine=svga_s3
captures=capture
vmemsize=8
memsize=63

core=dynamic
cputype=pentium_slow
cycles=max 110%
cycleup=10
cycledown=20

LasagnaDevil

@buzz

First of all, thanks for your reply!

"cat /etc/issue" outputs: Raspbian GNU/Linux 8 \n \l

"sudo __debug=1 ./retropie_packages.sh dosbox sources" outputs
sudo: ./retropie_packages.sh: command not found

"wget -S -O/dev/null -q https://files.retropie.org.uk/archives/dosbox-r3876.tar.gz" runs without error messages, but I can't find the file.

Then again, a simple "wget https://files.retropie.org.uk/archives/dosbox-r3876.tar.gz" outputs this:

--2017-03-03 23:03:53-- https://files.retropie.org.uk/archives/dosbox-r3876.tar.gz
Resolving files.retropie.org.uk (files.retropie.org.uk)... 93.93.129.253, 2a00:1098:0:80:1000:57:0:1
Connecting to files.retropie.org.uk (files.retropie.org.uk)|93.93.129.253|:443... connected.
ERROR: The certificate of ‘files.retropie.org.uk’ is not trusted.
ERROR: The certificate of ‘files.retropie.org.uk’ is not yet activated.
The certificate has not yet been activated

How come this wasn't a problem installing other Emus and files from the server? O.o

BuZz

@lasagnadevil sudo apt-get install ca-certificates might help - looks like you have missing certificates.

LasagnaDevil

@buzz, again, thanks for all the help!

after getting ca-certificates:
Reading package lists... Done
Building dependency tree
Reading state information... Done
ca-certificates is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 103 not upgraded.

But then I run wget again...
--2017-03-04 15:03:09-- https://files.retropie.org.uk/archives/dosbox-r3876.tar.gz
Resolving files.retropie.org.uk (files.retropie.org.uk)... 93.93.129.253, 2a00:1098:0:80:1000:57:0:1
Connecting to files.retropie.org.uk (files.retropie.org.uk)|93.93.129.253|:443... connected.
ERROR: The certificate of ‘files.retropie.org.uk’ is not trusted.
ERROR: The certificate of ‘files.retropie.org.uk’ is not yet activated.
The certificate has not yet been activated

:(

BuZz

@lasagnadevil Something is wrong with your system. you can try

sudo update-ca-certificates

but if that still doesn't help you might want to start from a fresh image.

Also check your system date/time. eg via date

LasagnaDevil

I've done a fresh install. Had the same issue twice. Wouldn't have come here to bother, otherwise.

I've noticed the output of date command is wrong (googled a bit more, and your message also pointed me in the right direction), and after some googling I managed to force my Pi to use the servers for the timezone of the South American region where I am, editing the "ntp.conf" file. Still, it didn't update to the proper date. So, via Raspi-Config, I forced the Pi to use the proper localization. Still no proper sync.

I ended up forcing things via sudo date -s "10 Aug 2017 12:18:00". Basically, a big f*ck you to any system sync of date and time. I don't care that much about those.

And after typing that... BOOM! DosBox binaries show up in Retropie Setup script. Everything seems solved. Didn't even have to update the script.

The puzzling thing is I've never had this problem before. Been using Linux for about ten years and Retropie since 3.4, and never ran into this. O.o

Thanks a lot for your help! :D

BuZz

@lasagnadevil Glad you have it sorted. Wonder if NTP is unable to connect to the timeservers for some reason - I have seen this before when someone's router/isp was blocking the port.

LasagnaDevil

Welp, unless my ISP has changed its ruleset, I dunno. I've done this a billion times, never ran into this issue before.

Weird. But now we know!

Thanks again for all the help and patience!

edmaul69

@buzz iv had this issue just by not having the time set so the year would be 1969. Setting the correct time fixed it for me. I have a rtc now which solves the issue for me. I think i set it to set the internet time while booting as well, so if my rtc failed it would set the internet time.