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

From: Björn Holmgren (bjohol_at_hotmail.com)
Date: 08/26/04 

Date: Thu, 26 Aug 2004 07:22:51 +0200

"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: Who is using the EXE
    ... Running applications across a network is a bad idea for several reasons, ... The normal solution is to write a small launcher program which is installed ... if it finds a newer one on the server it copies it over the local ... I developed an application using VB6, placed the exe in a shared ...
    (microsoft.public.vb.general.discussion)
  • Re: XP x 3+clipper=SLOW
    ... maybe a little when loading exe. ... I had the problem on "server" when i used mapped drive, ... it sounds like there is something wrong with how the network is ... Clipper applications and similar file sharing apps are run. ...
    (comp.lang.clipper)
  • Connection to SQL Server 7 using MDAC 2.6
    ... Whilst running the exe from a share in a small network with the SQL server ... on another server on a routed network, the connection times out first time ...
    (microsoft.public.sqlserver.connect)
  • Re: Application caching
    ... Microsoft MVP - Terminal Services ... We have set up Server 2008 with Terminal Server for about 10 users. ... All those users use the same application (a single exe from a network ...
    (microsoft.public.windows.terminal_services)
  • Re: vista pia
    ... You could have the small exe in program ... How do you install that new app? ... In our case, the app lives on a network drive, but the approach could work ... Running from the file server might be another solution too then, ...
    (microsoft.public.fox.programmer.exchange)