Re: Bug in the latest version
Hello. Bart Oldeman wrote: a) the DOS time is the same as in the previous PIC call. PIC schedules the next activation time and then works in polling mode to see when that time is reached. Even when it reached, there are no guarantees that it is possible to fire the int right away, so it can keep waiting. So it is OK when the activation time doesn't change for the several PIC polling cycles. b) IP is increased by 1 (c000:0009-c000:000a) for no apparent reason. Some priviledged 1-byte instr was emulated? Namely, the PIC call before the one above does this: I really wouldn't suspect PIC in that case. PIC deals with an async stuff and it was the constant source of the random crashes, but for the 100% predictable crashes it wasn't caught responsible yet (by me at least). Looking at this: c:\wp51\wp exit wp c:\wp51\wp Then, Dosemu exits with an error message. the crash happens on the (second) startup and at startup we have an exepack, that's why it seems more reasonable to suspect it, together with the fact that I am using the unpacked wp.exe and can't reproduce the problem... - To unsubscribe from this list: send the line unsubscribe linux-msdos in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: dosemu-1.1.3.5 for testing.
On Sun, 27 Oct 2002 01:59:47 -0400 (EDT)
Bart Oldeman [EMAIL PROTECTED] wrote:
it's available at
http://www.dosemu.org/testing
When compiling with plugin_keyboard instead of plugin_kbd_unicode
I get error:
...
gcc -c -D_GNU_SOURCE -O2 -fomit-frame-pointer -MD -mcpu=i586 -fno-strict-aliasing
-DGCC_VERSION_CODE=3002 -DASM_PEDANTIC -DGLIBC_VERSION_CODE=2002 -D_XOPEN_SOURCE -pipe
-DUSING_NET -Wall -I/usr/src/RPM/BUILD/dosemu-1.1.3/src/plugin/keyboard/include
-I/usr/src/RPM/BUILD/dosemu-1.1.3/src/include
-I/usr/src/RPM/BUILD/dosemu-1.1.3/src/dosext/dpmi -I/usr/include/slang
-I/usr/X11R6/include -DYYPURE -o lex.yy.o lex.yy.c
lexer.l: In function `real_yylex':
lexer.l:489: `KEYB_TR' undeclared (first use in this function)
lexer.l:489: (Each undeclared identifier is reported only once
lexer.l:489: for each function it appears in.)
make[2]: *** [lex.yy.o] Error 1
make[2]: Leaving directory `/usr/src/RPM/BUILD/dosemu-1.1.3/src/base/init'
make[1]: *** [base/init] Error 2
make[1]: Leaving directory `/usr/src/RPM/BUILD/dosemu-1.1.3/src'
make: *** [default] Error 2
Should KEYB_TR be defined in some other place too, or I have to use
plugin_kbd_unicode ?
Or I can safely remove next part from lexer.l.in ?
---
tr MAY_BE { yylval-i_value = KEYB_TR;
return(KEYB_LAYOUT); }
--
Grigory Batalov.
-
To unsubscribe from this list: send the line unsubscribe linux-msdos in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: dosemu-1.1.3.5 for testing.
Grigory Batalov writes:
Grigory Should KEYB_TR be defined in some other place too, or I
Grigory have to use plugin_kbd_unicode ?
Old keyboard code don't has turkish lauout. :(
Grigory Or I can safely remove next part from lexer.l.in ? --- tr
Grigory MAY_BE { yylval-i_value = KEYB_TR; return(KEYB_LAYOUT); }
Better move it to src/plugin/kbd_unicode/config/plugin_lexer
--
Sergey Suleymanov
P.S. Why do you use plugin_keyboard instead of plugin_kbd_unicode?
Any troubles with it?
-
To unsubscribe from this list: send the line unsubscribe linux-msdos in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
display multi-character under dosemu
Hi to the list member, Currently, I have an old clipper program need to run on DOSEMU to access my data stored in the Novell 4.11 server, it works properly, however the multi-character Chinese big5 font can not display properly. I am using the following command to invoke the terminal console: /usr/X11R6/bin/rxvt -im xcin -bg black -fg white -fm taipei16 -pt Root -km big5 then the dosemu and finally the the clipper exe. I am sure the console has no display problem, I use some xbase compiler CLIP to write up a small program to run directly from my Linux box to access the same data from my novell server. It works as expected. However after calling the dosemu and my old clipper application, it displays differently. I am running the RedHat 7.3 and it should be i18N ready and is capable of working different language. If some one has any ideas, please drop me a note! Thanks!! Best Regards Gene Leung - To unsubscribe from this list: send the line unsubscribe linux-msdos in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
IPX networking
These are my IPX nets: solt:~# cat /proc/net/ipx_interface NetworkNode_Address Primary Device Frame_Type 0111 0001 Yes Internal None 0777 00A0D216FF6B No eth1 802.3 0555 00C026A1AA2A No eth2 802.3 0666 00104B386E81 No eth0 802.3 0999 00A0D216FF6B No eth1 EtherII solt:~# cat /proc/net/ipx_route NetworkRouter_Net Router_Node 0333 0777 00C095E809B5 0999 Directly Connected 0666 Directly Connected 0555 Directly Connected 0777 Directly Connected 0111 Directly Connected When I run dosemu without root privs, it says: (here 333 is internal net of the native NetWare server) ERROR: IPX: Failure adding route 0333 through 0111:0001 Is this ok? Why not 0777:00C095E809B5? -- Sergey Suleymanov - To unsubscribe from this list: send the line unsubscribe linux-msdos in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: dosemu-1.1.3.5 for testing.
On Sun, 27 Oct 2002 01:59:47 -0400 (EDT)
Bart Oldeman [EMAIL PROTECTED] wrote:
it's available at
http://www.dosemu.org/testing
Also mkbindist-related part (sed) of patch-1.1.3.5 seems to be
broken. You should apply this patch.
--
Grigory Batalov.
--- dist/mkbindist.orig Mon Oct 28 16:10:11 2002
+++ dist/mkbindist Mon Oct 28 16:13:04 2002
@@ -77,7 +77,7 @@
#perl -pe \
#
's/^(\$_debug\s+=\s+\-a)/$1+c/;s/^(\$_rdtsc\s+=\s+\()on/$1off/;s/^(\$_dpmi\s+=\s+\()off/${1}0x2000/'
\
# ../etc/dosemu.conf $TMP/conf/dosemu.conf
-sed -e 's/^\(\$_rdtsc[[:space:]]*=[[:space:]]*(\)on/\1off/' |
+sed -e 's/^\(\$_rdtsc[[:space:]]*=[[:space:]]*(\)on/\1off/' ../etc/dosemu.conf
+$TMP/conf/dosemu.conf
for i in $BLIST; do
cp -p $BIN/$i $TMP/bin
Re: IPX networking
Hello.
Sergey Suleymanov wrote:
When I run dosemu without root privs, it says: (here 333 is
internal net of the native NetWare server)
ERROR: IPX: Failure adding route 0333 through
0111:0001
Is this ok?
Doesn't look healthy to me.
Does this patch help?
Patch is completely untested, but it compiles:)
--- src/dosext/net/net/ipxglt.c Sun Oct 27 17:35:39 2002
+++ src/dosext/net/net/ipxglt.c Mon Oct 28 19:03:27 2002
-109,8 +109,20
sscanf(proc_str, %s %s, proc_net, proc_node);
close_proc_scan();
- if (strcmp(buf_net, proc_net) || strcmp(buf_node, proc_node))
- return 0;
+ if (strcmp(buf_net, proc_net) || strcmp(buf_node, proc_node)) {
+ open_proc_scan(/proc/net/ipx_interface);
+ proc_str = get_proc_string_by_key(buf_net);
+ if (!proc_str) {
+ close_proc_scan();
+ return 0;
+ }
+ if (!strstr(proc_str, Internal)) {
+ close_proc_scan();
+ return 0;
+ }
+ close_proc_scan();
+ /* fall through */
+ }
return 1;
}
ms-dos w/dosemu
I'm very new to linux and am trying to use dosemu to network into an NT Domain. Unfortunately, even after downloading a version of Lan Manager that boasts 'FreeDos' compatibility, I still receive an Incorrect DOS Version error every time Net Services attempt to load. Is there any documentation on networking (NETBEUI) using dosemu? Also, is it possible to install MS-DOS instead of FreeDOS under dosemu? Thanks. -Joshua Gaines - To unsubscribe from this list: send the line unsubscribe linux-msdos in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Bug in the latest version
Bart Oldeman [EMAIL PROTECTED] writes: On Sun, 27 Oct 2002, Lars Bjørndal wrote: I've noticed that if I use dosemu-1.0.1, the mem-command gives, in the line largest executable program size 617K, 1.1.3.5, the same command and config gives 611K. Why, do you think? This problem was caused by that thing that 1.1.3.5 will not use the autoexec.emu. I've replaced it with autoexec.bat now, and then it's ok. Why will not .emu work? My config.emu's last lines is: SHELL=C:\DOS\COMMAND.COM C:\DOS\ /e:1024 /p install=c:\subst.exe i: c:\ install=c:\lredir.exe c: linux\fs/dos Witn dosemu-1.0.1, it is the autoexec.emu on the new drive c: that is executed. Lars -- Lars Bjørndal [EMAIL PROTECTED] Storetveitåsen 15, 5067 Bergen. Tlf.: 55 28 87 55 Mobil: 958 37 537 Telefaks: 55 28 40 67 - To unsubscribe from this list: send the line unsubscribe linux-msdos in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Bug in the latest version
Thank you! Now, wp.exe works perfect! Lars Bart Oldeman [EMAIL PROTECTED] writes: On Sun, 27 Oct 2002, Lars Bjørndal wrote: How do I unpack the wp.exe-file? try this: http://www.mirror.ac.uk/sites/ftp.simtel.net/pub/simtelnet/msdos/execomp/unp411.zip I don't completely understand the log so I couldn't reply anything useful so far. The last lines of your log look like this: INT21 (0) at c000:1508: AX=3300, BX=0001, CX=, DX=0001, DS=c000, ES=c000 int 0x21, ax=0x3300 DO_VM86, cs=0133:109e ss=c000:00f4 f=00033002 ax=3300 bx=0001 ss=c000 sp=00f4 bp= cx= dx=0001 ds=c000 cs=0133 ip=109e si=13fb di=0162 es=c000 flg=00033002 RET_VM86, cs=c000:c009 ss=c000:00ee f=000b3217 ret=0x1 ax=8f11 bx=bf06 ss=c000 sp=00ee bp= cx=2352 dx=0001 ds=09e8 cs=c000 ip=c009 si=e451 di=8208 es=c000 flg=000b3217 PIC: 0 32 fffafff9 Activate ++ dos time to 176073668 DO_VM86, cs=c000:c00a ss=c000:00ee f=000b3217 ax=8f11 bx=bf06 ss=c000 sp=00ee bp= cx=2352 dx=0001 ds=09e8 cs=c000 ip=c00a si=e451 di=8208 es=c000 flg=000b3217 SIGILL while in vm86() ERROR: unexpected CPU exception 0x06 err=0x cr2= while in vm86 (DOS) Program=sigsegv.c, Line=202 EIP: c000:c3cf ESP: c000:18e2 VFLAGS(b): 0 00110010 0110 EAX: 6f04 EBX: a0aa ECX: f16a EDX: VFLAGS(h): 3206 ESI: 8f79 EDI: 8208 EBP: e0e2 DS: 09e8 ES: 372a FS: GS: FLAGS: PF IF RF VM VIF IOPL: 3 essentially the PIC is the last thing handled before the crash and Stas knows the PIC better than I do. What looks suspicious (though maybe it might be completely logical to the DOSEMU PIC experts) is that a) the DOS time is the same as in the previous PIC call. b) IP is increased by 1 (c000:0009-c000:000a) for no apparent reason. Namely, the PIC call before the one above does this: RET_VM86, cs=fdc8:6c52 ss=0133:0916 f=000b3286 ret=0x2f02 ax=111b bx=03c0 ss=0133 sp=0916 bp=0444 cx= dx=3601 ds=0133 cs=fdc8 ip=6c52 si=00b0 di=00b0 es=036a flg=000b3286 Do INT0x2f: Using caller_function() INT2F at fdc8:6c52: AX=111b, BX=03c0, CX=, DX=3601, DS=0133, ES=036a MFS: Entering dos_fs_redirect, FN=1B .. bunch of MFS stuff PIC: 0 32 fffafff9 pic_itime[1]= 176096631 PIC: 0 32 fffafff9 pic_sys_time set to 176073668 PIC: 0 32 fffafff9 Activate ++ dos time to 176073668 DO_VM86, cs=fdc8:6c52 ss=0133:0916 f=000b3287 Bart - To unsubscribe from this list: send the line unsubscribe linux-msdos in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html -- Lars Bjørndal [EMAIL PROTECTED] Storetveitåsen 15, 5067 Bergen. Tlf.: 55 28 87 55 Mobil: 958 37 537 Telefaks: 55 28 40 67 - To unsubscribe from this list: send the line unsubscribe linux-msdos in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: ms-dos w/dosemu
Hi there, On Mon, 28 Oct 2002, Joshua Gaines wrote: Thanks for the quick response. That's OK, but please cc the list. Private mail is generally deprecated unless invited. We've actually got an old FoxPro system that runs under DOS. I guess what I'm looking for then are the instructions for installing MS-DOS to replace the FreeDOS install that dosemu uses by default. From the (old) docs: -- you just can have a Linux directory containing all what you want to have under your DOS C:. Copy your IO.SYS, MSDOS.SYS or what ever to that directory (e.g. /var/lib/dosemu/bootdir), put $_hdimage = bootdir into your /etc/dosemu.conf, and up it goes. -- Does that help? 73, Ged. - To unsubscribe from this list: send the line unsubscribe linux-msdos in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Bug in the latest version
On Mon, 28 Oct 2002, Lars Bjørndal wrote: Bart Oldeman [EMAIL PROTECTED] writes: On Sun, 27 Oct 2002, Lars Bjørndal wrote: I've noticed that if I use dosemu-1.0.1, the mem-command gives, in the line largest executable program size 617K, 1.1.3.5, the same command and config gives 611K. Why, do you think? This problem was caused by that thing that 1.1.3.5 will not use the autoexec.emu. I've replaced it with autoexec.bat now, and then it's ok. Why will not .emu work? My config.emu's last lines is: SHELL=C:\DOS\COMMAND.COM C:\DOS\ /e:1024 /p install=c:\subst.exe i: c:\ install=c:\lredir.exe c: linux\fs/dos Witn dosemu-1.0.1, it is the autoexec.emu on the new drive c: that is executed. Well you can use SHELL=C:\DOS\COMMAND.COM C:\DOS\ /e:1024 /p /k C:\AUTOEMU.BAT and use AUTOEMU.BAT instead of AUTOEXEC.BAT. The problem with $_emubat, is that while it seems to work using some OS'es, some COMMAND.COM's and some types of AUTOEXEC.BAT it is really a hack and can be confusing. All kinds of weird things were possible such as: * command.com simply crashing DOSEMU (this is what the FreeDOS command.com did) * command.com executing autoexec.emu for the first half and autoexec.bat for the second half if the number of estimated fakes was not correct. * you doing type autoexec.bat and getting the contents of autoexec.emu. * potentially deleting or renaming the wrong file. $_emusys is a hack too, but it's more predictable what the DOS does (only one fake is needed) and it cannot be worked around so easily (only using bootmenu's and keystrokes or a separate boot directory). BTW if /K doesn't work you can use isemu.com in autoexec.bat: isemu if errorlevel 1 goto native_dos call autoemu.bat exit :native_dos Bart - To unsubscribe from this list: send the line unsubscribe linux-msdos in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: IPX networking
Stas Sergeev writes: Stas Doesn't look healthy to me. Does this patch help? It does. Thanks. Stas Patch is completely untested, but it compiles:) Well, it has tested now. :) -- Sergey Suleymanov - To unsubscribe from this list: send the line unsubscribe linux-msdos in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
