I posted this in Sync Discussion, but it might be better here. There are a couple dos doors that my wife and I play daily and it's pretty much the reason I set this back up so I'd really appreciate any possible guidance.
After upgrade from 3.19 - 3.20 I'm getting a CPU Exception. The doors run fine when I run dosemu from command line and they were working before upgrade. It's throwing a system exception though which I know is strange. There are also other door games running fine through DosEMU. I also had made a few stupid mistakes on the upgrade on my end and I had to recereate the settings files. It's very possible I am missing a setting. I also thought permissions might be an issue, but I think I've come to the end of all the iterations I can do with that along with other DOS doors running fine.
Thanks!
ERROR: Accessing reserved memory
at ffffffff00044928 Maybe a null segment registerERROR: unexpected CPU excep
tion 0x0e err=0x00000005 cr2=ffffffff00044928 while in vm86 (DOS)Program=sigsegv
.c,
I can't think of any reason why the upgrade to v3.20 would be a factor with these errors. You could installv 3.19 and experiment
and see if the error magically disappears with that version, but I'd be very suprised and confused if that was the case.
Yeah I know it doesn't make any sense to me at all, I don't know the specifics, but I'm guessing you are just passing the fossil stuff and it's outside of Synchronet's control. That coupled with the fact other doors are working just fine. I'm just really hoping someone would see the post and it would spark a thought. It's a major bummer.
Yeah I know it doesn't make any sense to me at all, I don't know the specifics, but I'm guessing you are just passing the fossil stuff and it's outside of Synchronet's control. That coupled with the fact other doors are working just fine. I'm just really hoping someone would see the post and it would spark a thought. It's a major bummer.
Did you by chance also update your Dosemu? Sometimes I've noticed certain builds of Dosemu have changes that can cause issues that weren't there before.
Did you by chance also update your Dosemu? Sometimes I've noticed certain
builds of Dosemu have changes that can cause issues that weren't there
before.
Thanks for the reply. I had the same thought and looked up Dosemu and it seems like it hasn't been updated since 2014 unless I was seeing something wrong..
get any of the RTE patches on three doors to ever take, but the TSR would work with them. I read a little and it seems like if the exe is compressed it won't allow the patches to work, but the TSR would still work (although there are very little resources on that).
I'll keep trying stuff, it's been working for years and I had to fudge with
Did you by chance also update your Dosemu? Sometimes I've noticed certain
builds of Dosemu have changes that can cause issues that weren't there
before.
Thanks for the reply. I had the same thought and looked up Dosemu and it seems like it hasn't been updated since 2014 unless I was seeing something wrong..
Do you mean the package on your system, or Dosemu itself? If you're using Dosemu 1.x (I think 1.4?), I think that hasn't been updated since then, but the newer Dosemu2 is under active development.
get any of the RTE patches on three doors to ever take, but the TSR would work with them. I read a little and it seems like if the exe is compressed it won't allow the patches to work, but the TSR would still work (although there are very little resources on that).
I'll keep trying stuff, it's been working for years and I had to fudge with
you can try unp on them. if they stripped the headers it wont unpack it. there are other ones that force it if it's stripped but i wouldn't trust them.
Did you by chance also update your Dosemu? Sometimes I've noticed certain
builds of Dosemu have changes that can cause issues that weren't there
before.
Thanks for the reply. I had the same thought and looked up Dosemu and it seems like it hasn't been updated since 2014
unless I
was seeing something wrong..
Do you mean the package on your system, or Dosemu itself? If you're using Dosemu 1.x (I think 1.4?), I think that hasn't been
updated since then, but the newer Dosemu2 is under active development.
Ahhhh, I did not realize there was an active development version. When I go in I see this -
"Welcome to dosemu 1.4.0.8!"
But maybe it will work on the new one? And Sync can call that one too? Thanks!
you can try unp on them. if they stripped the headers it wont unpack it. there are other ones that force it if it's stripped but i wouldn't trust them.
That's a little out of my range of capability, but I'm not sure I have any other shots here thanks.
you can try unp on them. if they stripped the headers it wont unpack it. there are other ones that force it if it's stripped but i wouldn't trust them.
That's a little out of my range of capability, but I'm not sure I have any other shots here thanks.
how is that out of your range? you cant run an exe unpacking utility on them?
Ahhhh, I did not realize there was an active development version. When I go in I see this -
"Welcome to dosemu 1.4.0.8!"
But maybe it will work on the new one? And Sync can call that one too? Thanks!
There are some differences in Dosemu2. I thought almost all DOS doors worked well with dosemu 1.4. The only one that didn't work was TradeWars 2002, which was the reason I updated to Dosemu2. I noticed that some other doors didn't run very well though (some are very slow, like there's an infinite loop keeping the CPU busy).
you can try unp on them. if they stripped the headers it wont unpack it. there are other ones that force it if it's
stripped
but i wouldn't trust them.
That's a little out of my range of capability, but I'm not sure I have any other shots here thanks.
how is that out of your range? you cant run an exe unpacking utility on them?
Ahhhh, I did not realize there was an active development version. When I go in I see this -
"Welcome to dosemu 1.4.0.8!"
But maybe it will work on the new one? And Sync can call that one too? Thanks!
There are some differences in Dosemu2. I thought almost all DOS doors worked well with dosemu 1.4. The only one that didn't
work
was TradeWars 2002, which was the reason I updated to Dosemu2. I noticed that some other doors didn't run very well though
(some
are very slow, like there's an infinite loop keeping the CPU busy).
Nightfox
Oh man I just noticed something running in console mode from Syncronet! If I run DOSEMU from command prompt and type SHARE, I get SHARE loaded. This is what it shows from Synchronet -
"Welcome to dosemu 1.4.0.8!"
About to Execute : D:external.bat
dosemu FOSSIL emulator: installed.
Bad command or filename - "share.exe".
Bad command or filename - "ansi.com".
Why is it not finding share or ansi.com when running via the Synchronet call? I think this might be the key here, trying not to get too excited, but I have no idea why it finds it no issue when I call DOSEMU from command line, but it's not seeing it from Synchronet call. It might just be a simple Linux alias or something I don't know about.
I'm not sure why that might be.. But I believe Synchronet has its own directory for the C drive for dosemu, and in exec/dosemu.ini, it injects some variables to specify the different drives for dosemu. Maybe that's a place to start.
A tad less excited now, share.exe isn't on my system, but share.com is and that's what was running when I typed share from the command line.
If I look at the node/external.bat file there's a REM'd debug section that has all the variables that the dosemu.ini sets and it appears okay to me.
Re: Several Doors not working after upgrae[Box Dice]
By: Nightfox to The Lizard Master on Sat Sep 09 2023 11:40 am
Did you by chance also update your Dosemu? Sometimes I've
noticed certain builds of Dosemu have changes that can cause
issues that weren't there before.
Thanks for the reply. I had the same thought and looked up
Dosemu and it seems like it hasn't been updated since 2014
unless I was seeing something wrong..
Do you mean the package on your system, or Dosemu itself? If
you're using Dosemu 1.x (I think 1.4?), I think that hasn't been
updated since then, but the newer Dosemu2 is under active
development.
It also works just fine when I run it in DOSEMU, it doesn't when I
call it from Synchronet. So it doesn't leave me with much of a way to
figure it out.
---TLM
---
■ Synchronet ■ I filled this out to keep people from complaining...
I think I had to make some changes. Specfically, make sure I/O method
is FOSSIL or UART, Native Executable/Script is set to No and Use Shell
or New Context is Yes. The rest shouldn't matter. With these 3 set,
dosemu2 definitely works with the latest synchronet.
Great news! So I just decided to spin up a new Synch and installed dosemu2 to test. I followed the wiki, but I'm getting a response that dosemu2 can't find XTRNDIR. I assume this is a var setting somewhere I missed? Is there anyway to write this to the screen? Door.sys is getting written to the door directory so synch is finding and writing to it correctly in /xtrn/door.
| Sysop: | digital man |
|---|---|
| Location: | Riverside County, California |
| Users: | 1,063 |
| Nodes: | 17 (0 / 17) |
| Uptime: | 34:57:29 |
| Calls: | 501,357 |
| Calls today: | 2 |
| Files: | 109,427 |
| D/L today: |
1,940 files (259M bytes) |
| Messages: | 302,469 |