Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.clipper.visual-objects > #2045 > unrolled thread

File() command not working!!! How can this be??

Started bySteveMcNaughton <stevemcnaughton@auditron.com>
First post2011-09-20 09:29 -0700
Last post2011-09-21 09:11 -0700
Articles 14 — 9 participants

Back to article view | Back to comp.lang.clipper.visual-objects


Contents

  File() command not working!!! How can this be?? SteveMcNaughton <stevemcnaughton@auditron.com> - 2011-09-20 09:29 -0700
    Re: File() command not working!!! How can this be?? SteveMcNaughton <stevemcnaughton@auditron.com> - 2011-09-20 12:01 -0700
      Re: File() command not working!!! How can this be?? malcolm gray <malcolm.gray@ntlworld.com> - 2011-09-20 21:25 +0100
        Re: File() command not working!!! How can this be?? SteveMcNaughton <stevemcnaughton@auditron.com> - 2011-09-20 22:46 -0700
          Re: File() command not working!!! How can this be?? "Stephen Quinn" <stevejqNO@bigpondSPAM.net.au> - 2011-09-21 16:08 +1000
          Re: File() command not working!!! How can this be?? KPietsch <KuM.Pietsch@gmx.de> - 2011-09-20 23:16 -0700
            Re: File() command not working!!! How can this be?? Malcolm <malcolm-google@jobstream.com> - 2011-09-21 02:12 -0700
              Re: File() command not working!!! How can this be?? "richard.townsendrose" <richard.townsendrose@gmail.com> - 2011-09-21 02:44 -0700
                Re: File() command not working!!! How can this be?? Mark Ayliffe <mark.ayliffe-news@jobstream.com> - 2011-09-21 11:44 +0100
                Re: File() command not working!!! How can this be?? "Ginny Caughey" <ginny.online@hotmail.com> - 2011-09-21 07:38 -0400
                Re: File() command not working!!! How can this be?? "Willie Moore" <williem@wmconsulting.com> - 2011-09-21 07:21 -0500
                  Re: File() command not working!!! How can this be?? SteveMcNaughton <stevemcnaughton@auditron.com> - 2011-09-21 08:14 -0700
                    Re: File() command not working!!! How can this be?? Mark Ayliffe <mark.ayliffe-news@jobstream.com> - 2011-09-22 12:33 +0100
            Re: File() command not working!!! How can this be?? SteveMcNaughton <stevemcnaughton@auditron.com> - 2011-09-21 09:11 -0700

#2045 — File() command not working!!! How can this be??

FromSteveMcNaughton <stevemcnaughton@auditron.com>
Date2011-09-20 09:29 -0700
SubjectFile() command not working!!! How can this be??
Message-ID<3b5c86c1-d656-4b72-b40c-39d1c0fa58c2@s3g2000vbx.googlegroups.com>
Well, it has to be a library issue or something I'm guessing, but in
my FTP updating program, the FILE() command will not work across
mapped drives.  Works fine on local drives. Our main program has no
issue with it over mapped drives and they both use the same libs!  It
seems to be a windows 64 bit issue at the moment... but we're setting
up an old laptop running 32 bit to verify that.... will update once
that's done.

Anybody stub their toe on this one too??

[toc] | [next] | [standalone]


#2046

FromSteveMcNaughton <stevemcnaughton@auditron.com>
Date2011-09-20 12:01 -0700
Message-ID<6bacfa19-bee7-4b5b-bc2e-5988f70b4c0e@br5g2000vbb.googlegroups.com>
In reply to#2045
update...

this runs FINE on a 32 bit machine mapped to the same drive as the 64
bit machines that fail...!!!

64 bit works fine if not a mapped drive.

This is the code that craps...
	gcNetworkPath		:= GetRegistryString( WR_NetworkPath )  // this works
fine.
......
	IF ! File( gcNetworkPath + "Setup.dbf" )
		InfoMsg( oWin, "Setup Not Found", "Cannot locate the Setup data
file." + crlf;
			+  gcNetworkPath + "Setup.aud" + crlf;
			+ "Please contact Tech Support!" )
		_Quit()
	ENDIF

ALso, I cannot run the DEBUGGER on the 64 bit machines, but it runs
fine on the 32 bit XP machine!!

My libs are identical to the main program in the same order for those
that are needed in the FTP update.  They only lib that's in the FTP
program and not in the main is the INTERNET lib.

I'm going to try to cobble up a small program devoid of any special
libs for a sanity check....

[toc] | [prev] | [next] | [standalone]


#2047

Frommalcolm gray <malcolm.gray@ntlworld.com>
Date2011-09-20 21:25 +0100
Message-ID<tE6eq.434$kj5.380@newsfe25.ams2>
In reply to#2046
On 20/09/2011 20:01, SteveMcNaughton wrote:

