Back to home page

DOS ain't dead

Forum index page

Log in | Register

Back to the forum
Board view  Mix view

OMF records (Developers)

posted by Japheth Homepage, Germany (South), 17.02.2012, 08:08

> I played with it a bit more, but I'm really unfamiliar with WLINK syntax. I
> ended up doing something like "format dos name blah file
> abc,xyz,out,term,sys", which would give a few warnings, create an .EXE, but
> that wouldn't run, wrongly claimed xyz module is older than whatever. (That
> error detection part is apparently embedded in SYS.OBJ, whose source is not
> included. I don't think you really need it, but I don't know why it's
> confused here.) Anyways, for comparison, this does not happen with TLINK or
> MS LINK or VALX. I'm not sure why, there's too many oddball things going on

This is not really a high-quality error report. You should post the exact warning and error messages and also post the exact command line you used for both MS link and WLINK. I'm familiar with both linkers. Additionally, you should make the linkers create MAP files - by comparing the two resulting map files it will most likely become obvious what's wrong with wlink.

For wlink, to create a map file enter:

"format dos name blah file abc,xyz,out,term,sys op map"

---
MS-DOS forever!

 

Complete thread:

Back to the forum
Board view  Mix view
22761 Postings in 2121 Threads, 402 registered users (3 online)
DOS ain't dead | Admin contact
RSS Feed
powered by my little forum