It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
Hi!
I recently bought this game and Mean Streets is working perfectly. Although, Martians Memorandum doesn't load at all. Dos Box comes up, then it goes to full screen - the dos cursor shows up then Dos Box crashes. I tried installing on both my Vista and XP machines and get the same error. Any suggestions?
Thanks,
- Phil
No posts in this topic were marked as the solution yet. If you can help, add your reply
Try changing the graphics mode in which dosbox runs. GOG provides a tool to do that.
One of the game might be running is a resolution that is less compatibile with your videocard.
avatar
mirka3001: I tried installing on both my Vista and XP machines and get the same error. Any suggestions?

I had the same problem. Mean Streets worked fine, but Martian Memorandum did not. Avoid using the icons on the desktop. You must choose (by default) Start -> Programs -> GOG.com -> Tex Murphy 1 and 2 -> Martian Memorandum -> Graphic Mode Setup
I use Windows Vista so set the 'Change graphic mode' to Direct3D. If that does not work for you, choose one of the other options.
Hope this will help!
Post edited June 17, 2009 by tommyr
Same issue here (On Vista, no XP PC setup right now to test), though changing the settings to 'Run as Administrator' has solved it for me.
Post edited June 17, 2009 by Ois
that sounds like directory/file having the wrong permissions
Post edited June 17, 2009 by Qbix
avatar
mirka3001: I tried installing on both my Vista and XP machines and get the same error. Any suggestions?
avatar
tommyr: I had the same problem. Mean Streets worked fine, but Martian Memorandum did not. Avoid using the icons on the desktop. You must choose (by default) Start -> Programs -> GOG.com -> Tex Murphy 1 and 2 -> Martian Memorandum -> Graphic Mode Setup
I use Windows Vista so set the 'Change graphic mode' to Direct3D. If that does not work for you, choose one of the other options.
Hope this will help!

Thanks Tommy worked for me!
avatar
Qbix: that sounds like directory/file having the wrong permissions

MM is trying to write to "adlib.drv" but is unable to since the user only has ready access to that directory.
It's possible that .drv files aren't allowed to carry over into the virtualstore so they'd need to:
either be manually added in a registry key for each system (not a good idea)
or for specific games they'd need to be packaged specifially with DOSBox and then DOSBox compiled with a manifest file to not use the virtualstore for that application
(Users would then need write access to that directory)
or store the game in the user profile.
Also it looks like both MM and MS are using old config files.
Issue is caused by the Music driver not SFX. Disabling music in MM.CFG removes the error. (Using Roland causes the same issue just a different driver).
Post edited December 21, 2009 by DosFreak
avatar
Qbix: that sounds like directory/file having the wrong permissions
avatar
DosFreak: MM is trying to write to "adlib.drv" but is unable to since the user only has ready access to that directory.
It's possible that .drv files aren't allowed to carry over into the virtualstore so they'd need to:
either be manually added in a registry key for each system (not a good idea)
or for specific games they'd need to be packaged specifially with DOSBox and then DOSBox compiled with a manifest file to not use the virtualstore for that application
(Users would then need write access to that directory)
or store the game in the user profile.
Also it looks like both MM and MS are using old config files.
Issue is caused by the Music driver not SFX. Disabling music in MM.CFG removes the error. (Using Roland causes the same issue just a different driver).

Ah yes that makes sense.
DRV is on the list of non virtualized extensions. So windows will not virtualize it and hence opening in write mode fails as the user doesn't have the right permissions.
Installing it in a normal directory is probably the easiest, although simply modifying the permissions of this one file in question is probably the fastest