Back to home page

DOS ain't dead

Forum index page

Log in | Register

Back to index page
Thread view  Board view
DOS386(R)

01.05.2008, 04:59
 

MOV RIP,POASM (Developers)

http://openwatcom.org/index.php/Wasm No notice of JWASM yet :confused:

http://japheth.de/JWasm.html

Japheth wrote:

> JWasm is a fork of Open Watcom's WASM v1.7. It's intended to be a
> MASM v6 compatible, open source assembler.

Great :-)

Since JWASM has made such phenomenal progress in recent 1+1/2 months, the famous (but not really working) PO-ASM can now be considered as obsolete and dead, right ? :lol:

Tried to compile HIMEMX, but doesn't work, see shot :-( ... hoping for later versions

[image]

Tried also IDECHECK, also buggy, JWASM seems to dislike LEA insctruction (or was it the extremely "good" OFFFFFSET stuff inside it ??? :confused: ) , finally compiled after some hacks (still getting a two-column-warning, displayed in every pass again and again), but doesn't link :-(

> LIBS = duser32s.lib

COOL. :crying: OMF version of this got deleted just in HX 2.14 and the one from 2.13 doesn't work :-(

> 1.48: stack size reduced from 1 MB to 4 kB.

WOW !!! Stack is a decaying technology :lol:

Most other things obviously can't compile because of all those uncountable extremely heavy include files, some of them are not available at all ...

---
This is a LOGITECH mouse driver, but some software expect here
the following string:*** This is Copyright 1983 Microsoft ***

Rugxulo(R)

Homepage

Usono,
01.05.2008, 06:00

@ DOS386
 

MOV RIP,POASM

> Tried to compile HIMEMX, but doesn't work, see shot :-( ... hoping for
> later versions

What version did you try? On what OS? (Yeah, probably DOS ...) It seemed to assemble for me just now on XP. And at home on XP in the previous release it also worked. So I dunno why it doesn't work for you. (BTW, new version now shows "time elapsed"). Try again with the 4/28/2008 version or post more info.

DOS386(R)

01.05.2008, 06:02

@ Rugxulo
 

MOV RIP,POASM

> What version did you try?

1.7 :clap:

Again: exact compilation date&time needed :clap:

> On what OS? (Yeah, probably DOS ...)

:clap:

> Try again with the 4/28/2008 version or post more info.

I will :hungry:

---
This is a LOGITECH mouse driver, but some software expect here
the following string:*** This is Copyright 1983 Microsoft ***

Japheth(R)

Homepage

Germany (South),
01.05.2008, 12:14

@ DOS386
 

MOV RIP,POASM

> Since JWASM has made such phenomenal progress in recent 1+1/2 months, the
> famous (but not really working) PO-ASM can now be
> considered as obsolete and dead, right ? :lol:

it still supports COFF, which jwasm doesn't.

> > LIBS = duser32s.lib
>
> COOL. :crying: OMF version of this got deleted just in HX 2.14 and the one
> from 2.13 doesn't work :-(

WLINK can digest both OMF and COFF libs. However, there's a bug in WLINK of OW 1.7. It has been fixed in the meantime, just use the version from the jwasm project page.

(I updated IDECHECK.ZIP, which now uses jwasm+wlink by default.)

> Most other things obviously can't compile because of all those uncountable
> extremely heavy include files, some of them are not available at all ...

What are you talking about?

---
MS-DOS forever!

DOS386(R)

02.05.2008, 21:47

@ Japheth
 

MOV RIP,POASM | JWLINK can mix OMF with COFF ?

> it still supports COFF, which jwasm doesn't.

OK ... it's excellent ... except all those intentional "deliberate differences" making it unusable :-|

> WLINK can digest both OMF and COFF libs.

WOW ! Produce a valid EXE from any mix of COFF and OMF-32 OBJ's and LIB's ?

> I updated IDECHECK.ZIP, which now uses jwasm+wlink by default.

Thanks :-) I'll retest.

---
This is a LOGITECH mouse driver, but some software expect here
the following string:*** This is Copyright 1983 Microsoft ***

DOS386(R)

09.05.2008, 07:50

@ Japheth
 

MOV RIP,POASM | WIN32inc, PESTUB.ASM, MACROS.INC

> > Most other things obviously can't compile because of all those uncountable
> > extremely heavy include files, some of them are not available at all
> What are you talking about?

