Steamをインストール
ログイン
|
言語
简体中文(簡体字中国語)
繁體中文(繁体字中国語)
한국어 (韓国語)
ไทย (タイ語)
български (ブルガリア語)
Čeština(チェコ語)
Dansk (デンマーク語)
Deutsch (ドイツ語)
English (英語)
Español - España (スペイン語 - スペイン)
Español - Latinoamérica (スペイン語 - ラテンアメリカ)
Ελληνικά (ギリシャ語)
Français (フランス語)
Italiano (イタリア語)
Bahasa Indonesia(インドネシア語)
Magyar(ハンガリー語)
Nederlands (オランダ語)
Norsk (ノルウェー語)
Polski (ポーランド語)
Português(ポルトガル語-ポルトガル)
Português - Brasil (ポルトガル語 - ブラジル)
Română(ルーマニア語)
Русский (ロシア語)
Suomi (フィンランド語)
Svenska (スウェーデン語)
Türkçe (トルコ語)
Tiếng Việt (ベトナム語)
Українська (ウクライナ語)
翻訳の問題を報告
Also is sad, that we need someone to fix game which we pay for.
You don't have to copy the game (it will not work with Steam then)... maybe just for the backup purpose. The tool make a junction folder on drive C: "C:\MAX_PACK.W95" instead (and create a folder "C:\MAX_PACK.BAK" for save game backup). This trick allow to run game from Steam. When you will run game from Steam (or Steam shortcut) it will count game play time, otherwise run it with DOSBox.exe directly (when 95RPP is installed it's launcher, real DOSBox is renamed to BoxDOS.exe). Don't know if overlay working, since no one reported. On my PC overlay starting in background but it's not available in game, but same is when running without the 95RPP. If you are using "modern" Windows do not install additional wrappers (optional), those can crash at start.
(when it size it's bigger it should be safety to remove it either since it's only link not real folder, however we can only delete the MAX_PACK.W95 NOT the files / folders inside, since deleting the files will wipe the whole game with savegames, so for non advanced user more safety is to rename it).
This is probably rare situation when launcher trying to run game when 95RPP is not installed properly (Steam installation or linked folder moved or removed). Launcher try to run game, but when folder is missing, it create empty folders which cause it to stuck. I will fix that later...
The message is "Can't find the $Exe95 in expected location!", where "$Exe95" is exec name.
Please confirm if this help.
tried gog version, same issue.
win10
gtx970 latest drivers
intel i5 4670k
played tomb rider win95 version on this same pc no issues, just a few days ago.
I guess launcher-setup now show up without errors.
During 95RPP installation you have options to install 3 wrappers, first two are known to possibly crash under Windows 10, so those are disabled by default, only ddraw wrapper working and as far as I know it is required, however I think D3DWindower can be used instead (can't test it under Win 10).
So if you have installed default options (no IPX and CD wrappers) I think you can try to switch ddraw wrapper to OpenGL or GDI. Or disable it and try D3DWindower instead, however I not guarantee this will help.
(You can disable wrappers manually - just rename the wsock32.dll and winmm.dll if those are not renamed already, ddraw.dll can be replaced with D3DWindower [make backup]).
You can also try to run game exec directly (outside Steam) from:
C:\MAX_PACK.W95\CARMA\CARM95.EXE (C1)
C:\MAX_PACK.W95\CARSPLAT\CARM95.EXE (SP)
But note that when wrappers are present they are in use no matter how 95 version is started.
Other thing, maybe Tomb Raider have different version of wrapper/s included? Since now we have more versions where some work under XP, Vista, but the other under 8 and 10 (AFAIK).
Another thing... the 95RPP can be installed only for one version of game on one PC, so if you installed it for both versions only last installation will work correctly!
tried running from steam, from folder, etc, always the same. Basically, i've exhausted all the basic troubleshooting and it doesn't work.
so obviously it doesn't work on win10 or there is some conflict with drivers from nvidia.
this is what tomb raider 1996 uses for win95 version on modern hardware.
tried d3dwindower as well, same exact error.
https://github.com/ata4/glrage
works fine here. so I guess yours needs more testing on win10. hopefully some other win10 user can chime in with his experience.
If you have ways of me sending you a log file or something so you can fix it for win10, i'd be glad to help.
In my opinion problem is caused by the wrapper/s... or/and there is something wrong with the installation...
Try to install 95RPP again, but leave all options as they are, just uncheck "Disable C1 Password..." (the default password for Steam/GOG version is "gog"). That option will enable password screen (as is in original version) which should show up when 95 version is launched (maybe it not crash at least at this point).
I'm glad you want help :), but I have no idea which log may help me. You can try to debug it by your self - there is great tool that allow to trace which files (registry keys, etc.) are accessed. I usually using it to see on which file C1 (or other prog) crash, so this eventually may tell you something. On win XP something like dr Watson is starting after crash.
Warning: Log from that tool may be very big and may contains sensitive data, so do not post it anywhere!
The older version was Filemon (only for file access; for registry was Regmon), current we have ProcMon which integrate previous tools into one. Since sysinternals.com page is currently down (?), the exe file need to be downloaded from live source[live.sysinternals.com].