> I'm going to try to cobble up a small program devoid of any special
> libs for a sanity check....

I suspect posting that would help other comment.
Also what version of VO? We mainly use 27 and have not noticed a problem 
developing on win7 64bit

On a related point - I assume your problem is file returning false when 
you expect it to return true? (You don't seem to say)

[toc] | [prev] | [next] | [standalone]


#2050

FromSteveMcNaughton <stevemcnaughton@auditron.com>
Date2011-09-20 22:46 -0700
Message-ID<77c4e672-09ec-4b0a-9701-8b3e51f021f8@o15g2000vbe.googlegroups.com>
In reply to#2047
sorry, I'm using 2.8 latest version on Win 7 64 bit.

The File() issue was apparently some sort of corruption somewhere.  I
rebuilt the project using 'test' as the name and copied the
programming from one project to the other at the PRG level and made
some mods while I was at it (of course) and it appears to be working
mow using the mapped drives.  I did it piece by piece expexting
failure at some point, but I ended up entirely rewriting this small
FTP project.  A strange problem indeed.

BUTTTTTT......

I did discover this... when I changed the name back to the original
EXE, all of a sudden, the run button and debugger stop working!!
Changed properties to call it TEST.EXE again, and both buttons work
fine again!!

Someone please tell me why JUST changing the name of the exe
(ZyUpdate.exe) would cause such a problem!  I deleted the VOM and DBG
files to no avail.  It makes the actual EXE with no problem, it just
will not run from the IDE using either the RUN or the DEBUG... I'm
bugged!!! IIS there something hiding somewhere else that's killing me?

The message is "windows call createprocess() failed on starting
(filename)" when using either run or debug buttons...

Change it to anything else, and it's happy!  I really need it to be
ZyUpate.exe to keep things simple and automated on muy end!!  Any
ideas??

[toc] | [prev] | [next] | [standalone]


#2051

From"Stephen Quinn" <stevejqNO@bigpondSPAM.net.au>
Date2011-09-21 16:08 +1000
Message-ID<5afeq.2777$7r4.1918@viwinnwfe02.internal.bigpond.com>
In reply to#2050
Steve

Maybe windows sees  the 'UpDate' part and decides you need different 
permissions to be able to do things.
IIRC something like that happens with programs with 'install' as part of 
their name.

CYA
Steve 

[toc] | [prev] | [next] | [standalone]


#2052

FromKPietsch <KuM.Pietsch@gmx.de>
Date2011-09-20 23:16 -0700
Message-ID<b7f0424c-cc58-4874-b5c7-e1cdeea0d08c@h7g2000yqm.googlegroups.com>
In reply to#2050
On 21 Sep., 07:46, SteveMcNaughton <stevemcnaugh...@auditron.com>
wrote:
> sorry, I'm using 2.8 latest version on Win 7 64 bit.
>
> The File() issue was apparently some sort of corruption somewhere.  I
> rebuilt the project using 'test' as the name and copied the
> programming from one project to the other at the PRG level and made
> some mods while I was at it (of course) and it appears to be working
> mow using the mapped drives.  I did it piece by piece expexting
> failure at some point, but I ended up entirely rewriting this small
> FTP project.  A strange problem indeed.
>
> BUTTTTTT......
>
> I did discover this... when I changed the name back to the original
> EXE, all of a sudden, the run button and debugger stop working!!
> Changed properties to call it TEST.EXE again, and both buttons work
> fine again!!
>
> Someone please tell me why JUST changing the name of the exe
> (ZyUpdate.exe) would cause such a problem!  I deleted the VOM and DBG
> files to no avail.  It makes the actual EXE with no problem, it just
> will not run from the IDE using either the RUN or the DEBUG... I'm
> bugged!!! IIS there something hiding somewhere else that's killing me?
>
> The message is "windows call createprocess() failed on starting
> (filename)" when using either run or debug buttons...
>
> Change it to anything else, and it's happy!  I really need it to be
> ZyUpate.exe to keep things simple and automated on muy end!!  Any
> ideas??

Steve,

as Stephen worte:
This is because of the "Update" part in your filename.
The windows installer detection is the reason for this behaviour.
see http://msdn.microsoft.com/en-us/library/bb756960.aspx

Klaus

[toc] | [prev] | [next] | [standalone]


#2053

FromMalcolm <malcolm-google@jobstream.com>
Date2011-09-21 02:12 -0700
Message-ID<8c97ea8d-21fa-407b-9d19-c356895f0413@1g2000vbu.googlegroups.com>
In reply to#2052
On Sep 21, 7:16 am, KPietsch <KuM.Piet...@gmx.de> wrote:
> On 21 Sep., 07:46, SteveMcNaughton <stevemcnaugh...@auditron.com>
> wrote:
>
>
>
>
>
>
>
>
>
> > sorry, I'm using 2.8 latest version on Win 7 64 bit.
>
> > The File() issue was apparently some sort of corruption somewhere.  I
> > rebuilt the project using 'test' as the name and copied the
> > programming from one project to the other at the PRG level and made
> > some mods while I was at it (of course) and it appears to be working
> > mow using the mapped drives.  I did it piece by piece expexting
> > failure at some point, but I ended up entirely rewriting this small
> > FTP project.  A strange problem indeed.
>
> > BUTTTTTT......
>
> > I did discover this... when I changed the name back to the original
> > EXE, all of a sudden, the run button and debugger stop working!!
> > Changed properties to call it TEST.EXE again, and both buttons work
> > fine again!!
>
> > Someone please tell me why JUST changing the name of the exe
> > (ZyUpdate.exe) would cause such a problem!  I deleted the VOM and DBG
> > files to no avail.  It makes the actual EXE with no problem, it just
> > will not run from the IDE using either the RUN or the DEBUG... I'm
> > bugged!!! IIS there something hiding somewhere else that's killing me?
>
> > The message is "windows call createprocess() failed on starting
> > (filename)" when using either run or debug buttons...
>
> > Change it to anything else, and it's happy!  I really need it to be
> > ZyUpate.exe to keep things simple and automated on muy end!!  Any
> > ideas??
>
> Steve,
>
> as Stephen worte:
> This is because of the "Update" part in your filename.
> The windows installer detection is the reason for this behaviour.
> seehttp://msdn.microsoft.com/en-us/library/bb756960.aspx

Another argument for always giving your exes a manifest (from that
link)
"When the requestedExecutionLevel is present in the embedded
application manifest, it overrides Installer Detection."

[toc] | [prev] | [next] | [standalone]


#2054

From"richard.townsendrose" <richard.townsendrose@gmail.com>
Date2011-09-21 02:44 -0700
Message-ID<03b76f61-bec2-4205-9cc9-a852d7ab45a4@n5g2000yqc.googlegroups.com>
In reply to#2053
Hi all

seems to me that, apart from the currently silent geoff, that many of
us have issues with win7 64 bit.

richard

[toc] | [prev] | [next] | [standalone]


#2056

FromMark Ayliffe <mark.ayliffe-news@jobstream.com>
Date2011-09-21 11:44 +0100
Message-ID<bqrok8-7qj.ln1@news.virginmedia.com>
In reply to#2054
On or about 2011-09-21,
richard.townsendrose <richard.townsendrose@gmail.com> illuminated us with:
> Hi all
>
> seems to me that, apart from the currently silent geoff, that many of
> us have issues with win7 64 bit.

It's been working just fine for us here at Jobstream. We are silent,
but we are several and using VO full-time. 7 programmers all using
Windows 7 64-bit and QA resource using it too.

-- 
Mark Ayliffe MA CEng MBCS, Senior Consultant       Jobstream Group PLC
http://www.jobstream.com                            +44 (0)1223 433900

[toc] | [prev] | [next] | [standalone]


#2059

From"Ginny Caughey" <ginny.online@hotmail.com>
Date2011-09-21 07:38 -0400
Message-ID<4e79cbe7$0$10089$c3e8da3$50776f34@news.astraweb.com>
In reply to#2054
richard,

We are silent because we aren't having problems on Win7-64.

Ginny

"richard.townsendrose"  wrote in message 
news:03b76f61-bec2-4205-9cc9-a852d7ab45a4@n5g2000yqc.googlegroups.com...

Hi all

seems to me that, apart from the currently silent geoff, that many of
us have issues with win7 64 bit.

richard 

[toc] | [prev] | [next] | [standalone]


#2061

From"Willie Moore" <williem@wmconsulting.com>
Date2011-09-21 07:21 -0500
Message-ID<j5ckst$v54$1@speranza.aioe.org>
In reply to#2054
Richard,

I am also using Win 7 64bit with no issues. I have had it on my machines 
ever since it went RTM.

Regards,
Willie

"richard.townsendrose"  wrote in message 
news:03b76f61-bec2-4205-9cc9-a852d7ab45a4@n5g2000yqc.googlegroups.com...

Hi all

seems to me that, apart from the currently silent geoff, that many of
us have issues with win7 64 bit.

richard 

[toc] | [prev] | [next] | [standalone]


#2063

FromSteveMcNaughton <stevemcnaughton@auditron.com>
Date2011-09-21 08:14 -0700
Message-ID<abcd960f-3fc9-4d6b-a9ac-8c4b034d3cde@l4g2000vbz.googlegroups.com>
In reply to#2061
well, I'm standing besides myself at this moment.

At this point, I have to agree with Richard.
There is SOMETHING magical about the naming and Win7/64.

1. If I rename it to ZyUpd.exe in the properties in VO, it works in
all aspects, compile/run exe, run from VO and debug.
2. even when I run the Exe as ZyUpdate.exe, it errors in the program
itself with no real error!
3. If I just change the name of the EXE using Windows explorer from
the same locatoin, it runs fine!!
4. I moved the AEF to my backup platform a 2003 server and compiled
and ran in debug mode there with no problems! So it's not coding, and
seems specific to my machine.
5. I even tried to put the file manually into the MS firewall settings
for advanced permissions after noticing it was missing.  Curiously,
other spelling interations spark the firewall prompting for access
permissions, but not "ZyUpdate". And I see the other spellings listed
automagically in the permitted programs, but not ZyUpdate!

I keep hearing the music of the Outer Limits playing for some
reason.... (Not sure if those of you out of the States will get that
joke...)

Yea, I can change the filename as a workaround, except I have 100's of
terminals out there that expect it to be ZyUpdate.exe and have
shortcuts and there start/program list is looking for that name too.
What a mess that would be.

Could one of you with win7/64 bit just try changing the name of one of
your programs to ZyUpdate.exe?  Preferrable one with FTP access, if
you have one. Or perhaps someone that might know the corners of the OS
better than I give me a clue of what else I could wiggle or check?

Thanks greatly.

[toc] | [prev] | [next] | [standalone]


#2067

FromMark Ayliffe <mark.ayliffe-news@jobstream.com>
Date2011-09-22 12:33 +0100
Message-ID<e1jrk8-odm.ln1@news.virginmedia.com>
In reply to#2063
On or about 2011-09-21,
SteveMcNaughton <stevemcnaughton@auditron.com> illuminated us with:
> well, I'm standing besides myself at this moment.
>
> At this point, I have to agree with Richard.
> There is SOMETHING magical about the naming and Win7/64.
>
> 1. If I rename it to ZyUpd.exe in the properties in VO, it works in
> all aspects, compile/run exe, run from VO and debug.
> 2. even when I run the Exe as ZyUpdate.exe, it errors in the program
> itself with no real error!

This started with Vista:
http://msdn.microsoft.com/en-us/library/bb756960.aspx Best advice is
to work out how to use manifest files and better still to embed them
in your app: http://msdn.microsoft.com/en-us/library/bb756929.aspx

> Yea, I can change the filename as a workaround, except I have 100's of
> terminals out there that expect it to be ZyUpdate.exe and have
> shortcuts and there start/program list is looking for that name too.
> What a mess that would be.
>
> Could one of you with win7/64 bit just try changing the name of one of
> your programs to ZyUpdate.exe?  Preferrable one with FTP access, if
> you have one. Or perhaps someone that might know the corners of the OS
> better than I give me a clue of what else I could wiggle or check?

Our executable files will work fine because the have embedded manifests.

-- 
Mark Ayliffe MA CEng MBCS, Senior Consultant       Jobstream Group PLC
http://www.jobstream.com                            +44 (0)1223 433900

[toc] | [prev] | [next] | [standalone]


#2064

FromSteveMcNaughton <stevemcnaughton@auditron.com>
Date2011-09-21 09:11 -0700
Message-ID<481f0fc6-0155-4f69-a7fb-ac2594834e7a@k29g2000yqf.googlegroups.com>
In reply to#2052
Klause,

I somehow missed your post the first time through...Saw Stephen's but
skipped over yours!

and it appears you may be right!

from the pointer you gave....

"Before a 32 bit process is created, the following attributes are
checked to determine whether it is an installer:
Filename includes keywords like "install," "setup," "update," etc."

Apparently, something changed where it looks for these words as
substrings of those filenames now, not as whole names.  We've used
this filename since about 1986 (from the good old Clipper days!)
without a problem until now. (that's 25 stinking years!!)

I have verified that what previously worked for SEVERAL MONTHS on win7
64 bit systems has stopped working in the last month.  I've just put
the EXE on my wife's laptop and a client's system.  The program works
fine if it does not contain the word "update" as part of the filename.
It does not start the installer, it just crashes ugly when you go past
the first prompt. My only conclusion has to be that Micro$oft changed
something in one of their recent updates as nothing has changed in the
field for our software. And nothing has changed programitcally, until
now, in over a year in the actual program, which, as I said, WAS
working fine.


> as Stephen worte:
> This is because of the "Update" part in your filename.
> The windows installer detection is the reason for this behaviour.
> seehttp://msdn.microsoft.com/en-us/library/bb756960.aspx
>
> Klaus- Hide quoted text -
>
> - Show quoted text -

[toc] | [prev] | [standalone]


Back to top | Article view | comp.lang.clipper.visual-objects


csiph-web