R
RJones
I run a bach file called LINK to link all my *.obj files.
This batch file called LINK works in 98 is as follows:
rl96 & <1%
Now this 1st '&' seems to kick the linker into a mode that
reads from a file, the linker responds with ">>". It is
pobobably necessary, I am not shure. No documentation.
Now J1. is a file which tells the linker what files to
object files to link, what to call the output, ans where
things go im memory. It ia about 900 characters long and
about 12 lines. Somethindg like this:
cstart.obj, reg.obj, hht.obj, ................, j95.obj, &
aaa.obj, ....................................., ddd.obj, &
....
....
............... , &
TO x1. ram(001A-01FF, ................ , &
.................rom(1000- ............................., &
....STACKSIZE(+2)
Running LINK J1 gives response:
"System cannot execuite specified program"
It works just fine in Windows 98
Now it seems like all of this problem has to do with
the "&". It has no meaming in Windows 98. It seemes to
tell the liker that more data is on the next line,
otherwise the linker will think that it is done.
However in a section about what is new for Windows 2000 is
says that the '&' now has a meaning. It means that a new
batch command follows. That is what used to take several
lines to wright now can be done on only one line.
As Olly said, "Anorher fine mess."
Will I ever be able to link under Windows 2000?
PS - I have tried to put all 900 chatacters of this one
command line at the prompt without any "&".
.............................
It comes back again saying:
"Cannot execuite specified program"
However when I got the command line down to less than 128
characters the linker executes just fine, wikh a lot of
expected link errors.
I must have mistakenly interpeted what I read somewhere on
this form, that for Windows 2000 this barrier was
something like 2000 bytes rather than 128 bytes.
Thank you.
R Jones
This batch file called LINK works in 98 is as follows:
rl96 & <1%
Now this 1st '&' seems to kick the linker into a mode that
reads from a file, the linker responds with ">>". It is
pobobably necessary, I am not shure. No documentation.
Now J1. is a file which tells the linker what files to
object files to link, what to call the output, ans where
things go im memory. It ia about 900 characters long and
about 12 lines. Somethindg like this:
cstart.obj, reg.obj, hht.obj, ................, j95.obj, &
aaa.obj, ....................................., ddd.obj, &
....
....
............... , &
TO x1. ram(001A-01FF, ................ , &
.................rom(1000- ............................., &
....STACKSIZE(+2)
Running LINK J1 gives response:
"System cannot execuite specified program"
It works just fine in Windows 98
Now it seems like all of this problem has to do with
the "&". It has no meaming in Windows 98. It seemes to
tell the liker that more data is on the next line,
otherwise the linker will think that it is done.
However in a section about what is new for Windows 2000 is
says that the '&' now has a meaning. It means that a new
batch command follows. That is what used to take several
lines to wright now can be done on only one line.
As Olly said, "Anorher fine mess."
Will I ever be able to link under Windows 2000?
PS - I have tried to put all 900 chatacters of this one
command line at the prompt without any "&".
..................................
.............................
It comes back again saying:
"Cannot execuite specified program"
However when I got the command line down to less than 128
characters the linker executes just fine, wikh a lot of
expected link errors.
I must have mistakenly interpeted what I read somewhere on
this form, that for Windows 2000 this barrier was
something like 2000 bytes rather than 128 bytes.
Thank you.
R Jones