|
Beta 9:
- default GUI and main window position is centered, not top/left corner
- optional ini-file registry replacement.
* -ini <file> in command line: use <file>
* winuae.ini used if it is in same directory as winuae.exe
* file extension must be .ini or it will be ignored
* file will be silently deleted and re-created if
- it is read-only but not delete-protected
- if warning messages in ini-file are modified or deleted
- if it is not compatible with new version
* message will be added to both logs if registry replacement is enabled. Bug reports without also testing in non-ini mode will be ignored.
* Pointless Windows feature "discussions" won't be allowed.
Beta 10: (Paths reseting can make testing very annoying..)
- added missing "barrier" bytes at end of Z3 fast. Crashed in non-direct JIT-mode if read/write crossed memory boundaries. (for example long read from END_OF_Z3 - 2)
- paths reseting to default fix (b9)
Beta 11:
- some device insertions caused crashes
- quick start mode on/off registry setting fixed (b9)
- A3000 RAM detection problem fixed (b10)
- some hardfiles didn't automount
- Sana2 device is working, at least in theory..
Sana 2 device emulation instructions:
Requirements:
OpenVPN Win32 TAP driver http://openvpn.net/download.html (OpenVPN 2.1_rc4 or newer) run OpenVPN installer, only needed component is "TAP-Win32 Virtual Ethernet Adapter"
Now TAP Adapter and real network adapter needs to be bridged. Go to "Network Connections", select both TAP adapter and your real network adapter and select "Bridge Connections" from right mouse menu. http://www.pavelec.net/adam/openvpn/bridge/ (only steps 1 and 2 are needed, name is not important)
Check new bridged adapter has correct IP settings. (This is now your "real" network adapter) Windows networking should continue working normally.
(Perhaps there is simpler solution?)
Enable "uaenet.device" in misc-panel. Emulation-side device name is "uaenet.device" (remember to disable bsdsocket emulation or there may be bsdsocket.library conflicts)
Note: without bridging all sent data goes to black hole and nothing can be received either. Emulator can't detect bridge's status.
Not supported (yet):
- multicast
- tracked stats counters
- promiscuous mode
- something I forgot..
Other notes:
- global stats may not be correct
- stability may not be too good
- very ugly interrupt routine.. (CopyToBuff,CopyFromBuff made things very complex..)
- produces lots of logging
- MiamiDX DHCP and ping worked
- OS3.9 Genesis never tries to send any data.. Confusing..
- didn't test AmiTCP, I didn't bother to configure it
- as you can see, not much testing done.. |
本帖子中包含更多资源
您需要 登录 才可以下载或查看,没有账号?立即注册
x
评分
-
1
查看全部评分
-
|