Re: LNK1106: Invalid file or disk full: cannot seek to 0x68e2.

From: GeorgeMar (GeorgeMar_at_discussions.microsoft.com)
Date: 08/26/04 

Date: Thu, 26 Aug 2004 16:49:03 -0700

Thank you again Bjorn.

One more question if I may.

I am compiling on my computer and taking the EXE to the client. The reason
I tried to compile at the client's site was to get the error message because
my EXE was being stopped by my own On Error.

Since I am compiling locally and it was running well before, I am trying to
work out how the linker is getting involved? I would assume that the linker
is not called when an EXE is run. Am I correct? That would point to something
else.

regards
george

"Björn Holmgren" wrote:

> "GeorgeMar" <GeorgeMar@discussions.microsoft.com> skrev i meddelandet
> news:A3B6E441-F729-49EF-8658-9BFF5770591B@microsoft.com...
> > Thank you again Bjorn
> >
> > You will pardon my ignorance but I need to clarify somethings with you.
> >
> > The situation that I have at the moment is that the VB EXE resides on the
> > server and the users run the EXE from a shorcut on their desktop. Thus
> they
> > are all running the same EXE. The EXE does three things: Verify the
> version
> > of an MDE on the local drive against that on the server, Verify the
> user's
> > name and password and then fire up the MDE application on the local drive
> and
> > closes the EXE.
> >
> > Since the EXE is supplied by me, that is, it has been compiled on my PC
> and
> > works fine, how does one compile/link on their local drive as you suggest?
> > They do not have the source code.
> >
>
> No, I didn't mean on -their- local drive(s), but on -a- local drive.
> The error you're getting - if it's network related - occurs when you save
> the
> exe - while compiling - to a location on the network, because the linker
> uses
> something called memory-mapped files, which can cause problems on some
> networks. The workaround is to first "make" the exe on your local drive, and
> then
> copy it to the network location.
>
> In your original post you stated that you were trying to "compile at the
> client's
> site", which lead me to believe that maybe you were making the exe
> directly on a network location at the client's site.
>
> If that's not the case and you're already compiling locally, then it's not
> network related,
> and you'll probably have to look for physical errors on your local disk.
>
> >
> > Should the EXE be run locally? If so, that creates a problem for me as to
> > how to find where on the server the necessary files for the EXE to work
> are?
> > Currently, the shortcut directs the EXE to start from a path to the
> server.
> >
>
> Having the exe on the server seems like a good idea to me.
> But if I understand correctly, you're getting the LNK1106 error while compil
> ing,
> not when running the exe, right? So then there should be no problem running
> the exe from the server, just compiling directly to the network location,
> and then
> it's all just a matter of compiling/making/saving the exe on you'r local
> disk and
> then copy it to the server.
>
> >
> > Hope all that makes sense. It is driving me crazy, not knowing the proper
> > answer.
> >
>
> Well, sort of. But I'm still not absolutely sure what you're doing when you
> receive the error. Compiling or running? Compiling where? etc... ;-)
>
>
> --
> Björn Holmgren
> Guide Konsult AB
>
>
>

Relevant Pages

  • Re: Printing variables to screen, when in debug
    ... >>> evaluation tool (CosmoScope). ... >>Are you aware of the immediate window, and the Debug object? ... > But do remove before compiling as they slow your program down. ... For example, Debug.Print statements, while ignored in the run-time .exe, are ...
    (microsoft.public.vb.general.discussion)
  • Re: Source of EXE Size OT
    ... Aside from any resources you may have added, the EXE will ... After compiling to native code for many years, ... >> default compiler options. ...
    (microsoft.public.vb.general.discussion)
  • Re: Update #1 - Initialization Failure on Running Apps...
    ... I have exactly the same problem after actually compiling the application. ... so when using the "old" exe and debug info things are ... then repair again and I'm hoping that it'll download a fresh update. ...
    (borland.public.delphi.non-technical)
  • Re: LNK1106: Invalid file or disk full: cannot seek to 0x68e2.
    ... > server and the users run the EXE from a shorcut on their desktop. ... The error you're getting - if it's network related - occurs when you save ... If that's not the case and you're already compiling locally, ...
    (microsoft.public.vb.general.discussion)
  • Re: Source of EXE Size OT
    ... > There is a phenomena in VB6 when compiling to native code the exe will grow ... Can't say I ever noticed it (I don't look at .exe size too often--it's ... generating p-code or native and whether he has changed any of the ... default compiler options (empahsize speed over size comes to mind). ...
    (microsoft.public.vb.general.discussion)