 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
| HomeDiscussion Groups Database Servers DB2InformixIngresMS SQLOraclePervasive.SQLPostgreSQLProgressSybaseDesktop Databases FileMakerFoxProMS AccessParadoxGeneral General DB TopicsDatabase TheoryRelated Topics Java Development.NET DevelopmentVB DevelopmentMore Topics ... |
Database Forum / FoxPro / Setup / February 2004Vfp8 SP1 Probs. with Profile
Hi All First im saying my englisch is bad ;-) Lee Mitchell says : > 2. Run this code somehow to change it. You could create a startup script > for him to run his app: > ntemp=0 > SystemParametersInfo(0x103F,0,ntemp,2) What does the 0x103F flag, which combination of flags is it ? SPI_?? | SPI_?? My problem is, that on one of four machines the vfp8 SP1 does not start, it gives me an GPF Cx00000005. And i know that is something with the Profile of this user. With another profile on the same machine the vfp works. And with this profile on another machine its not work. My Programms and Vfp-Dll's (vfp*, gdi*, msvc*) are in one Directory, which is on the Server. The Client has local no Vfp-Files ! Its an W2K-machine. Thx 4 Help Daniel Hello, Daniel! I'd first try to fix this by removing the user's resource file (usually foxuser.dbf/fpt). Let us know if that doesn't help.  SignatureEric den Doop www.foxite.com - The Home Of The Visual FoxPro Experts - Powered By VFP8 Hi Eric We dont us foxuser.dbf -> set reso off I have searched on the local Drive, and on our Application-Directory ( Drive on Server). The files foxuser.* does not exist ! When i start my Application, before i see the screen(application) it coms the error cx0000..5 I have also try to install and register the vfp-files localy, but with the same result. With the User "Administartor" its works, and also with another user on the same machine. Daniel File-Protocoll log : many things.. .... 2092 16:24:41 TAGLZ.EXE:492 OPEN Z:\TimeAs\VFP8R.DLL SUCCESS Options: Open Access: All 2093 16:24:41 TAGLZ.EXE:492 QUERY INFORMATION Z:\TimeAs\VFP8R.DLL SUCCESS FileBasicInformation 2094 16:24:41 TAGLZ.EXE:492 CLOSE Z:\TimeAs\VFP8R.DLL SUCCESS 2095 16:24:41 TAGLZ.EXE:492 OPEN C:\WINNT\win.ini SUCCESS Options: Open Access: All 2096 16:24:41 TAGLZ.EXE:492 OPEN C:\WINNT\win.ini SUCCESS Options: Open Access: All 2097 16:24:41 TAGLZ.EXE:492 QUERY INFORMATION C:\WINNT\win.ini SUCCESS Attributes: A 2098 16:24:41 TAGLZ.EXE:492 SET INFORMATION C:\WINNT\win.ini SUCCESS FileBasicInformation 2099 16:24:41 TAGLZ.EXE:492 QUERY INFORMATION C:\WINNT\win.ini SUCCESS Length: 1554 2100 16:24:41 TAGLZ.EXE:492 CLOSE C:\WINNT\win.ini SUCCESS 2101 16:24:41 TAGLZ.EXE:492 OPEN C:\WINNT\win.ini SUCCESS Options: Open Access: All 2102 16:24:41 TAGLZ.EXE:492 CLOSE C:\WINNT\win.ini SUCCESS 2103 16:24:41 TAGLZ.EXE:492 LOCK C:\WINNT\win.ini SUCCESS Excl: No Offset: 0 Length: -1 2104 16:24:41 TAGLZ.EXE:492 QUERY INFORMATION C:\WINNT\win.ini SUCCESS Length: 1554 2105 16:24:41 TAGLZ.EXE:492 READ C:\WINNT\win.ini SUCCESS Offset: 0 Length: 1554 2106 16:24:41 TAGLZ.EXE:492 UNLOCK C:\WINNT\win.ini RANGE NOT LOCKED Offset: 0 Length: -1 2107 16:24:41 TAGLZ.EXE:492 CLOSE C:\WINNT\win.ini SUCCESS 2108 16:24:41 TAGLZ.EXE:492 OPEN C:\WINNT\win.ini SUCCESS Options: Open Access: All 2109 16:24:41 TAGLZ.EXE:492 OPEN C:\WINNT\win.ini SUCCESS Options: Open Access: All 2110 16:24:41 TAGLZ.EXE:492 QUERY INFORMATION C:\WINNT\win.ini SUCCESS Attributes: A 2111 16:24:41 TAGLZ.EXE:492 SET INFORMATION C:\WINNT\win.ini SUCCESS FileBasicInformation 2112 16:24:41 TAGLZ.EXE:492 QUERY INFORMATION C:\WINNT\win.ini SUCCESS Length: 1554 2113 16:24:41 TAGLZ.EXE:492 CLOSE C:\WINNT\win.ini SUCCESS 2114 16:24:41 TAGLZ.EXE:492 OPEN C:\WINNT\win.ini SUCCESS Options: Open Access: All 2115 16:24:41 TAGLZ.EXE:492 CLOSE C:\WINNT\win.ini SUCCESS 2116 16:24:41 TAGLZ.EXE:492 LOCK C:\WINNT\win.ini SUCCESS Excl: No Offset: 0 Length: -1 2117 16:24:41 TAGLZ.EXE:492 QUERY INFORMATION C:\WINNT\win.ini SUCCESS Length: 1554 2118 16:24:41 TAGLZ.EXE:492 READ C:\WINNT\win.ini SUCCESS Offset: 0 Length: 1554 2119 16:24:41 TAGLZ.EXE:492 UNLOCK C:\WINNT\win.ini RANGE NOT LOCKED Offset: 0 Length: -1 2120 16:24:41 TAGLZ.EXE:492 CLOSE C:\WINNT\win.ini SUCCESS if its work, on this place, the vfp8r.dll will be opened again... else following this... 2121 16:24:41 TAGLZ.EXE:492 OPEN Z:\TimeAs\VFP8Rerr.log SUCCESS Options: OpenIf Access: All 2122 16:24:41 TAGLZ.EXE:492 OPEN Z:\TimeAs\VFP8Rerr.log SUCCESS Options: Open Access: All 2123 16:24:41 TAGLZ.EXE:492 READ C:\WINNT\CSC\00000001 SUCCESS Offset: 0 Length: 4096 2124 16:24:41 TAGLZ.EXE:492 SET INFORMATION Z:\TimeAs\VFP8Rerr.log SUCCESS FileBasicInformation 2125 16:24:41 TAGLZ.EXE:492 READ Z:\TimeAs\VFP8Rerr.log SUCCESS Offset: 0 Length: 256 2126 16:24:41 TAGLZ.EXE:492 READ Z:\TimeAs\VFP8Rerr.log SUCCESS Offset: 5079 Length: 512 2127 16:24:41 TAGLZ.EXE:492 READ Z:\TimeAs\VFP8Rerr.log SUCCESS Offset: 4617 Length: 256 2128 16:24:41 TAGLZ.EXE:492 READ Z:\TimeAs\VFP8Rerr.log SUCCESS Offset: 1099 Length: 256 2129 16:24:41 TAGLZ.EXE:492 READ Z:\TimeAs\VFP8Rerr.log SUCCESS Offset: 4780 Length: 256 2130 16:24:41 TAGLZ.EXE:492 READ Z:\TimeAs\VFP8Rerr.log SUCCESS Offset: 4761 Length: 256 2131 16:24:41 TAGLZ.EXE:492 READ Z:\TimeAs\VFP8Rerr.log SUCCESS Offset: 0 Length: 512 2132 16:24:41 TAGLZ.EXE:492 READ Z:\TimeAs\VFP8Rerr.log SUCCESS Offset: 2048 Length: 512 2133 16:24:41 TAGLZ.EXE:492 READ Z:\TimeAs\VFP8Rerr.log SUCCESS Offset: 512 Length: 512 2134 16:24:41 TAGLZ.EXE:492 READ Z:\TimeAs\VFP8Rerr.log SUCCESS Offset: 0 Length: 2 2135 16:24:41 TAGLZ.EXE:492 READ Z:\TimeAs\VFP8Rerr.log SUCCESS Offset: 0 Length: 4096 2136 16:24:41 TAGLZ.EXE:492 READ Z:\TimeAs\VFP8Rerr.log SUCCESS Offset: 1495 Length: 4096 2137 16:24:41 TAGLZ.EXE:492 READ Z:\TimeAs\VFP8Rerr.log SUCCESS Offset: 0 Length: 4096 2138 16:24:41 TAGLZ.EXE:492 READ Z:\TimeAs\VFP8Rerr.log SUCCESS Offset: 0 Length: 512 2139 16:24:41 TAGLZ.EXE:492 READ Z:\TimeAs\VFP8Rerr.log SUCCESS Offset: 0 Length: 64 2140 16:24:41 TAGLZ.EXE:492 READ Z:\TimeAs\VFP8Rerr.log SUCCESS Offset: 0 Length: 512 2141 16:24:41 TAGLZ.EXE:492 CLOSE Z:\TimeAs\VFP8Rerr.log SUCCESS Hello, Daniel! You wrote on Tue, 27 Jan 2004 08:49:58 +0100: DB> With the User "Administartor" its works, and also with another user on DB> the same machine. Hmmm this sounds like a security setting. Does the user have sufficient access (read/write) in the temp folders? Just a thought. SignatureEric den Doop www.foxite.com - The Home Of The Visual FoxPro Experts - Powered By VFP8 Hi Eric Its not an security problem ! We have another client with this problem (cx00..5), and on that machine an "normal-user" works fine, but the administrator does not work. i has called the client, and we have checked the user-temp-folder and checked the system-temp-folder, and on both folder the user has all access. Info : the profile wich is not working with vfp, is an server-side profile. Vfp 7.0 has worked perfekt! Same code (+ / -) compiled with vfp8.0 SP1 crashs ! ON THE SAME USER.. on other machines it works... Im very confused about this bug... Daniel Thank u for help me ! Hi Eric i have something testet / configurated on my W2k, and i can make that the error coms like by the clients. 1. create an serverside-profil from an WIN 2000 operating-system. 2. login with this profile on an WinXP machine. and logout 3. login wit this profil on the "old" Win2K, start your Vfp-Application and it will be crashed ! i got both profiles from my W2K, the old 1 which is ok, and the new which is corrupted. i will now try to find the difference... Daniel Did you ever figure this one out? I have the same types of problems with VFP 8 at my client sites as well, some machines work fine while others are unusable with C5 errors all through out the application. Hi Jerry I have writen an Patch-Exe for me, on my case its works after starting my patch ! I write an C-Program witch is calling just one thing : void* ntemp = NULL; SystemParametersInfo(0x103F,0,ntemp,SPIF_SENDWININICHANGE); What this Parameter "0x103F" does, i don't know, but its works. No one from this "MS Foxpro Gurus" has explained to mee. I found any changes in the ntuser.dat (User-profile), but its too much changes for mee to finding the exactly error-bloc. Cu Daniel |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.