emu built from google code
... with some helpful pointers regarding awk, I figured out most of the problems with my build environment.
I've built emu for Nt under VC2005 on XP, with the Windows Server 2003 R2 SDK, and these instructions: https://umdrive.memphis.edu/blstuart/htdocs/msvc8.html
While emu compiles and works, it takes a year-and-a-day (~10 minutes) to present the prompt. At that point,
I can run the various commands, etc, but upon launching wm/logon, I get just the gray "inferno desktop"
window, with nothing on it. Typing "inferno" and pressing enter gets me a blank desktop with the Log
window, but nothing else. Definately no "start" menu. I also get the following output on the console:
C:\Users\Inferno\20080416>emu -rc:/users/inferno/20080416 -pmain=1000000 -v
Inferno Fourth Edition (20080416) main (pid=9168) interp
Initial Dis: "/dis/emuinit.dis"
; wm/wm wm/logon
tk: font not found: /fonts/pelm/unicode.8.font
tk error on 'menubutton .toolbar.start -menu .m -borderwidth 0 -bitmap vitasmall
.bit': !failed to load bitmap
tk error on 'pack .toolbar.start -side left': !bad window path .toolbar.start
wmclient: tk error !failed to load bitmap on 'button .Wm_t.e -bitmap exit.bit -c
ommand {send wm_title exit} -takefocus 0'
wmclient: tk error !bad window path .Wm_t.e on 'pack .Wm_t.e -side right'
wmclient: tk error !failed to load bitmap on 'button .Wm_t.top -bitmap task.bit
-command {send wm_title task} -takefocus 0; pack .Wm_t.top -side right'
wmclient: tk error !failed to load bitmap on 'button .Wm_t.m -bitmap maxf.bit -c
ommand {send wm_title size} -takefocus 0; pack .Wm_t.m -side right'
tk error on 'text .cons.t -width 60w -height 15w -bg white -fg black -font /font
s/misc/latin1.6x13.font -yscrollcommand {.cons.scroll set}': !failed to open fon
t
tk error on 'pack .cons.t -fill both -expand 1': !bad window path .cons.t
It's almost like some modules aren't finding things in the root. I have the fonts installed and stuff. "ls
/fonts/pelm" shows that the unicode.8.font is in place, and similarly, the various .bit's are where they
(Continue reading)