Computer Graphics Memory Disk Space
Minimum 386 VGA 1 MB 12 MB
Control: Keyboard, Mouse (recommended), Joystick (recommended)
Sound: Ad Lib, Roland LAPC-1, Sound Blaster
Monitor: Color required
MS-DOS: 5.0 or higher required. Min req. of 600K conventional
memory.
Reviewed version 1.2 on: 486/66, 4MB RAM, SB Pro sound card, Thrustmaster
joystick
기본적인 설정과 스샷 저장경로는
~/.dosbox/doxbox-0.73.conf
~/.
dosbox /capture 에 png 로 저장된다.
아무래도 에뮬레이션이다 보니 성능 저하는 심한편이지만
1.7Ghz CPU로 돌릴경우 386 25Mhz 짜리 성능을 내준다고 하니
그 당시 게임을 돌리는 데에는 문제가 없을 것으로 생각된다.
하지만 486 시절 게임을 돌리려면 ... 최소한 3Ghz 급으로 클럭빨을 세워야 하려나?
Special Keys
ALT-ENTER
Go full screen and back.
ALT-PAUSE
Pause emulation.
CTRL-F1
Start the keymapper.
CTRL-ALT-F5
Start/Stop creating a movie of the screen.
CTRL-F4
Swap mounted disk-image (Only used with imgmount). Update directory cache for all drives!
CTRL-F5
Save a screenshot.(png)
CTRL-F6
Start/Stop recording sound output to a wave file.
CTRL-ALT-F7
Start/Stop recording of OPL commands.
CTRL-ALT-F8
Start/Stop the recording of raw MIDI commands.
CTRL-F7
Decrease frameskip.
CTRL-F8
Increase frameskip.
CTRL-F9
Kill dosbox.
CTRL-F10
Capture/Release the mouse.
CTRL-F11
Slow down emulation (Increase dosbox Cycles).
CTRL-F12
Speed up emulation (Decrease dosbox Cycles).
ALT-F12
Unlock speed (turbo button).
Notes
While we hope that, one day, dosbox will run virtually all programs ever made for the PC... we are not there yet. At present, dosbox run on a 1.7 Gigahertz PC is roughly the equivalent of a 25MHz 386 PC. While the 0.60 release has added support for "protected mode" allowing for more complex and recent programs, but note that this support is early in development and nowhere near as complete as the support for 386 real-mode games (or earlier). Also note that "protected mode" games need substantially more resources and may require a much faster processor for you to run it properly in dosbox.
예전에 정리 해놓은줄 알았는데 없길래 다시 정리.
Xming에서 특정 openGL이 제대로 안되서 부랴부랴 다시 찾는데
opengl의 advanced 소스중 일부가 아래와 같은 오류를 발생하며 실행되지 않는 문제가 있다.
이경우에는 cygwin/x로 하면 문제없이 해결된다.
(하지면 용량이 200메가에 ftp.daum.net은 폐쇄되었는지 안되고 -_- 결론은 받는데 한참걸림)
$ gcc -lglut -lGLU accumaa.c
$ ./a.out
freeglut (./a.out): ERROR: Internal error <FBConfig with necessary capabilities not found> in function fgOpenWindow
X Error of failed request: BadWindow (invalid Window parameter)
Major opcode of failed request: 4 (X_DestroyWindow)
Technical details: ssh tried to run xauth generate to create a untrusted cookie for the session, which failed because the server isn't compiled with the XCSECURITY extension built-in.
6.3. I'm confused about the difference between trusted and untrusted X11 forwarding. What does "Warning: untrusted X11 forwarding setup failed: xauth key data not generated" mean? Why is the SECURITY extension disabled?
The warning means that ssh is going to use trusted X11 forwarding because untrusted X11 forwarding depends on the security extension, which isn't built into the Xserver and has been disabled by default upstream.
Trusted X11 forwarding means that you trust the server that you wish to ssh into. The X server will allow remote clients to do whatever a local client would be able to do to your X session, for example, monitor your keypresses and take a screenshot. Such programs could be run by a malicious or compromised root user on the ssh server, or under your account if it was compromised on the ssh server.
So why is this disabled? Untrusted X11 forwarding was meant to be a way to allow logins to unknown or insecure systems. It generates a cookie with xauth and uses the security extension to limit what the remote client is allowed to do. But this is widely considered to be not useful, because the security extension uses an arbitrary and limited access control policy, which results in a lot of applications not working correctly and what is really a false sense of security. See this mail for more on the subject.
winehq faq에 의하면 다시 마운트 해서 하라는데, 그런다고 해서 CD 내용이 달라지는 것도 아닐테고..
그냥 복사해서 해봐야 할 듯?
6.2. I double-clicked on an .exe file, but the system said "The file foo.exe is not marked as executable..."
If the dialog says "Read about the executable bit", with a hyperlink, try clicking on the hyperlink and reading about the executable bit.
If the file is on your hard drive, right-click it, choose Properties / Permissions, and check "Allow executing file as program".
If the file is on a CD-ROM, you can run it from the commandline as described above. Or, if you know how to use 'mount', remount the cd-rom to mark all files as executable with a command like mount -o remount,mode=0777,exec /media/cdrom but using the real mount point if it's different from /media/cdrom.
