Re: Re: Visual Studio 2008

It could be one of approximately a billion things.. :(
Anyway, I'll keep it in mind.

Thanks
Dimitris



On Sat, Sep 29, 2012 at 12:05 PM, chris.kevany <[email protected]>wrote:

> **
>
>
> Hi Dimitris,
>
> Probably a bit confusing but a meant a service pack for
> Visual Studio 2008 itself;
>
> http://www.microsoft.com/en-us/download/details.aspx?id=10986
>
> About the problems...
>
> I basically develop still on XP but mirror my develop environment
> on Win7 so I can easily see the difference.
>
> My application is complex, uses large buffers (32K), calls functions
> in ddl's hundreds of times, loads/decrypt/runs many encrypted gc
> utilities and does this without any issues on XP (unless I introduce
> errors myself of course).
>
> On win7 the same sources work very unpredictable, hangs without any
> notification (Gui4Cli error message) at arbitrary places.
> And the most weird thing is that this depends on the size of the
> scripts and the file path from where it runs.
>
> E.g. When I have this problem on path x and not on path y, then
> when I simply add a comment to the script (changing the file size),
> it happens that it runs on path x but hangs at another arbitrary
> place at path y. I test it at seven different install paths and
> with a lot of patience I occasionally can "trim" the whole stuff
> so it runs on all paths without noticeable issues.
>
> I started testing on win7 about 6 months ago and tried almost
> everything to find out what's wrong, like changing the order and
> things in the the scripts of which I thought they could be critical.
>
> For XP it all doesn't matter, it always act the same.
>
> I still have the impression there's an issue on win7 with loading
> the scripts into memory and perhaps with the stack?
>
> I remember I had highly comparable behaviour on XP a few years ago
> but that was because I used "Include" to include a part of the script
> from within a self-contained executable. The part to incuded was
> also a resource in the executabe. After I added the part to the
> main script, the problem was solved.
>
> Chris
>
>
> --- In [email protected], Dimitris Keletsekis <gui4cli@...> wrote:
> >
> > Hi Chris,
> >
> > I had a look at my control panel -> system, and it says Windows 7 -
> service
> > pack 1.
> >
> > It is updated automatically so if you're connected to the internet, you
> > have it. Version 19.38 was compiled under this, although it shouldn't
> make
> > any differences.
> >
> > Remind me again what problems you're having?
> >
> > Dimitris
> >
> >
> >
> > On Fri, Sep 28, 2012 at 11:02 PM, chris.kevany <chris.kevany@...>wrote:
> >
> > > **
>
> > >
> > >
> > > Hi Dimitris,
> > >
> > > I'm still strugling with Gui4Cli/Widows 7 compatibility
> > > issues and came across something at MSDN that says that
> > > Visual Studio 2008 needs SP1 to be compatible with Windows 7.
> > >
> > > Perhaps you know that already and had to install it anyway
> > > to run the app in the first place but I thought to mention
> > > it in case of.
> > >
> > > I also don't know if it would have any effect on the produced
> > > executables.
> > >
> > > 19.38 works still flawless in XP for whatever I add or change.
> > >
> > > Chris
> > >
> > >
> > >
> >
>
>  
>