TASClient .50 Unitsync Crash >>RESOLVED<<

[[BSG75]Lee_Adama]

Hi everyone,

So ever since TASClient started crashing on unitsync I've been less than happy, but after reading reports that it worked fine on Windows 7 I installed it and discovered that it was indeed fine!

Therefore Win7 became my primary OS (instead of Vista Ultimate). Today, though, .50 started crashing for me on Unitsync again

I tried to think what had changed in the last day, and the only thing I could think of was that I had installed two programs: one of them VirtualBox, and the other Office 2007 Ultimate.

Upon uninstalling Office 2007, TASClient .50 worked again! I used system restore roll back to before it was installed (it had automatically created a restore point) because Win7 kept complaining that 'this program may have not uninstalled correctly'.

I intend to reboot back into Windows Vista and uninstall Office 2007 Ultimate from there to see if it starts working again. Things to note about my installs:

-Both Win7 and Vista Ultimate are 64 bit
-Service Pack 2 and all available updates for Office '07 were installed

I hope this helps nail down the issue...Satirik?.

[Satirik]

tasclient works on both vista and seven 32bit i have with office 2007 ... i doubt the 64 version make it crash

[[BSG75]Lee_Adama]

I'm just telling you what I experienced.

Those are the only things that changed: Office 2007 Ultimate w/ Security and Service Pack Updates.

I haven't gone back to my Vista install yet to try it out.

[Licho]

Yes tasclient crashes on startup on my windows7 64bit too..

Due to unitsync..

[Satirik]

don't have win7 64 nor office 2007 so i can't help ...

[hoijui]

huh? resolved? :D

btw...
i think someone already mentioned this, but could it be that it is cause of the calling convention?
i neither have 64bit, i just know that unitsync 64bit uses the default caling-conv, as we do not specify any explicitly, like we do on 32bit (stdcall), i read about win64 bi calling conv some time ago, but o forgot most of it, i just remember that they are radically different from the 32bit ones.
just as a hint for anyone investigating.

[[BSG75]Lee_Adama]

tasclient works on both vista and seven 32bit i have with office 2007 ... i doubt the 64 version make it crash

don't have win7 64 nor office 2007 so i can't help ...

Those two statements seem to contradict each other Satirik...

@hoijui - I thought resolved would attract some attention and get some balls rolling onto what the next post could be titled "... FIXED"
And what you said about the calling conv is way over my head ... but hopefully not someone elses'.

[aegis]

calling convention

yeah, 'cept I use tasclient with win7 64-bit and have no problems.

[Satirik]

by "i have" i mean "im trying on a friend comp"

[[BSG75]Lee_Adama]

calling convention

yeah, 'cept I use tasclient with win7 64-bit and have no problems.

Aegis can you try installing Office 2007 Ultimate?

[Satirik]

huh? resolved? :D

btw...
i think someone already mentioned this, but could it be that it is cause of the calling convention?
i neither have 64bit, i just know that unitsync 64bit uses the default caling-conv, as we do not specify any explicitly, like we do on 32bit (stdcall), i read about win64 bi calling conv some time ago, but o forgot most of it, i just remember that they are radically different from the 32bit ones.
just as a hint for anyone investigating.

yeah it can't be calling convention unless office 2007 changes it

[[BSG75]Lee_Adama]

huh? resolved? :D

btw...
i think someone already mentioned this, but could it be that it is cause of the calling convention?
i neither have 64bit, i just know that unitsync 64bit uses the default caling-conv, as we do not specify any explicitly, like we do on 32bit (stdcall), i read about win64 bi calling conv some time ago, but o forgot most of it, i just remember that they are radically different from the 32bit ones.
just as a hint for anyone investigating.

yeah it can't be calling convention unless office 2007 changes it

I just thought I'd share with you my experience on what caused my issues. I thought as a developer you'd appreciate bug reports / insight in fixing issues most of your user base is having and waiting on you to fix. Just because your development machines don't experience issues doesn't mean that the end users' machines don't as well.

It's your choice on whether to use my information or not; just don't be smug about it

[Satirik]

when you don't understand something don't make conclusion about it please

[[BSG75]Lee_Adama]

when you don't understand something don't make conclusion about it please

Well when it's pretty evident what changed in less than 12 hours and what the effects where... I never said I understood what happened, I said I was sharing what I experienced in the hopes that it would help someone who did understand.

Sat. Night: 0.50 doesn't have Unitsync crash.
Sun Morning: install Office Ultimate 2007 and install office updates - .50 experiences Unitsync crash.

Seems pretty clear to me, unless you have any suggestions. Oh wait, you don't, just criticism for someone trying to help you debug.

[Satirik]

i was quoting hoiji and telling HIM (not you) that what he said is not possible ... because calling convention can't be changed by office 2007 ... stop being paranoiac please

and i am glad you posted that

[Forboding Angel]

Really? Hmm, so reinstalling office2007 fixed it for you? Well fuckit, I'll try and post back here with the results.

[Satirik]

where the fuck did you read that forb ?

[Licho]

Unitsync crash is not happening on all 64bit OSes, its not a calling convention. Its even possible its related to office2007, since i have it too..

[hoijui]

So win 7 only works right if you get office too?
would anyone be surprised by this?

[Forboding Angel]

Nothing to do with win7. Office is necessary because I need spreadsheets that don't suck i.e. openoffice, and word2007 is the only processor that always opens docx correctly.

There are good reasons for having both