1. WIN32INC ... 1.2 MiB ZIP, 6.2 MiB extracted, 280 files in 22 DIR's ... it is extremely heavy :-P
2. MACROS.INC - where to get it ?

Update: IDECHECK compiles like a charm now (but to OBJ only, no PE :-( ), and also links, good size, but different content, doesn't work (starts and displays text, but IDE access crashes) ... what is the correct command line to link it ?

---
This is a LOGITECH mouse driver, but some software expect here
the following string:*** This is Copyright 1983 Microsoft ***

Japheth(R)

Homepage

Germany (South),
09.05.2008, 09:39

@ DOS386
 

MOV RIP,POASM | WIN32inc, PESTUB.ASM, MACROS.INC

> > > Most other things obviously can't compile because of all those
> uncountable
> > > extremely heavy include files, some of them are not available at all
> > What are you talking about?
>
> 1. WIN32INC ... 1.2 MiB ZIP, 6.2 MiB extracted, 280 files in 22 DIR's ...
> it is extremely heavy :-P
> 2. MACROS.INC - where to get it ?

Which tool requires MACROS.INC?

> Update: IDECHECK compiles like a charm now (but to OBJ only, no PE :-( ),
> and also links, good size, but different content, doesn't work (starts and
> displays text, but IDE access crashes) ... what is the correct command line
> to link it ?

The command to link IDECHECK can be found in MAKEFILE. It is

-------------------------------------------------------------------
wlink format windows nt runtime console file idecheck.obj op quiet,map, stub=\hx\bin\LOADPEX.BIN, stack=0x1000 LibPath \hx\Lib Library duser32s.lib

patchPE idecheck.exe
-------------------------------------------------------------------

Because it is not quite trivial and also somewhat crucial that the correct link params are used, it is - strongly - recommended to use MAKEFILE to create the binary.

---
MS-DOS forever!

DOS386(R)

11.05.2008, 12:50

@ Japheth
 

MOV RIP,POASM | WIN32inc, PESTUB.ASM, MACROS.INC

> Which tool requires MACROS.INC?

PESTUB (see subj)

> The command to link IDECHECK can be found in MAKEFILE.

I did pick it from there ... but something went wrong nevertheless :-( Retry :hungry:

Is it safe to delete the "LibPath \hx\Lib" if I place the "duser32s.lib" in same dir ?

> Because it is not quite trivial and also somewhat crucial that the correct link params

But JWASM at least needs source filename only, like FASM ?

JWASM IDECHECK.ASM
JWASM PESTUB.ASM

> is - strongly - recommended to use MAKEFILE to create the binary.

Yeah ... but then I need something that eats the MAKEFILE and 1'000'000 things in correct subdirs :-(

Also I'm still getting 1'000'000 errors in Win32Inc when compiling stuff including it :-(

What WLINK to use ? The one from JWASM page or JWASM source package ?

---
This is a LOGITECH mouse driver, but some software expect here
the following string:*** This is Copyright 1983 Microsoft ***

Japheth(R)

Homepage

Germany (South),
11.05.2008, 20:05

@ DOS386
 

some infos

> > Which tool requires MACROS.INC?
>
> PESTUB (see subj)

Ok, but there might be kind of confusion on your side. HX and Win32Inc are not linked. That is, to assemble a HX part (for example PESTUB), you don't need Win32Inc. Furthermore, HXDEV does contain a MACROS.INC file.

> > The command to link IDECHECK can be found in MAKEFILE.
>
> I did pick it from there ... but something went wrong nevertheless :-(
> Retry :hungry:
>
> Is it safe to delete the "LibPath \hx\Lib" if I place the "duser32s.lib"
> in same dir ?

Yes.

> Yeah ... but then I need something that eats the MAKEFILE and 1'000'000
> things in correct subdirs :-(

No. I usually use a NMAKE.EXE, which is just stored in a tools directory and doesn't need anything (besides KERNEL32/DKRNL32). For OW's WMAKE, I'm not sure however.

> Also I'm still getting 1'000'000 errors in Win32Inc when compiling stuff
> including it :-(

Might be a good idea to reveal 1 of the million errors so one can guess at least based on 1 tiny fact. Because, I don't get any errors and I bet there is no magic involved.

> What WLINK to use ? The one from JWASM page or JWASM source package ?

The one from the JWasm page is from the OW snapshot of March. There was a bug fixed concerning COFF libs. The old v1.7 linker won't accept COFF libs created by non-OW tools.

---
MS-DOS forever!

DOS386(R)

31.05.2008, 03:05

@ Japheth
 

INC'ing

> Ok, but there might be kind of confusion on your side.

YES :-(

> HX and Win32Inc are not linked. That is, to assemble a HX part
> (for example PESTUB), you don't need Win32Inc.

GOOD :-)

> Furthermore, HXDEV does contain a MACROS.INC file.

YES. I was searching at wrong place :-(

> I usually use a NMAKE.EXE, which is just stored in a tools directory

Of what ? It isn't in my copy of HXSRC 2.14 :confused:

> Might be a good idea to reveal 1 of the million errors so one can guess

Now using the HXDEV includes ... is better, only cca 100'000 errors in the includes when compiling PESTUB ... "?FLAT" is not (???) defined ?

At least, IDECHECK now compiles and links :-) no idea what stupid bug I had committed previously :-(

---
This is a LOGITECH mouse driver, but some software expect here
the following string:*** This is Copyright 1983 Microsoft ***

Rugxulo(R)

Homepage

Usono,
04.06.2008, 01:53
(edited by Rugxulo, 04.06.2008, 16:07)

@ DOS386
 

INC'ing

> > I usually use a NMAKE.EXE, which is just stored in a tools directory
>
> Of what ? It isn't in my copy of HXSRC 2.14 :confused:

It's probably Microsoft's NMAKE. You might (very doubtful) be able to use wmake /ms instead. (BTW, there are many free make clones: GNU/DJGPP make, DMAKE, Ladsoft's IMAKE, etc.)

rr(R)

Homepage E-mail

Berlin, Germany,
04.06.2008, 09:24

@ Rugxulo
 

INC'ing

> It's probably Microsoft's NMAKE. You might (very doubtful) be able
> to use wmake /ms instead. (BTW, there are many free make clones:
> GNU/DJGPP make, Dmake, etc.)

But most have a different syntax.

Rugxulo(R)

Homepage

Usono,
04.06.2008, 16:06

@ rr
 

INC'ing

> > It's probably Microsoft's NMAKE. You might (very doubtful) be
> able
> > to use wmake /ms instead. (BTW, there are many free make clones:
> > GNU/DJGPP make, Dmake, etc.)
>
> But most have a different syntax.

Yes, but they more or less serve the same purpose. And Japheth is allowed to use whichever one he wants (although I would find it hard to believe GNU make isn't feature-rich enough for him).

---
Know your limits.h

DOS386(R)

11.06.2008, 00:50

@ Rugxulo
 

JMAKE

> It's probably Microsoft's NMAKE.
> might (very doubtful) be able to use wmake /ms
> many free make clones: GNU/DJGPP make, DMAKE, Ladsoft's IMAKE

> But most have a different syntax.

Any is "100% compatible" ?

---
This is a LOGITECH mouse driver, but some software expect here
the following string:*** This is Copyright 1983 Microsoft ***

rr(R)

Homepage E-mail

Berlin, Germany,
11.06.2008, 11:38

@ DOS386
 

JMAKE

> > It's probably Microsoft's NMAKE.
> > might (very doubtful) be able to use wmake /ms
> > many free make clones: GNU/DJGPP make, DMAKE, Ladsoft's IMAKE
>
> > But most have a different syntax.
>
> Any is "100% compatible" ?

Maybe Digital Mars - smake?

Japheth(R)

Homepage

Germany (South),
10.07.2008, 16:43

@ DOS386
 

download source for NMAKE

> > I usually use a NMAKE.EXE, which is just stored in a tools directory
>
> Of what ? It isn't in my copy of HXSRC 2.14 :confused:

Here's one:

http://website.masm32.com/microsft.htm

---
MS-DOS forever!

Rugxulo(R)

Homepage

Usono,
10.07.2008, 22:28

@ Japheth
 

download source for NMAKE

> > > I usually use a NMAKE.EXE, which is just stored in a tools directory
> >
> > Of what ? It isn't in my copy of HXSRC 2.14 :confused:
>
> Here's one:
>

Untested, but maybe it helps. :-)

http://jrfonseca.dyndns.org/projects/gnu-win32/software/msds/nmake2make.sed

Back to index page
Thread view  Board view
15194 Postings in 1365 Threads, 250 registered users, 12 users online (1 registered, 11 guests)
DOS ain't dead | Admin contact
RSS Feed
powered by my little forum