nono is OMRON LUNA-I emulator runs on NetBSD and so on.+nono は NetBSD とかで動作する OMRON LUNA-I/LUNA-88K +(と SHARP X68030) のエミュレータです。 +
nono is OMRON LUNA-I/LUNA-88K (and SHARP X68030) emulator +runs on NetBSD and etc.
How to build
How to build
How to execute
Configuration
About VM
Try it
Example of host network setup
Known Issues
How to migrate from old versions
Changes
Contact, License, etc
+
Green Background is new or updated paragraph.+
How to build
The followings are required for build.+
+wxWidgets は NetBSD(pkgsrc) なら pkgsrc/x11/wxGTK30 です。
+OPTIONS:gtk3 で動作確認しています。
+If you use NetBSD(pkgsrc),
+wxWidgets is pkgsrc/x11/wxGTK30 (OPTIONS:gtk3 is tested).
+
+
+(NetBSD 以外でのビルドはサポートしていませんが)
+Ubuntu 20.04 ではたぶん以下のパッケージが必要です。
+You may need the following packages on Ubuntu 20.04
+(though we won't support non-NetBSD platform).
+
+nono のソースアーカイブを展開したら以下のようにビルドします。
+configure には環境変数 CC、CXX でコンパイラを指定することが出来ます。
+また wx-config が標準的な名前で提供されていないために見付けられない場合には
+環境変数 WX_CONFIG にパスを指定することが出来ます。
+Extract the nono's source archive and build as following.
+You can specify C/C++ compiler using environment variable CC and CXX
+if configure cannot find standard name suitable compiler.
+Also, you can specify wx-config path using environment variable WX_CONFIG
+if configure cannot find wx-config.
+
+-DNOTEST は開発者用のテストツールをビルドしないためのものです。
+With -DNOTEST, the build excludes test tools which is needed
+for developers only.
+
-まだ make install はないです。 -wx/nono が GUI 版実行ファイル、 -cli/nono-cli がコマンドライン版です。 + +% ./configure -% make depend -% make +% make -DNOTEST depend +% make -DNOTEST +% su +# make install
+2つの実行ファイルがインストールされます。
+nono が GUI 版実行ファイル、
+nono-cli がコマンドライン版です。
+Two executables will be installed.
+nono is the GUI executable and nono-cli is
+the command line executable.
Command Line Option
How to execute
Command Line Option
Specifies the VM directory/configuration file. +If vmpath is a directory, +make nono.cfg in that directory a configuration file. +Or if vmpath is a file, +make the specified file a configuration file. +And in both cases, +make the directory where that file is located a VM directory. +If -c option is omitted, +vmpath is considered as the current directory.
Boot as the fast mode. +You can change this mode on GUI menu after boot, +and the option only changes its initial state.
+GUI Only. +Specifies the initial fontsize on all sub windows. +height is one of 12 or 16. +The default value is 12. +You can change this value on GUI menu after boot.
+GUI Only. +Specifies the initial main window scale in real number. +You can change this scale on GUI menu after boot, +but unlike this option, there are only a few preset choices +(Should be improved in someday). +The default value is 1.0
Shows the result of reading configuration file and +parsing -V options.
Shows the version.
Use this name=value +instead of name=configvalue specified in configuration file. +If name is not correct, it will exit on error.
Loads and executes host's file. +If file is relative path, +it is path from the current directory. +If the file is gzip'd, it is automatically extracted. +The supported file format (after extracting) is a.out (OMAGIC) or ELF. +Actually, it only assumes bootloaders or kernels. +Regardless of prom-image and luna-dipsw1 configuration +(see below), +the internal emulated PROM loads and executes the host file immediately.
For developers:
Configuration
Configuration
VM configuration file is nono.cfg +(or the file specified by -c option) in the VM directory. +Its syntax is key = value format, one per line. +White spaces before and after key and value are ignored. +Blank lines, lines beginning with "#" are also ignored. +The lines with unrecognized key are ignored with a warning.
設定項目は次の通りです。
+The configuration items are:
Specifies the VM type from the following. +This field is mandatory.+
| luna | … LUNA-I + | |
| luna88k | … LUNA-88K + | |
| x68030 | … X68030 (Experimental) + |
Specifies the X68030's external CGROM image file path. +This CGROM is 768KB. +If the path does not have any path delimiters, +the VM directory and then its parent directory will be searched. +If the path is a relative path, +it will be path from the VM directory, not from the current directory. +If the path is empty, nono's builtin compatible CGROM will be used. +The default value is empty.
Specify how to synchronize the time in virtual machine. +If real, synchronize with the real time; +if virtual, synchronize with the virtual time. +The default is real. +This feature is under experimentation and may be changed in the future +without notice.
Specifies console driver of the debugger. +stdio, tcp, and none can be specified. +stdio uses the standard input/output. +tcp listens on TCP port using TELNET protocol. +none doesn't make any communication with the host. +The default is none.+
Specify the TCP port number that debugger console driver listens.
Specify the number of floppy drives from 0 to 4. +The default is 2.
Specify a diskimage to be inserted to floppy drive N at startup. +If the path is relative path, it is from the VM directory. +You can also operate them from menu after startup. +The default is empty.
Specify whether to install FPU or not. +If none, FPU is not installed. +If 68881, 68881 FPU is installed. +68882 is not supported yet. +And, none can also be written as 0, +68881 can also be written as 1. +The default is 68881. +This item cannot be specified on LUNA-I +because (probably) all LUNA-I has 68881.+
Specifies the host driver of serial port. +stdio, tcp, and none can be specified. +stdio uses the standard input/output. +tcp listens on TCP port using TELNET protocol. +none doesn't make any communication with the host. +The default is none.
Specify the TCP port number that host driver listens.
Specify the behavior when the driver which is selected by +hostcom-driver is unusable; +terminate the process if 0, +or continue to run using the none driver if 1. +The default is 0.
Specifies the input mode of the host keyboard. +char means the character mode, +jp means the Japanese keyboard mode. +The defualt is char. +See About VM for details.
Specifies the host driver of ethernet device. +afpacket, bpf, and tap can be specified +only if the host OS supports them. +auto and none can always be specified. +afpacket uses Linux's AF_PACKET socket, +bpf uses bpf(4) device, +and tap uses tap(4) interface. +none doesn't make any communication with the host. +If auto is specified, +it tries tap, afpacket, and bpf in that order +(if the host OS supports them). +The default is auto.
Specify an interface name to bind to, when the host driver is afpacket. +If auto is specified as ifname, +it selects an usable interface automatically. +The default is auto. +Note that this host driver cannot communicate with the localhost.
Specify an interface name to bind to, when the host driver is bpf. +If auto is specified as ifname, +it selects an usable interface automatically. +The default is auto. +Note that this host driver cannot communicate with the localhost.
+Specify a device pathname, when the host driver is tap. +The default is auto. +The behavior in this case depends on the host OS. +On Linux, it's the same as /dev/net/tun. +On OpenBSD, it will try from /dev/tap0 to /dev/tap9 +until successful. +On NetBSD (and FreeBSD), it will try cloning by /dev/tap first. +If that fails, then try from /dev/tap0 to /dev/tap9 +until successful. +In all cases, you need to prepare two shell script files which names are +nono-ifup and nono-ifdown in the VM directory or +its parent directory. +Even if you don't have anything to do in these scripts, +you need to prepare empty scripts that will terminate successfully.
Specify the behavior when the driver which is selected by +hostnet-driver is unusable; +terminate the process if 0, +or continue to run using the none driver if 1. +The default is 0.
Specifies the X68030's external IPLROM image file path. +This one contains 128KB at 0xfe0000..0xffffff and is known as IPLROM30. +If the path does not have any path delimiters, +the VM directory and then its parent directory will be searched. +If the path is a relative path, +it will be path from the VM directory, not from the current directory. +If the path is empty, the public released IPLROM30 will be used. +The default value is empty.
Specifies the X68030's external IPLROM image file path. +This one contains 128KB at 0xfc0000..0xfdffff and is known as ROM30. +If the path does not have any path delimiters, +the VM directory and then its parent directory will be searched. +If the path is a relative path, +it will be path from the VM directory, not from the current directory. +If the path is empty, internal emulated ROM will be used. +The ROM supports only enough SCSI IOCS to boot NetBSD/x68k. +The default value is empty.
Specify whether to connect keyboard on boot. +If 1, it is connected; if 0, it isn't connected. The default is 1. +You can change it on GUI menu after boot.
+Specifies whether nono corrects RTC emulation for OSes +that adopts wrong RTC epoch on LUNA. +0 means making no correction +(this is the same behavior as the actual machine). +1 means making correction +(this is the same behavior as the real world). +The default is 1. Normally, leave it 1.+
+LUNA で採用している RTC (MK48T02) は2桁で保持している年の値が +4 で割り切れる年をうるう年とする仕様です。 +ところが NetBSD/luna68k、OpenBSD/luna88k などはこの +RTC の年の値を 1970年からの経過年として使用しています。 +例えば1970年はうるう年ではないため 2月28日の翌日は 3月1日ですが、 +MK48T02 的には 00年であるためうるう年と認識し 2月28日の翌日が2月29日になります。 +このように、これらの OS を使っている場合実機の +RTC は4年のうち約2年間、1日ずれた日付を指しているようです。 +しかしながら、RTC の時刻は OS 起動時に一度読んだ後は基本的に参照しない上、 +今時必要なら NTP で時間を合わせるため、 +実機でも問題が顕在化することはまずないと思います。 +nono の場合は実機と異なり、アプリケーション実行中しか RTC が進まないため、 +補正がない場合の動作が問題になるのは +nono を起動したまま偶数年の2月末日から日付をまたいで、 +かつ nono を起動したまま OS を再起動して NTP などで時刻修正を行わなかった時 +だけだと思います。 +このオプションはほぼ開発者向けの動作確認用です。
Specifies status of the front panel DIPSW#1-1..#1-8 using 8 digit. +"0" means DOWN and "1" means UP. +The first character corresponds to #1 and +the eighth character corresponds to #8.+
+LUNA-I でのデフォルトは 11110111 です。
+各スイッチの内容は以下のリンクを参照してください。
+On LUNA-I, the default value is 11110111.
+See the following link about DIPSW.
+→ NetBSD/luna68k: Information
-各スイッチの内容はここ
-(NetBSD/luna68k: Information) を参照してください。
On LUNA-88K, the default value is 11111111. +See the following link about DIPSW.
Specifies status of the front panel DIPSW#2-1..#2-8. +The same syntax as luna-dipsw1 is used. +The default value is 11111111.+
+NetBSD/luna68k のブートローダは、
+DIPSW#2 が "11111111" なら自動的にカーネルをロードして実行し、
+どれかでも "0" にするとプロンプトで停止するようです。
+(本当は #8 だけで制御するつもりだったんじゃないかという気がします)
+NetBSD/luna68k bootloader will automatically load and execute the kernel,
+if the DIPSW#2 is "11111111".
+Otherwise, the bootloader will enter interactive mode.
+(I doubt that they actually wanted to switch with only #8)
+
Specify number of planes on LUNA video board. +The valid values are 1 or 4. +1 means a monochrome video board, +4 means 16-color (4bpp) video board. +Note that 8bpp video board is not (yet?) supported. +The default value is 1 for now (It may be changed in the future).
Specifies refresh rate of all text monitor windows in Hz. +It ranges from 1 to 60. The default is 20Hz. +You can change this value on GUI menu after boot, +but unlike this configuration value, there are only a few preset choices.
Specifies the MPU clock in MHz. +The default value is 20MHz on LUNA-I, or 25MHz on LUNA-88K +and X68030.
Specifies the LUNA-I/LUNA-88K's external ROM image file path. +If the path does not have any path delimiters, +the VM directory and then its parent directory will be searched. +If the path is a relative path, +it will be path from the VM directory, not from the current directory. +If the path is empty, internal emulated ROM will be used. +The default value is empty.
-実機を持っていない場合はこの値を 0 にしておくと、
+実機を持っていない場合はこの値を空に (= デフォルトのままに) しておくと、
nono 内蔵のなんちゃって下位互換 ROM で起動します。
+If you does not have the real LUNA machines,
+you can boot with nono's internal downward compatible emulated ROM
+if you set this field empty (or leave it as the default).
+
+LUNA-I 実機を持っている場合は
+ROM ファイルを指定することで実機 ROM で起動できます。
+ROM ファイルは実機の 0x41000000-0x4101ffff (128KB) を保存したものです。
+今のところ ROM は V4.22 (Thu Jul 27 11:45:42 1989) のみサポートしています。
+それ以外については何も分かりません。
+If you have the real LUNA-I machine,
+you can boot with the real ROM spcifying the ROM file path.
+The ROM file is extracted from 0x41000000-0x4101ffff (128KB) of
+the real LUNA-I machine.
+For now, only V4.22 (Thu Jul 27 11:45:42 1989) is supported.
+I have no idea about other ROMs.
+
+LUNA-88K 実機の場合は 0x41000000-0x4103ffff (256KB) を保存したものです。
+今のところ ROM は version 1.20 のみサポートしています。
+
+For LUNA-88K,
+the ROM file is extracted from 0x41000000-0x4103ffff (256KB).
+For now, only version 1.20 is supported.
Specifies the RAM size in MB.+
On LUNA-I, the default is 16MB. +If the size is less than 16MB, you can specify in 4MB unit. +If larger, you can specify up to 255MB in 1MB unit. +By the way, NetBSD/luna68k needs at least 8MB to boot.+
On LUNA-88K, the default is 64MB. +If the size is less than 64MB, you can specify in 16MB unit. +If larger, you can specify up to tentative 255MB in 1MB unit.+
On X68030, the default is 12MB. +You can specify it in 1MB unit from 4MB to 12MB.+
Specifies the RTC (MK48T02) epoch year. +The default is 1970. +Since both NetBSD/luna68k and OpenBSD/luna88k use 1970 as epoch year, +there is no need to touch this value. +If you boot 4.4BSD on LUNA-I as the guest OS, specify 1900.
Specifies whether to display the status panel or not. +If 0, it is hidden; if 1, it is shown. +You can change it on GUI menu after boot.
+Specifies SCSI device and image. N in the key is 0 to 7. +But don't specify ID 7 because the host uses it. +The value is in a form of device type devtype and +the disk image path path separated by ","(comma). +devtype can be one of the following:+
+devtype が hd なら path は省略できません。
+devtype が cd か mo なら path は省略可能です。
+イメージパスが相対パスなら VM ディレクトリからの相対パスになります。
+
+If devtype is hd, path cannot be ommitted.
+If devtype is cd or mo, path can be ommitted.
+If the path is relative path, it is from the VM directory.
+
-実機を持っている場合は ROM ファイルを用意して -この値を 1 にすると実機 ROM で起動できます。 -ROM ファイルは実機の 0x41000000-0x4101ffff (128KB) を PROM.DAT (大文字) -という名前で保存したもので、VM ディレクトリに置きます。
-例えば、nono.cfg と同じディレクトリに置いたディスクイメージ luna.img
-を使う場合、
-LUNA では通常 ID 6 をプライマリ HDD に割り当てるのでこんな感じになります。
+例えば、nono.cfg と同じディレクトリに置いた sd0.img を
+起動 HDD ディスクイメージとして使い
+(LUNA では通常 ID 6 をプライマリ HDD に割り当てます)、
+ID 5 に同じディレクトリの install.iso をセットした CD ドライブを、
+ID 4 に起動時メディアなしの MO ドライブを接続する場合は次のようになります。
+For example, if you use a harddisk image sd0.img placed in the same
+directory as nono.cfg
+(LUNA usually assigns ID 6 to the primary HDD),
+ID 5 for CD-ROM drive that loads install.iso in the same directory,
+and ID 4 for MO drive without media on boot,
+write as following:
-spc0-id6-image = hd,luna.img +spc0-id6-image = hd,sd0.img +spc0-id5-image = cd,install.iso +spc0-id4-image = mo
Specifies the average seek time of specified SCSI HDD in msec. +Currently, the default value is 0 +(This may be something like SSD :-). +If you specify about 16 or so, you can feel nostalgic, +but this feature is still unstable.
Specifies whether nono ignores writing to SCSI HD devices. +0 means normal operation (writes to the devices). +If 1 is specified, +nono will not actually write back to the disk image +even though the write command is succeeded. +nono's SCSI devices acts as +write command is successfully done but it never writes back +to the actual disk image. +This is useful for kernel debugging because it does not require fsck +after the kernel hangs. +But don't use this flag if you don't understand this paragraph. +The default value is 0.+
+ちなみに、メディアを書き込み禁止にしたい場合はこれではなく、
+イメージファイルの書き込み権を落としてください。
+By the way, if you want to make the media write-protected,
+clear the write permission from the image file
+(instead of this setting).
Obsolete. +Use spc0-idN-writeignore instead. +This option is for developers.
Specify whether to synchronize a RAM size field in SRAM +with real RAM size or not. +If 0, the application will do nothing (as same as the real). +If 1, the application updates(synchronizes) +$ed0008.L (RAM size) in SRAM with configuration value of ram-size. +This update is performed once only if +the SRAM magic string is correct at the application startup. +The default is 1.+
Try it
About VM
Implementation Status+
| ◎ | : ほぼ実装済み Mostly implemented+ |
| ○ | : 困らない程度には実装済み Works+ |
| △ | : とりあえず動いてる程度 Works somehow+ |
| × | : 未実装 Not implemented+ |
| — | : 実装予定なし Not planned+ |
| LUNA-I + | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MPU (68030) + | ○ + | キャッシュ未実装 Cache not implemented+ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| FPU (68881) + | ◎ + | + | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| BT454 + | ◎ + | + | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CRTC2 + | ○ + | 標準で使用する値のみサポート + | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Frame buffer + | ◎ + | + | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Keyboard/Mouse + | ◎ + | + | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| SIO + | ◎ + | + | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| PIO + | ○ + | + | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Ethernet (AM7990) + | ◎ + | LARF を除く Except LARF+ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| NVRAM&RTC (MK48T02) + | ◎ + | + | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Front LCD + | ◎ + | + | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| SPC + | ◎ + | + | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| SCSI HD/CD/MO Devices + | ○ + | + | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
XP とその向こうXP and beyonds+ ×
+ |
+ | 電源 | Power Circuit+ ○
+ |
+ | LUNA-88K specific
+ | MPU (88100 part)
+ | ○
+ | マルチプロセッサ未実装、バグも未実装? | MP (and bugs?) not implemented+ MPU (88200 part)
+ | ◎
+ |
+ | MPU (88110)
+ | —
+ | 実装予定なし | Not planned+ FUSEROM
+ | ○
+ |
+ | X68030
+ | MPU (68030)
+ | ○
+ | キャッシュ未実装、ファンクションコード未実装 | Cache and FC not implemented+ MPU (68EC030)
+ | —
+ | 実装予定なし | Not planned+ FPU (68881)
+ | ◎
+ | 68882 は未実装 | 68882 not implemented+ DMAC
+ | ○
+ |
+ | CRTC/VC
+ | △
+ | 768x512 のテキスト画面のみサポート | Only 768x512 text screen supported+ FDC/FDD
+ | ○
+ |
+ | 標準・拡張エリアセット | Areaset+ ×
+ |
+ | ADPCM/OPM
+ | ×
+ |
+ | グラフィック機能全般 | All other graphics+ ×
+ | 当面予定なし | Not scheduled+ Keyboard
+ | ◎
+ | TVコントロールを除く | Except TV Control+ Mouse
+ | ◎
+ | 本体接続のみ
+ | MFP
+ | △
+ |
+ | PPI
+ | △
+ |
+ | Printer
+ | ×
+ |
+ | RTC
+ | ◎
+ | アラームを除く | Except Alarm+ SPC
+ | ◎
+ |
+ | SCSI HD/CD/MO Devices
+ | ○
+ |
+ | SCC
+ | ◎
+ |
+ | SRAM
+ | ◎
+ |
+ | システムポート | System port+ △
+ |
+ | テキスト画面 | Text screen+ ○
+ |
+ | 電源 | Power curcuit+ ○
+ |
+ | Nereid Ethernet
+ | ×
+ |
+ | Nereid Bank memory
+ | ×
+ |
+ | Nereid USB
+ | —
+ | 実装予定なし | Not planned+ 拡張メモリ | Extended memory+ ×
+ |
+ | | ||||
68030 cache is not implemented. +Therefore, number of clock cycle is not correct. +ATC (Address Translation Cache) is differ from and faster than the real 68030.+ +
Status Panel
The performance meter's icon at the center of the status panel +shows the VM speed status. +You can switch full speed / syncronized mode by double-clicking +on this icon.+
+| …
+ |
+マークなしの場合、ユーザが等速モードを指定していて、等速モードで実行中です。
+ | When no icons are displayed, +the user has specified syncronized mode and +the VM is running in synchronized mode.+
+ | …
+ |
+三角3つの場合、ユーザが高速モードを指定していて、高速モードで実行中です。
+高速モード中はパーセントではなく何倍速で動作しているかを表します。
+ | When an icon (three triangles) is displayed, +the user has specified full speed mode and +the VM is running in full speed mode. + |
Key input mode
LUNA and X68030 has the Japanese keyboard +(though I ever heard there are US keyboard for LUNA...). +So nono provides two input modes +for Japanese keyboard users and non Japanese keyboard users. +Both have advantages and disadvantages.+
+JP キーボードモードは、ホストが日本語キーボードであることを前提に
+対応するキーの押下、開放をその都度 VM に入力します。
+メリットとしては動作が実機に近くなり、
+特にキーリピート(をハードウェアが行わないこと)も忠実に再現可能です。
+デメリットは ALT + TAB やアクセラレータキーでメニューを開く場合などに
+キー入力が残ることがあることです
+(キーを押した後でフォーカスが外れるとキーを離したことが
+アプリケーションに通知されないため)。
+またホストが日本語キーボードでなければ使いづらいです。
+JP keyboard mode assumes that the host uses the Japanese keyboard.
+Each time you presses and releases a key,
+nono sends the corresponding key-pressed or key-released to the VM.
+One advantage is that it's close to the real machine behavior,
+and another is that it can reproduce
+the LUNA keyboard itself does not perform a key repeat.
+On the other hand,
+one disadvantage is that key sometimes remains pressed,
+especially when you enter ALT + TAB to switch the application
+or enter accelerator key to open the menu
+(If the application loses the focus after the key is pressed,
+the application will not receive the subsequent key release).
+And another disadvantage is that
+it will be hard to use for non Japenese keyboard users.
+
+一方、キャラクタ入力モードは、ホストから入力された「文字」を
+再び LUNA/X68030 のキーコードに解釈し直して VM に入力するモードです。
+例えばゲスト OS に "@" を入力したい場合、
+US キーボードなら [SHIFT] + [2] を、
+JP キーボードなら [@] キーを押しますが、
+どちらも VM には [@] キーの押下、[@] キーの開放が連続して送られます。
+US キーボードで [SHIFT] を押したことは通知されません。
+逆に "=" を入力したい場合、
+US キーボードなら [=] キーを、
+JP キーボードなら [SHIFT] + [-] を押しますが、
+どちらも VM には
+[SHIFT]押下 → [-]押下 → [-]開放 → [SHIFT]開放のシーケンスが送られます。
+このようにホストキーボードのレイアウトによらず、
+入力したい文字が入力できるようになり、
+通常のタイピングで困ることはないと思います。
+デメリットは、通常の文字入力以外のタイピングはほぼ出来ないことです。
+[SHIFT] キーを押したままにすることや、
+文字が入力できないキーの組み合わせは入力出来ません。
+もう一つのデメリットはキーリピート(をハードウェアが行わないこと)が再現できず、
+ホスト側のキーリピートが効いてしまうことです
+(本来キーリピートが動作しない ROM やブートローダでもキーリピートが効くことは
+一般ユーザからはメリットに感じられるかも知れませんが)。
+In contrast, in the character mode, when you type a character,
+nono re-converts it into the LUNA/X68030's key code and sends it to the VM.
+For example if you want to type "@" in the guest OS,
+you would press [SHIFT] + [2] on the US keyboard or [@] on the JP keyboard.
+In both cases, the sequence of
+[@]-pressed and [@]-released will be sent to the VM.
+Note that the fact that you pressed [SHIFT] key on the US keyboard
+will not be sent to the VM.
+Another example, if you want to type "=",
+you would press [=] on the US keyboard or [SHIFT] + [-] on the JP keyboard.
+In both cases, the sequence of
+[SHIFT]-pressed, [-]-pressed, [-]-released, and [SHIFT]-released
+will be sent to the VM.
+Thus, you can type what character you want to type,
+regardless of your keyboard layout.
+Of course there are some disadvantages.
+Firstly, it's hard to type any special characters,
+for example, you can not type any key conbinations
+that don't generate a character.
+Or you can not hold [SHIFT] key pressed.
+Secondly, the key repeat works (by the host),
+even though it should not work as a correct emulation
+(Although some of you may feel it an advantage).
+
Keycode table in the character mode
The following table shows the correspondence between +the character that typed from the host +and the key that will be sent to the VM. +nono can recognize the function keys and arrow keys. +The keys that not listed in this table can +only be typed from the software keyboard window.+
+
| HostChar | GuestKey + |
|---|---|
| a 〜 z | [A] 〜 [Z] + |
| 0 〜 9 | [0] 〜 [9] + |
| SPACE | [SPACE] + |
| - | [-] + |
| ^ | [^] + |
| \ | [\] + |
| @ | [@] + |
| [ | [[] + |
| ; | [;] + |
| : | [:] + |
| ] | []] + |
| , | [,] + |
| . | [.] + |
| / | [/] + |
| HostChar | GuestKey + |
|---|---|
| A 〜 Z | [SHIFT]+[A] 〜 [SHIFT]+[Z] + |
| ! | [SHIFT]+[1] + |
| " | [SHIFT]+[2] + |
| # | [SHIFT]+[3] + |
| $ | [SHIFT]+[4] + |
| % | [SHIFT]+[5] + |
| & | [SHIFT]+[6] + |
| ' | [SHIFT]+[7] + |
| ( | [SHIFT]+[8] + |
| ) | [SHIFT]+[9] + |
| = | [SHIFT]+[-] + |
| ~ | [SHIFT]+[^] + |
| | | [SHIFT]+[\] + |
| ` | [SHIFT]+[@] + |
| { | [SHIFT]+[[] + |
| + | [SHIFT]+[;] + |
| * | [SHIFT]+[:] + |
| ] | [SHIFT]+[]] + |
| < | [SHIFT]+[,] + |
| > | [SHIFT]+[.] + |
| ? | [SHIFT]+[/] + |
| _ | [SHIFT]+[_] + |
| HostChar | GuestKey + |
|---|---|
| F1 〜 F10 | [PF1] 〜 [PF10] + |
| F11 | [PF10] + |
| ↑ | [↑] + |
| ← | [←] + |
| → | [→] + |
| ↓ | [↓] + |
| ^@ | [CTRL]+[@] + |
| ^A 〜 ^Z | [CTRL]+[A] 〜 [CTRL]+[Z] + |
| ^[ | [ESC] + |
| ^\ | [CTRL]+[\] + |
| ^] | [CTRL]+[]] + |
| ^^ | [CTRL]+[^] + |
| ^_ | [CTRL]+[_] + |
| ^H | [BS] + |
| ^I | [TAB] + |
| ^M | [Enter] + |
Keycode table in the JP keyboard mode
The following table shows the correspondence between +the host key and the guest key. +The keys that not listed in this table can only be enter from +the software keyboard window.+
+
| HostKey | GuestKey + |
|---|---|
| [0] 〜 [9] | [0] 〜 [9] + |
| [A] 〜 [Z] | [A] 〜 [Z] + |
| [-] | [-] + |
| [^] | [^] + |
| [\] | [\] + |
| [@] | [@] + |
| [[] | [[] + |
| [;] | [;] + |
| [:] | [:] + |
| []] | []] + |
| [,] | [,] + |
| [.] | [.] + |
| [/] | [/] + |
| [_] | [_] + |
| HostKey | GuestKey + |
|---|---|
| [ESC] | [ESC] + |
| [TAB] | [TAB] + |
| [CTRL] | [CTRL] + |
| [BS] | [BS] + |
| [Enter] | [Enter] + |
| [F1] 〜 [F10] | [PF1] 〜 [PF10] + |
| [F11] | [PF10] + |
| [SHIFT-L] | [SHIFT-L] + |
| [SHIFT-R] | [SHIFT-R] + |
| [↑] | [↑] + |
| [←] | [←] + |
| [→] | [→] + |
| [↓] | [↓] + |
| HostKey | GuestKey + |
|---|---|
| [DEL] | Numpad[DEL] + |
| Numpad[0]〜[9] | Numpad[0]〜[9] + |
| Numpad[+] | Numpad[+] + |
| Numpad[-] | Numpad[-] + |
| Numpad[*] | Numpad[*] + |
| Numpad[/] | Numpad[/] + |
| Numpad[=] | Numpad[=] + |
| Numpad[.] | Numpad[.] + |
| Numpad[Enter] | Numpad[Enter] + |
Key Repeat
On LUNA, +key repeat is done by software(OS), not by the keyboard hardware. +For this reason, +key repeat doesn't occur on LUNA's PROM or NetBSD/luna68k's bootloader +that don't implement it, and +key repeat occurs on NetBSD/luna68k kernel that implements it. +Since the timing of key repeat is measured by the guest software, +if the VM is running faster than the real, +the key repeat will occur faster, too. +The host application doesn't have the way to avoid it. +Therefore, nono will temporarily suppress the full speed mode +while any keys are pressed. +That is why the above-mentioned icon distinguishes them. +If keys continue to be pressed for some reasons, +the VM also continues to run syncronized mode. +In this case, you can resolve it by using the software keyboard window.+
Try it
Try NetBSD/luna68k
Tsutsui-san has provided a liveimage of NetBSD/luna68k 9.2.+ +ここではこれを起動してみます。
Let's try it.+
-% mkdir -p ~/nono/luna/ -% echo "vmtype=luna" > ~/nono/luna/nono.cfg -% path/to/nono -c ~/nono/luna +Create a directory somewhere for nono (for example ~/nono/), +and create subdirectories for individual VMs in it +(for example ~/nono/luna/).+ +- 以下のリンクからイメージファイルをダウンロードして展開し、 +VM ディレクトリ ~/nono/luna/ に置きます。 +
Download imagefile from the following link, +extract it and place it in the VM directory, ~/nono/luna/.++http://teokurebsd.org/netbsd/liveimage/20210910-luna68k/ ++ +- 以下の内容の設定ファイル nono.cfg を VM ディレクトリ ~/nono/luna/ +に作成します。 +ここでは説明を簡単にするためネットワークなしにしていますが、 +ネットワーク設定は必要に応じて行ってください。 +
Create a configuration file nono.cfg in the VM directory, ~/nono/luna/, +with following contents. +By the way, to simplify the explanation, we assume there is no network here. +However, please configure the network if necessary.++ ++vmtype = luna +spc0-id6-image = hd,liveimage-luna68k-with-packages-20210910.img +hostnet-driver = none +- nono -c ~/nono/luna で起動します +(VM ディレクトリに自動的に NVRAM.DAT が作られます)。 +
Run as nono -c ~/nono/luna. +(NVRAM.DAT will be created automatically in the VM directory)+ +- Emulated ROM Monitor が起動するので、 +初回は以下のように入力すると NetBSD が起動します。 +
The emulated ROM Monitor will be executed. +Then, only for the first time, +entering the following can boot NetBSD.++画面はこんな感じのはずです (太字が入力部分)。 ++k⏎ +⏎ +⏎ +d⏎ +boot⏎ +g⏎ +x⏎ +You will see a screen like this. The bold text indicates +the characters you need to enter.++この内容は NVRAM.DAT に記録されているので次回以降は直接 NetBSD が起動します。 ++NONO 0.4.0 Emulated ROM Monitor for LUNA-I + +** NVRAM Initialized. + +>k⏎ +controller: dk ?⏎ +drive unit: 0 ?⏎ +partition : c ?d⏎ +filename : vmunix ?boot⏎ +>g⏎ +Loaded. Entry point = $00700000 +>x⏎ +The information you have just entered is recorded in the NVRAM, +so next time it will boot NetBSD automatically.+- 初回起動時、 +Updating fontconfig cache はあほみたいに時間がかかりますが、 +nono がハングアップしてるわけではありません(>_<)。 +また初回は起動後数時間めちゃくちゃ重たいですが、 +これはバックグラウンドで makemandb が動くためで +nono のせいではありません(>_<)。 +
At the first boot, you will see the console stops after printing +"Updating fontconfig cache". +This is because the infamous fontconfig takes very looooong time. +nono would not have hang-up. +In addition, at the first boot, you will feel it's too heavy for several hours. +This is because the infamous makemandb(8) runs heavily in the background +for a looooong time. +It's very sad to me that these two accidents which are far from the ideal +are the first experiences of newcomers.+ +- 終了する時は root +ユーザで “shutdown -p now” を実行してください。 +LUNA はソフトウェアから電源オフでき、 +VM の電源オフで nono も終了します。 +
To quit, type “shutdown -p now” as the root user. +LUNA can be powered off by software, +and nono will terminate when the VM is powered off.+
Try OpenBSD/luna88k
Aoyama-san has provided a liveimage of OpenBSD/luna88k 7.0.+ +ここではこれを起動してみます。
Let's try it.+
Create a directory somewhere for nono (for example ~/nono/), +and create subdirectories for individual VMs in it +(for example ~/nono/luna88k/).+ +
Download liveimage-luna88k-raw-20211221.img.gz from the following link, +extract it and place it in the VM directory, ~/nono/luna88k/.+
+http://www.nk-home.net/~aoyama/liveimage/ ++ +
Create a configuration file nono.cfg in the VM directory, ~/nono/luna88k/, +with following contents. +By the way, to simplify the explanation, we assume there is no network here. +However, please configure the network if necessary.+
+ ++vmtype = luna88k +spc0-id6-image = hd,liveimage-luna88k-raw-20211221.img +hostnet-driver = none +
Run as nono -c ~/nono/luna88k. +(NVRAM.DAT will be created automatically in the VM directory)+
The emulated ROM Monitor will be executed. +Then, only for the first time, +entering the following can boot OpenBSD.+
+画面はこんな感じのはずです (太字が入力部分)。 ++nvram boot_filename boot⏎ +y +b⏎ +
You will see a screen like this. The bold text indicates +the characters you need to enter.+
+この内容は NVRAM.DAT に記録されているので次回以降は直接 OpenBSD が起動します。 ++NONO 0.4.0 Emulated ROM Monitor for LUNA88K + +** NVRAM Initialized. + +N>nvram boot_filename boot⏎ +Update boot_filename : "vmunix" -> "boot" (Y/[N]):y +Updated +N>b⏎ +
The information you have just entered is recorded in the NVRAM, +so next time it will boot OpenBSD automatically.+ +
To quit, type “shutdown -p now” as the root user. +LUNA-88K can be powered off by software, +and nono will terminate when the VM is powered off.+
Try NetBSD/x68k
Tsutsui-san has provided a liveimage of NetBSD/x68k 9.2. Let's try it.+
Create a directory somewhere for nono (for example ~/nono/), +and create subdirectories for individual VMs in it +(for example ~/nono/x68k/).+ +
Download your favorite one of plain-install or with-packages +from the following link, +extract it and place it in the VM directory, ~/nono/x68k/.+
+http://teokurebsd.org/netbsd/liveimage/20210613-x68k/ ++ +
Create a configuration file nono.cfg in the VM directory, ~/nono/x68k/, +with following contents. +You don't need to add the liveimage first time.+
+ ++vmtype = x68030 +
Run as nono -c ~/nono/x68k. +After a few seconds, a message will be displayed like this captured screen. +It says in Japanese that "Cannot boot from disk. Please set correct one". +Then, terminate the nono by "File > Exit" in menu or close button. +By this operation, SRAM will be initialized by X68030 IPLROM and +be saved as SRAM.DAT in the VM directory.+
Then, add a disk image downloaded earlier to configuration file nono.cfg +(see 2nd line).+
++vmtype = x68030 +spc0-id0-image = hd,liveimage-x68k-with-packages-20210613.hds
Again, run as nono -c ~/nono/x68k. +NetBSD/x68k will be booted from HDD. +Next time, it will boot NetBSD automatically.+ +
At the first boot, you will feel it's too heavy for several hours. +This is because the infamous makemandb(8) runs heavily in the background +for a looooong time. +It's very sad to me that an accident which is far from the ideal +is the first experiences of newcomers.+ +
After NetBSD boots up (more precisely, if powerd(8) is running), +you can shutdown and power off by +"Device > Operation > Push Power button" on menu, +and nono will terminate when the VM is powered off.+ +
Setup network
Example of host network setup
Add the following line to configuration file, nono.cfg. +(Although you don't need to write it since these are default behavior +on NetBSD)
-を追加し、VM ディレクトリに nono-ifup、nono-ifdown -というスクリプトを用意してください。 -nono は tap(4) をオープンし、 -そのデバイス名を引数にこれらのスクリプトを呼びます。 --ethernet-hostdriver = tap +hostnet-driver = tap +hostnet-tap-devpath = auto
-最もシンプルなケースだとおそらく + +
By default, /dev/tap is only accessible to privileged user. +You need to chmod /dev/tap (without unit number) appropriately. +Note that upgrading using sysinst always reset the permission to 600.+ +
Create a bridge(4) interface, and +add your physical interface to the bridge.
-のようにして用意しておいた bridge0 に対して、 -(sudo の設定は別途行ってから) -次のような nono-ifup、nono-ifdown を用意すれば -wm0 の物理セグメントとブリッジできると思います。 +常用するなら /etc の設定ファイルに書いておきましょう。 +-# brconfig bridge0 create +# ifconfig bridge0 create # brconfig bridge0 add wm0
If you use it regularly, +you can put configuration file into /etc.+
+/etc/ifconfig.bridge0 +++create +up +!/sbin/brconfig $int add wm0 +++# /etc/rc.d/network restart ++
Return to non-privileged user, and +create following two scripts in the VM directory or its parent directory. +nono will open tap(4) and +invoke these scripts with the name of the device as an argument. +In addition, you need to set up sudo separately.
nono-ifup#!/bin/sh -sudo ifconfig $1 up -sudo brconfig bridge0 add $1 +sudo /sbin/ifconfig $1 up +sudo /sbin/brconfig bridge0 add $1
-nono-ifup +nono-ifdown+ +#!/bin/sh -sudo brconfig bridge0 delete $1 -sudo ifconfig $1 down +sudo /sbin/brconfig bridge0 delete $1 +sudo /sbin/ifconfig $1 down +
++% chmod +x nono-ifup nono-ifdown
Run nono, +and open "Monitor > Host > Host Network" window from menu. +It's OK if you can see "HostNet Driver: tap".+ +
Known Issues
In debugger console, some special characters like backspace or cursor keys +aren't printed correctly.+(since ver 0.3.0) +
If the host OS is running on VirtualBox (on Windows?) and +"Mouse integration" on VirtualBox is enabled, +the mouse pointer will not move as expected in nono's Mouse Mode.+(2021/12/30) + +
On Wayland, window size may be incorrect. +This may be due to wxWidgets (3.0.5) bug.+(2021/12/30) + +
If there are nono's sub windows or other windows near the center of +the main window, you will not enter the mouse mode.(since ver 0.0.2) + +
How to migrate from old versions
Some versions may have incompatibilities in the configuration files, etc. +In such case, you may need to upgrade it by referring the following link.+ +
Changes
Contact, License, etc
License
nono uses X68030 IPLROM image distributed without charge. +You must read +the license agreement +(even though it's Japanese original text only).+
Contact us
If you find any problems, please let me know. +You may write in English.
About contributes
If you provide a patch to nono, we assume that you agree the following +conditions:+
All your work are operated or distributed under the nono license.+
The license may be changed in the future.+
Do not exercise your author's rights.+
nono uses source code with the following advertising clause.+
+This product includes software developed by Gordon Ross+
+This product includes software developed by the University of California, Lawrence Berkeley Laboratory.
+
Note
This is alpha quality release. -All specifications on this page may be changed -without compatibility in the near future.