Hal, Why don't you try starting XWin without the '/B'. The '/B' is no longer necessary because XWin.exe should start as a Windows application, thus it should give the command line back immediately. Thus part of your problem might be that your xterm is starting too soon. Throw a 'sleep 5' in after your 'start XWin' line.
As a further test, remove the 'run' from the 'run xterm' command line. That will allow xterm to dump any errors to the console (it will prevent wmaker from starting though). You could also just change 'run xterm' to 'start /B xterm', which would put xterm in the background but still print its messages to the launching console. Let us know what happens, Harold "ROTTENBERG,HAL (HP-USA,ex1)" <[EMAIL PROTECTED]> said: > Since upgrading, Xterm will not open. Other X apps seem to work fine. I > will see a brief flicker of xterm trying to open (from my startwin.bat file) > then its gone. I'm using the wmaker WM. If I use the run command, either > nothing happens, or wmaker crashes. I've looked around a bit for any sort > of logs but haven't found anything so far. > > The pertinent part of my startwin.bat file is very simple: > > start /b XWin -unixkill > run xterm -sl 1000 -sb -rightbar -ms red -fg yellow -bg black -e > /usr/bin/bash > run wmaker > > What did I do wrong?? > > Hal Rottenberg | Email: [EMAIL PROTECTED] > Technical Support Engineer | Jabber: [EMAIL PROTECTED] > http://www.hp.com/security | Phone: +1-404-774-4041 > HEWLETT-PACKARD > >
