Opened 13 years ago
Closed 8 years ago
#10439 closed defect (obsolete)
Keyboard doesn't work in NetOp Remote Control OS/2-eCS clients
Reported by: | Rafcio | Owned by: | |
---|---|---|---|
Component: | guest control | Version: | VirtualBox 4.1.10 |
Keywords: | Cc: | ||
Guest type: | other | Host type: | Windows |
Description
Keyboard doesn't work in virtual OS/2-eCS clients remotely controlled through NetOp Remote Control. Since NetOp Remote Control is probably the only available remote control solution for OS/2 and eCS hosts, it should get a high priority to get this fixed. I REALLY need a remote control for virtual OS/2 clients and all other solutions have serious bugs (mostly mouse issues). I'm not sure if they still have OS/2 Host code (installed on the controlled host) available (I have it from the old days when I was an OS/2 engineer for a major financial company) and there is no more OS/2 Guest (installed on controlling host) available, so Windows Guest needs to be used for remote control. I can provide the OS/2 Host code for testing and the Windows serial numbers should work for it, or I can provide that too. BTW, these lines from VBox.log are wrong: 00:00:05.397 File system of 'D:\VirtualBox\RRSOAS01VM\RRSOAS01VM_1.vdi' is ntfs 00:00:05.400 File system of 'D:\VirtualBox\RRSOAS01VM\RRSOAS01VM_2.vdi' is ntfs The file system if JFS, not NTFS.
Attachments (1)
Change History (2)
by , 13 years ago
comment:1 by , 8 years ago
Resolution: | → obsolete |
---|---|
Status: | new → closed |
Please reopen if still relevant with a recent VirtualBox release.
Client log.