Hi all

I have a code in file new.txt: 

>>
..model tiny
..code
..386
org 100h

Start:

end Start
>>

When I try to link it, an error occurs:
Fatal: 16 bit segments not supported in module new.txt

What does it mean? What should I do?

I am newbie ;--)

-- 
pozdr.  Dygi [GG 1027078]
dygimail(at)poczta(dot)fm

"Mr Dygi" <dygimailNo@SPAMpoczta.fm> wrote in message
news:Xns94749A720AB6Fdygimailpocztafm@127.0.0.1...
> Hi all
>
> I have a code in file new.txt:
>
> >>
> .model tiny
> .code
> .386
> org 100h
>
> Start:
>
> end Start
> >>
>
> When I try to link it, an error occurs:
> Fatal: 16 bit segments not supported in module new.txt
>
> What does it mean? What should I do?
>
> I am newbie ;--)
>
> -- 
> pozdr.  Dygi [GG 1027078]
> dygimail(at)poczta(dot)fm
>

let's see your command lines for assembly and linking...

"Mr Dygi" <dygimailNo@SPAMpoczta.fm> wrote in message
news:Xns94749A720AB6Fdygimailpocztafm@127.0.0.1...
> Hi all
>
> I have a code in file new.txt:
>
> >>
> .model tiny
> .code
> .386
> org 100h
>
> Start:
>
> end Start
> >>
>
> When I try to link it, an error occurs:
> Fatal: 16 bit segments not supported in module new.txt
>
> What does it mean? What should I do?
>
> I am newbie ;--)

You're not trying to use masm32 are you? Usually you get errors like then
when writing 16-bit code for a 32-bit program. Linux and Windows are both
32-bit. DOS is 16-bit for the most part. (DOS has 32-bit extensions, but I
highly doubt you're using them.)

-Matt

"Bx. C" <null@the.void> wrote in 
news:CHAOb.5333$D%.1298@bignews1.bellsouth.net:

> let's see your command lines for assembly and linking...

tasm32 /t new.txt
tlink32 new.obj

Is this what you are asking for?

-- 
pozdr.  Dygi [GG 1027078]
dygimail(at)poczta(dot)fm

"Matt Taylor" <para@tampabay.rr.com> wrote in
news:MFCOb.24652$Bj.22349@twister.tampabay.rr.com: 

> You're not trying to use masm32 are you? Usually you get errors like
> then when writing 16-bit code for a 32-bit program. Linux and Windows
> are both 32-bit. DOS is 16-bit for the most part. (DOS has 32-bit
> extensions, but I highly doubt you're using them.)

True. I thought I can use 32-bit linker for 16-bit code. But there is 
another problem now. When I try to use 16-bit tasm compiler and linker, 
these errors occur:

+ tasm /t new.txt =>

bad command or filename
bad command or filename
bad command or filename

[result: file new.obj created]

+ tlink new.obj =>

Error: Invalid entry point offset
Warning: No stack

+ type new.map [DOS shell] =>

 Start  Stop   Length Name               Class

 00000H 000FFH 00100H _TEXT              CODE
 00100H 00100H 00000H _DATA              DATA

Error: Invalid entry point offset
Program entry point at 0000:0000
Warning: No stack

-- 
pozdr.  Dygi [GG 1027078]
dygimail(at)poczta(dot)fm

Hi Mr Dygi

You say "I have a code in file new.txt:"

But I can't see your code, I mean there's
no code in your program ???
Or have I missed something here....?


"Mr Dygi" <dygimailNo@SPAMpoczta.fm> wrote in message
news:Xns947550D8C41ADdygimailpocztafm@127.0.0.1...
> "Matt Taylor" <para@tampabay.rr.com> wrote in
> news:MFCOb.24652$Bj.22349@twister.tampabay.rr.com:
>
> > You're not trying to use masm32 are you? Usually you get errors like
> > then when writing 16-bit code for a 32-bit program. Linux and Windows
> > are both 32-bit. DOS is 16-bit for the most part. (DOS has 32-bit
> > extensions, but I highly doubt you're using them.)
>
> True. I thought I can use 32-bit linker for 16-bit code. But there is
> another problem now. When I try to use 16-bit tasm compiler and linker,
> these errors occur:
>
> + tasm /t new.txt =>
>
> bad command or filename
> bad command or filename
> bad command or filename
>
> [result: file new.obj created]
>
> + tlink new.obj =>
>
> Error: Invalid entry point offset
> Warning: No stack
>
> + type new.map [DOS shell] =>
>
>  Start  Stop   Length Name               Class
>
>  00000H 000FFH 00100H _TEXT              CODE
>  00100H 00100H 00000H _DATA              DATA
>
> Error: Invalid entry point offset
> Program entry point at 0000:0000
> Warning: No stack
>
> -- 
> pozdr.  Dygi [GG 1027078]
> dygimail(at)poczta(dot)fm
>

"SharK" <the_shark_356@hotmail.com> wrote in 
news:400ed62f$0$204$edfadb0f@dread12.news.tele.dk:

> You say "I have a code in file new.txt:"
> 
> But I can't see your code, I mean there's
> no code in your program ???
> Or have I missed something here....?

Yes. That was a problem. I thought there were no problem to compile and 
link source with only main directives, and without main code. In fact 
addition main code did nothing. A problem is still but now it's another 
error.

Before i tried to use 32 bit tasm to compile 16 bit code. Now i try to 
compile using 16 bit tasm, and i have these problems:

dir c:\tasm =>

    	TASM.EXE
    	TLINK.EXE
    	DPMIMEM.DLL

tasm new.asm => ok
tlink /t new.obj => an error occur

    	Failed to locate protected mode loader <DPMILOAD.EXE>

I've found this file in c:\tasm32 (where I have unpacked tasm32) and I've 
copied it to c:\tasm (where I have unpacked tasm16). Sometimes there is no 
problem but sometimes is. But unfortunately I forgot what was the problem 
and I am waiting when it'll occur again.

ps Why there is a problem with DPMILOAD.EXE file? Some of you don't have 
this file and it's all ok. I am using asm in WinXP.

-- 
pozdr.  Dygi [GG 1027078]
dygimail(at)poczta(dot)fm