>I thought this was standard now on Win10. Not that I think it is >relevant with my problem.
It is. There is a syscall compiled version in System32 (64-bit) and a 32-bit version in SysWOW64. named winsqlite3.dll The App Store and the (modern app) Installer processes use sqlite3 databases to track dependencies, installations and so forth. It is actually kina nice because when Windows gets itself in a tizzy you can open the databases with the command-line tool and "fix" (that is, remove) the broken entries, clean up the filesystem, and everything (modern app wise) will work again. Especially helpful since the regular windows upgrade/install and the roll-back to previous version does not know how to "fix" updated versions of modern apps properly and if you can end up with a completely borked phone susbsystem on the computer which cannot even run the settings applet crap properly until you fix the database and let it re-install the apps. Much better than the proprietary undocumented "no user serviceable parts inside" so typical of Microsoft. Of course, the actual Store and the couple of services that use the database were written by a moron and excess data is cached that ought not be, so you have to cycle a bunch of services (or reboot) before it "notices" that the database was changed. >On Thu, Sep 7, 2017 at 9:58 AM, Chris Locke ><[email protected]> >wrote: > >> I'd suggest running the Microsoft Process Monitor >> https://docs.microsoft.com/en-us/sysinternals/downloads/procmon >> >> When your application crashes, this will show the files it tried to >access >> before the crash. It might point to a dependancy missing. >> Have you 'installed' SQLite on your Win 10 machines? I use >> system.data.sqlite.dll in my applications, and that requires >msvcr120.dll. >> Without that, I get a weird 'SQLite.Interop.dll module could not be >found' >> error ... which makes sense, but its not strictly accurate ... its >there, >> it just can't be loaded. SQLite requires a couple of extra files >to run >> properly. They may not be installed on the Win 10 box. >> >> Ideally, you need a proper stack trace and error log from your >application. >> >> > In Windows you get a frowny face "modern icon" >> >> Thats for a full-on Windows 'blue screen', not an application >crash. I >> assume this isn't causing a blue-screen, but is just failing. >> >> > Could the problem be that SQLite is installed by MS already on >those >> machines? >> >> SQLite is a third party product, and would not be pre-installed by >> Microsoft. >> >> >> Thanks, >> Chris >> >> >> On Thu, Sep 7, 2017 at 8:45 AM, Bart Smissaert ><[email protected]> >> wrote: >> >> > Yes, not very helpful. The message is from my VB6 wrapper as is >like >> this: >> > >> > Method ProcedureX of object _ClassX failed >> > >> > ClassX is the class in the wrapper ActiveX dll that also has the >> procedure >> > that makes the call to SQLite that causes the problem, in this >> > case sqlite3_initialize. >> > ProcedureX is another procedure in that same class, but that >procedure >> has >> > nil to do with the problem. >> > I can take that ProcedureX out and that I will get another >procedure >> > mentioned in the error message that is again completely unrelated >to the >> > problem. >> > >> > So the whole thing is just completely puzzling and I am seriously >stuck >> > with this. >> > >> > >> > RBS >> > >> > >> > >> > On Thu, Sep 7, 2017 at 2:44 AM, Keith Medcalf ><[email protected]> >> wrote: >> > >> > > >> > > In Windows you get a frowny face "modern icon" (about 5 inches >square) >> > and >> > > "something went wrong, sorry about your luck". >> > > >> > > >> > > --- >> > > The fact that there's a Highway to Hell but only a Stairway to >Heaven >> > says >> > > a lot about anticipated traffic volume. >> > > >> > > >> > > >-----Original Message----- >> > > >From: sqlite-users [mailto:sqlite-users- >> > > >[email protected]] On Behalf Of Simon Slavin >> > > >Sent: Wednesday, 6 September, 2017 15:06 >> > > >To: SQLite mailing list >> > > >Subject: Re: [sqlite] Fwd: Problem on Windows 10 machines >> > > > >> > > > >> > > > >> > > >On 6 Sep 2017, at 10:03pm, Bart Smissaert ><[email protected]> >> > > >wrote: >> > > > >> > > >> When my wrapper makes the call to the Sqlite dll my app >crashes >> > > > >> > > >With what error ? Segmentation fault ? Privilege violation ? >I >> > > >don’t think I’ve seen any crash which doesn’t produce an error >report >> > > >of some kind, even if we know that there’s no reason for that >error >> > > >at that point. >> > > > >> > > >Simon. >> > > >_______________________________________________ >> > > >sqlite-users mailing list >> > > >[email protected] >> > > >http://mailinglists.sqlite.org/cgi- >bin/mailman/listinfo/sqlite-users >> > > >> > > >> > > >> > > _______________________________________________ >> > > sqlite-users mailing list >> > > [email protected] >> > > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite- >users >> > > >> > _______________________________________________ >> > sqlite-users mailing list >> > [email protected] >> > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite- >users >> > >> _______________________________________________ >> sqlite-users mailing list >> [email protected] >> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite- >users >> >_______________________________________________ >sqlite-users mailing list >[email protected] >http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
