Hi,
Johnson Lam escribió:
On Fri, 3 Dec 2004 06:52:17 +0300 (MSK), you wrote:
Make next file (say, DUMP.DBG):
d c000:0,
d d000:0,
d e000:0,
q
then run DEBUGDUMP.DBGDUMP.RES (without quotes) and you get dump in file
DUMP.RES. Be carefull - its size is 970k, so archive it before
On Fri, 03 Dec 2004 10:56:35 +0100, you wrote:
Hi Aitor,
Am I miss anything?
The redirection signs :-)
Thanks for detail explain.
I'll post the result in my homepage tonight (6 hours later), with
other dumped data from different mainboard.
Rgds,
Johnson.
Hi Johnson, talking about testing-in-emulation...
Maybe also explained why there's no DOS client can mount
a linux or SAMBA client.
There are LTOOLS. Works like MTOOLS: Special programs, which are
like copy, dir, ..., but which can use Linux drive letters.
For Samba, I guess there is only
If there is anybody who has tried to use USBASPI.SYS and EMM38, has
had USBASPI.SYS reboot immediately with EMM386 loaded, AND wants to
try a test EMM386 to get around the reboot, let me know and I'll send
on a copy for you to try.
Well, stupid of me I did not test that on my images. Because
Hi!
3--2004 13:19 [EMAIL PROTECTED] (Johnson Lam) wrote to
[EMAIL PROTECTED]:
JL to me ... How to dump c000-efff. Or any other information is useful?
Make next file (say, DUMP.DBG):
d c000:0,
d d000:0,
d e000:0,
q
then run DEBUGDUMP.DBGDUMP.RES (without quotes) and you get dump
Hi!
3--2004 15:35 [EMAIL PROTECTED] (Johnson Lam) wrote to
[EMAIL PROTECTED]:
JL If they're not for money or reputation, they should relax their limit.
Dura lex, sed lex. Law applied notwitstanding, if there is (explicit)
lost of money/reputation. Issue is only will someone raise sue or
If there is anybody who has tried to use USBASPI.SYS and EMM38, has
had USBASPI.SYS reboot immediately with EMM386 loaded, AND wants to
try a test EMM386 to get around the reboot, let me know and I'll
send on a copy for you to try.
Hi Michael,
I guess I was the only one posted the
On Fri, 3 Dec 2004 17:50:38 +0300 (MSK), you wrote:
Hi,
Dura lex, sed lex. Law applied notwitstanding, if there is (explicit)
lost of money/reputation. Issue is only will someone raise sue or not.
In western world like US, maybe someone will think carry out the law
is most important, but
Hi there,
I have started reading EMM386.ASM (not the latest hot version, but the
previous one, not many changes I assume), and although I haven't yet
finished, I think I'd need a couple of hints on some things there. BTW
quite an interesting pierce of work! :-)
I suppose some of them are
Hello Aitor,
I leave the rest to michael, but
(4) What are those special comments/marks for? What are they indicating?
They are all over the sources
; (*-9-*)
; (#-9-#)
that's historic, kind of pre-diff;
it was published (printed) in several versions, and the later ones
had
; (*-9-*)
Aitor Santamaría Merino wrote:
I can't answer anything emm386 specific, but maybe this'll help a little
until Michael/Tom/? answers.
Hi there,
I have started reading EMM386.ASM (not the latest hot version, but the
...
(2) What is the meaning of this structure? How much memory does it
weight
Hi, comment on 40:72 -
MEM 0040h:0072h - POST RESET FLAG
which can be 0, 1234h, and a few other values.
I think this should be 40:7b instead -
MEM 0040h:007Bh - INT 4Bh FLAGS (PS2 and newer)
5 set if Virtual DMA Spec supported [PS] (see INT 4B)
3 set if INT 4Bh intercepted and must
Hi!
3--2004 19:53 [EMAIL PROTECTED] (tom ehlert) wrote to Aitor Santamara
Merino [EMAIL PROTECTED]:
(5) In the startup of the driver, it is set 00AAh into memory
0040h:0072h, but I can't find references to this BIOS variable, what is
that?
te it's LPT4. and scince ther's no LPT4, it's abused
Hi!
3--2004 19:12 [EMAIL PROTECTED] (Aitor Santamara Merino) wrote to
[EMAIL PROTECTED]:
ASM (2) What is the meaning of this structure? How much memory does it
ASM weight actually, or how does the assembler determine that? (the bit that
ASM I ignore is the (?))
ASM RES_STACK SEGMENT PARA USE16
On Fri, 03 Dec 2004 18:03:29 +0800, you wrote:
Hi,
Due to web server problem, I can't FTP into my account.
The file will be available on my friends server:
1) HP (ASUS KL97-XV Rev 1.04) Pentium3-266MHz (No SCSI)
http://home.thinkpat.com/~johnson/store/asus-kl97-xv.zip
2) Iwill XA 100plus -
Hi!
4--2004 00:43 [EMAIL PROTECTED] (Johnson Lam) wrote to
[EMAIL PROTECTED]:
Dura lex, sed lex. Law applied notwitstanding, if there is (explicit)
lost of money/reputation. Issue is only will someone raise sue or not.
JL In western world like US, maybe someone will think carry out the law
At 07:12 PM 12/3/2004 +0100, Aitor Santamaría Merino wrote:
Hi there,
I have started reading EMM386.ASM (not the latest hot version, but the
previous one, not many changes I assume), and although I haven't yet
finished, I think I'd need a couple of hints on some things there. BTW
quite an
...
It was more interesting to have ATAPICDD in NASM, but I am not sure if
the port has the same maturity as the original MASM/TASM version. At least
it helps to test patches for ATAPICDD that it can be compiled with free
compilers / assemblers. But you still need spare time for that :-(.
...
Hi,
Michael Devore escribió:
As it is currently a quite active development project, any nontrivial
changes to EMM386 unrelated to fixing a verified bug should be sync'ed
through me or Tom. Unannounced code changes to EMM386 could make
Michael cry and misbehave.
Sure :)
Aitor
Hi,
Kenneth J. Davis escribió:
...
It was more interesting to have ATAPICDD in NASM, but I am not sure if
the port has the same maturity as the original MASM/TASM version. At
least
it helps to test patches for ATAPICDD that it can be compiled with free
compilers / assemblers. But you still need
Aitor Santamaría Merino schreef:
Could you extend a little bit on this?
ATASPI for the ATAPI/ASPI layer and CDROM over it (which means I need to
load two drivers, isn't it?), or
ATASPI for ASPI CD-ROM, and CD-ROM for ATAPI or...?
And in this case, CDROM will be the char device and ATASPI a
Aitor Santamaría Merino wrote:
...
actually current ATAPICDD, which is now split into cdrom.sys
ataspi.sys to separate the CD code from the IDE/ATAPI code uses
FASM.
Could you extend a little bit on this?
ATASPI for the ATAPI/ASPI layer and CDROM over it (which means I need to
load two drivers,
Kenneth J. Davis schreef:
As CD-ROMs are controlled by what are essentially SCSI packets over an
ATA(IDE) interface, using ASPI makes a convenient method to separate
them allowing me to use a SCSI card or existing CD driver for testing.
Jeremy
Quite smart thinking to split up the driver into
On Sat, 4 Dec 2004 00:07:55 +0300 (MSK), you wrote:
Hi,
I think, your local judges not think so (unless they are corrupted :).
Judges may not. Before judges maybe :-)
Sure, experienced lawyer may find very strange reasons to sue you. :)
;( For example: distribution of materials,
Hi,
From Jason Hood's DOSLFN page:
FreeDOS has a problem with extended DPBs, which causes problems with
XMSDSK (DOSLFN thinks the RAMdisk is FAT32). Here is a FreeDOS patch
and kernel (build 2034, NASM 0.98.38, Borland C++ 3.1, TLINK 7.01,
386) to fix it.
Still have the bug in 2035a or
25 matches
Mail list logo
