> > > >Is doscmd working for anyone on current? Here I just get:
> > > >
> > > >---------
> > > >
> > > >I have tried it on a single processor and SMP -current and both do the same
> > > >thing. I had it working a while back, so I think my configuration is ok.
> > > >
> > > >Ideas on how to look into this?
> > > 
> > > Start by invoking it with the various debug/trace options.  I'd guess
> > > that it may be broken by the signal-related changes that were made
> > > recently.
> > 
> > hehehe It dies at the very first vm86 instruction, so I guess something
> > isn't setup correctly to enter vm86 mode via the sigreturn():
> 
> I bet that someone got smart and disallowed PSL_VM in eflags on a 
> return to user-mode.

Nope it wasn't that bad. I'm not sure if this is the correct fix, but
with this patch I can boot dos again. Can someone with more knowledge
of the signal stuff look and say if this is correct/enough?

The redirector don't work though. I just get a "File not Found" error
when trying to dir any of the redirected directories.

John
-- 
John Hay -- [EMAIL PROTECTED]


Index: doscmd.c
===================================================================
RCS file: /home/ncvs/src/usr.bin/doscmd/doscmd.c,v
retrieving revision 1.11
diff -u -r1.11 doscmd.c
--- doscmd.c    1999/10/13 23:48:35     1.11
+++ doscmd.c    1999/11/07 12:50:06
@@ -258,6 +258,7 @@
 
     sigemptyset(&uc.uc_sigmask);
     sigaltstack(NULL, &uc.uc_stack);
+    uc.uc_mcontext.mc_onstack = uc.uc_stack.ss_flags;
 
     if (tmode)
        tracetrap(REGS);


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to