• Announcements

    • xper

      MSFN Sponsorship and AdBlockers!   07/10/2016

      Dear members, MSFN is made available via subscriptions, donations and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, become a site sponsor and ads will be disabled automatically and by subscribing you get other sponsor benefits.
ppgrainbow

Skype 6.1 on Windows 2000

60 posts in this topic

Runtime error 217 at 0053CE7D report.

TypeLib GUID {B9AA1F11-F480-4054-A84E-B5D9277E40A8}

it returns 0x8002802A by oleaut32.dll in StringFromGUID2 step.

0053D200 50 push eax

0053D201 8B442410 mov eax,[esp+10h]

0053D205 50 push eax

0053D206 8B434C mov eax,[ebx+4Ch]

0053D209 50 push eax

0053D20A 8B00 mov eax,[eax]

0053D20C FF5038 call [eax+38h]

0053D20F E86C080000 call SUB_L0053DA80 <- eax=8002802A

0053D214 EB0C jmp L0053D222

SUB_L0053DA80:

test eax,80000000h

jz L0053DA8C

call SUB_L0053DA64 <- raise exception.

L0053DA8C:

retn

SUB_L0053DA64:

push ebx

mov ebx,eax

push ebx

push 00000000h

xor ecx,ecx

mov dl,01h

mov eax,[L0053A8C0]

call SUB_L0053D8F8

call SUB_L004075AC <-

pop ebx

retn

SUB_L004075AC:

or eax,eax

jnz L004075BA

mov eax,000000D8h

call SUB_L00407CC0

:

push ecx

push 00000001h

push 0EEDFADEh <- if occurs exception 0xEEDFADE

mov eax,esp

call edx

add esp,00000030h

L00407612:

jmp [L01636014]

retn

I think that it comes from the different of some components installed.

HKEY_CLASSES_ROOT\TypeLib\{B9AA1F11-F480-4054-A84E-B5D9277E40A8}

Skype.exe

it is created when skype.exe is starting.

But fail to create them on my environment.

0

Share this post


Link to post
Share on other sites

Is there anyone shows me the way to create VMWare Image, which Skype 6.1 can't recv message ? :(

My English environment only shows Runtime error.

0

Share this post


Link to post
Share on other sites

Is there anyone shows me the way to create VMWare Image, which Skype 6.1 can't recv message ? :(

My English environment only shows Runtime error.

I'll try to prepare such an image. The problem is not about receiving but about sending messages. Nothing happens when you click ENTER.

Edit: I've just send you the file on Twitter. Please check your PM.

Edited by tomasz86
0

Share this post


Link to post
Share on other sites

Thx tomasz86

But on your Image Skype 6.1 crashes Runtime Error same as me.

Your version is v6.0

I find that you can send message facemark only .

Is there anyone can run Skype 6.1 without Runtime Error ?

Is there anyone shows me the way to create VMWare Image, which Skype 6.1 can't recv message ? :(

My English environment only shows Runtime error.

I'll try to prepare such an image. The problem is not about receiving but about sending messages. Nothing happens when you click ENTER.

Edit: I've just send you the file on Twitter. Please check your PM.

0

Share this post


Link to post
Share on other sites

Is there anyone shows me the way to create VMWare Image, which Skype 6.1 can't recv message ? :(

I have to give you a no as well. 6.0 doesn't send messages, I can receive them though. 6.1 installs but I get a runtime error as well.

0

Share this post


Link to post
Share on other sites

I've just done some testing. The last version of Skype where you can send messages is 5.9.0.123. Sending messages doesn't work starting from versions 5.10.x.x. I've uploaded some of the older Skype versions to my Download Archive (navigate to Programs/Skype). After installing Skype 5.9.0.123 make sure that automatic updates are disabled in its settings.

Just in case here you can find changelog for Skype 5.10.

Edit: This registry entry seems to do the job when it comes to blocking Skype autoupdates:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Skype\Phone]
"DisableVersionCheckPolicy"=dword:00000001

Edited by tomasz86
0

Share this post


Link to post
Share on other sites

blackwingcat has managed to find a way to run Skype 6.1 and newer in Windows 2000:

http://blog.livedoor.jp/blackwingcat/archives/1759259.html

Unfortunately sending messages doesn't work (yet?) so Skype 5.9.0.123 is still the last fully functional version.

I try to install Exetended kernel v23a and Skype 6.2 in VMWare image which you provided at first.

But It seems no problem to send messages. :ph34r:

0

Share this post


Link to post
Share on other sites

I try to install Exetended kernel v23a and Skype 6.2 in VMWare image which you provided at first.

But It seems no problem to send messages. :ph34r:

I'm trying to do it right now but still nothing happens when trying to send text (only sending emoticons works). Would it be a problem for you to upload the WMWare image where sending messages work again?

I've managed to make it work in a VM but can't on my desktop. I'll try to do more tests to find out what the problem is about.

Edit: After more testing:

  1. Skype 6.2 works with BWC Kernel v23a but doesn't with UURollup-v11 daily. I don't know yet what the reason is.
  2. There's a problem though. After installing Skype 6.2 using blackwingcat's installer everything seems to work fine... but after reboot system fonts become something like this:
    J55BRKP.jpg
  3. In the blackwingcat's registry file there are these settings:
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\FontLink\SystemLink]
    "Helvetica"=hex(7):4d,00,53,00,47,00,4f,00,54,00,48,00,49,00,43,00,2e,00,54,00,54,\
    00,43,00,2c,00,4d,00,53,00,20,00,55,00,49,00,20,00,47,00,6f,00,74,00,68,00,\
    69,00,63,00,00,00,00,00
    "Tahoma"=hex(7):4d,00,53,00,47,00,4f,00,54,00,48,00,49,00,43,00,2e,00,54,00,54,\
    00,43,00,2c,00,4d,00,53,00,20,00,55,00,49,00,20,00,47,00,6f,00,74,00,68,00,\
    69,00,63,00,00,00,00,00
    "Arial"=hex(7):4c,00,5f,00,31,00,30,00,36,00,34,00,36,00,2e,00,54,00,54,00,46,\
    00,00,00,4d,00,53,00,47,00,4f,00,54,00,48,00,49,00,43,00,2e,00,54,00,54,00,\
    43,00,2c,00,4d,00,53,00,20,00,55,00,49,00,20,00,47,00,6f,00,74,00,68,00,69,\
    00,63,00,00,00,00,00
    "MS Sans Serif"=hex(7):4c,00,5f,00,31,00,30,00,36,00,34,00,36,00,2e,00,54,00,\
    54,00,46,00,00,00,4d,00,53,00,47,00,4f,00,54,00,48,00,49,00,43,00,2e,00,54,\
    00,54,00,43,00,2c,00,4d,00,53,00,20,00,55,00,49,00,20,00,47,00,6f,00,74,00,\
    68,00,69,00,63,00,00,00,00,00
    "Marlett"=hex(7):4c,00,5f,00,31,00,30,00,36,00,34,00,36,00,2e,00,54,00,54,00,\
    46,00,00,00,4d,00,53,00,47,00,4f,00,54,00,48,00,49,00,43,00,2e,00,54,00,54,\
    00,43,00,2c,00,4d,00,53,00,20,00,55,00,49,00,20,00,47,00,6f,00,74,00,68,00,\
    69,00,63,00,00,00,00,00
    "Microsoft Sans Serif"=hex(7):4d,00,53,00,47,00,4f,00,54,00,48,00,49,00,43,00,\
    2e,00,54,00,54,00,43,00,2c,00,4d,00,53,00,20,00,55,00,49,00,20,00,47,00,6f,\
    00,74,00,68,00,69,00,63,00,00,00,00,00


    And after transforming them to INF format:

    HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\FontLink\SystemLink","Helvetica",0x10000,"MSGOTHIC.TTC,MS UI Gothic"
    HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\FontLink\SystemLink","Tahoma",0x10000,"MSGOTHIC.TTC,MS UI Gothic"
    HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\FontLink\SystemLink","Arial",0x10000,"L_10646.TTF","MSGOTHIC.TTC,MS UI Gothic"
    HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\FontLink\SystemLink","MS Sans Serif",0x10000,"L_10646.TTF","MSGOTHIC.TTC,MS UI Gothic"
    HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\FontLink\SystemLink","Marlett",0x10000,"L_10646.TTF","MSGOTHIC.TTC,MS UI Gothic"
    HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\FontLink\SystemLink","Microsoft Sans Serif",0x10000,"MSGOTHIC.TTC,MS UI Gothic"


  4. I installed Skype 6.2 once again but this time without these font related keys... and fonts are fine after reboot and Skype itself also seems to work! What are the above font settings required for? :unsure:

Edited by tomasz86
0

Share this post


Link to post
Share on other sites

I've managed to make it work in a VM but can't on my desktop. I'll try to do more tests to find out what the problem is about.

Normaliz.dll was the culprit in case of UURollup (more info here).

Edited by tomasz86
0

Share this post


Link to post
Share on other sites

FontLink Setting is for Japanese one.

You can recover registry from %systemroot%\repair\system

Load Hive and Export it.

or Install Japanese setting.

I try to install Exetended kernel v23a and Skype 6.2 in VMWare image which you provided at first.

But It seems no problem to send messages. :ph34r:

I'm trying to do it right now but still nothing happens when trying to send text (only sending emoticons works). Would it be a problem for you to upload the WMWare image where sending messages work again?

I've managed to make it work in a VM but can't on my desktop. I'll try to do more tests to find out what the problem is about.

Edit: After more testing:

  1. Skype 6.2 works with BWC Kernel v23a but doesn't with UURollup-v11 daily. I don't know yet what the reason is.
  2. There's a problem though. After installing Skype 6.2 using blackwingcat's installer everything seems to work fine... but after reboot system fonts become something like this:
    J55BRKP.jpg
  3. In the blackwingcat's registry file there are these settings:
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\FontLink\SystemLink]
    "Helvetica"=hex(7):4d,00,53,00,47,00,4f,00,54,00,48,00,49,00,43,00,2e,00,54,00,54,\
    00,43,00,2c,00,4d,00,53,00,20,00,55,00,49,00,20,00,47,00,6f,00,74,00,68,00,\
    69,00,63,00,00,00,00,00
    "Tahoma"=hex(7):4d,00,53,00,47,00,4f,00,54,00,48,00,49,00,43,00,2e,00,54,00,54,\
    00,43,00,2c,00,4d,00,53,00,20,00,55,00,49,00,20,00,47,00,6f,00,74,00,68,00,\
    69,00,63,00,00,00,00,00
    "Arial"=hex(7):4c,00,5f,00,31,00,30,00,36,00,34,00,36,00,2e,00,54,00,54,00,46,\
    00,00,00,4d,00,53,00,47,00,4f,00,54,00,48,00,49,00,43,00,2e,00,54,00,54,00,\
    43,00,2c,00,4d,00,53,00,20,00,55,00,49,00,20,00,47,00,6f,00,74,00,68,00,69,\
    00,63,00,00,00,00,00
    "MS Sans Serif"=hex(7):4c,00,5f,00,31,00,30,00,36,00,34,00,36,00,2e,00,54,00,\
    54,00,46,00,00,00,4d,00,53,00,47,00,4f,00,54,00,48,00,49,00,43,00,2e,00,54,\
    00,54,00,43,00,2c,00,4d,00,53,00,20,00,55,00,49,00,20,00,47,00,6f,00,74,00,\
    68,00,69,00,63,00,00,00,00,00
    "Marlett"=hex(7):4c,00,5f,00,31,00,30,00,36,00,34,00,36,00,2e,00,54,00,54,00,\
    46,00,00,00,4d,00,53,00,47,00,4f,00,54,00,48,00,49,00,43,00,2e,00,54,00,54,\
    00,43,00,2c,00,4d,00,53,00,20,00,55,00,49,00,20,00,47,00,6f,00,74,00,68,00,\
    69,00,63,00,00,00,00,00
    "Microsoft Sans Serif"=hex(7):4d,00,53,00,47,00,4f,00,54,00,48,00,49,00,43,00,\
    2e,00,54,00,54,00,43,00,2c,00,4d,00,53,00,20,00,55,00,49,00,20,00,47,00,6f,\
    00,74,00,68,00,69,00,63,00,00,00,00,00


    And after transforming them to INF format:

    HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\FontLink\SystemLink","Helvetica",0x10000,"MSGOTHIC.TTC,MS UI Gothic"
    HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\FontLink\SystemLink","Tahoma",0x10000,"MSGOTHIC.TTC,MS UI Gothic"
    HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\FontLink\SystemLink","Arial",0x10000,"L_10646.TTF","MSGOTHIC.TTC,MS UI Gothic"
    HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\FontLink\SystemLink","MS Sans Serif",0x10000,"L_10646.TTF","MSGOTHIC.TTC,MS UI Gothic"
    HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\FontLink\SystemLink","Marlett",0x10000,"L_10646.TTF","MSGOTHIC.TTC,MS UI Gothic"
    HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\FontLink\SystemLink","Microsoft Sans Serif",0x10000,"MSGOTHIC.TTC,MS UI Gothic"


  4. I installed Skype 6.2 once again but this time without these font related keys... and fonts are fine after reboot and Skype itself also seems to work! What are the above font settings required for? :unsure:

Edited by blackwingcat
0

Share this post


Link to post
Share on other sites

Skype 6.9 and 6.10 on Windows 2000 crashes when its logon sequence.

It seems call "jmp [edx] (edx=0x00000204)."

How do I catch this exception (I want to know this call address.)?. Are there any ideas?

Edited by blackwingcat
0

Share this post


Link to post
Share on other sites

Skype 6.9/6.10 seem to require Windows XP Service Pack 3, and it seems to me an error I had when it was installed on Service Pack 2, it was related to CPU info or something like that. I doubt that answers your question but I think it might help you get started. All I know is the newest Skype versions will NOT work on Windows XP Service Pack 2 and below.

0

Share this post


Link to post
Share on other sites

Time to dig this up since it affects us Windows 2000 users to a degree. Tomasz86's version works for now...but what do we do after this deadline hits? The newest version will install, but calls cannot be made nor can files be sent since I just tested it out tonight. I don't know how long we have but this is not good news for us.

0

Share this post


Link to post
Share on other sites

Do you know what's the oldest Skype version to work in Windows 2000 at the moment?

Last time I checked, the old Skype 4.2 was still working fine.

0

Share this post


Link to post
Share on other sites

Do you know what's the oldest Skype version to work in Windows 2000 at the moment?

Last time I checked, the old Skype 4.2 was still working fine.

I'm using the latest one you have on your site so far, which is 6.3.32.105 but even that is giving me the 'your skype will retire soon' message. The reason I brought this up is I had version 5 something on my machine and it signed me out saying it was too old and would no longer work until I upgraded.

0

Share this post


Link to post
Share on other sites

You were right. This is what happens when trying to log in with Skype 4.2 in Windows 2000 <_<

 

MnwztNX.png

 

Using Application Compatibility Launcher to run it in XP SP3 mode doesn't help as Skype just crashes then.

0

Share this post


Link to post
Share on other sites

I use 5.2 on XP SP3, and it remains working OK. So the problem is just another MS device to force people to upgrade.

I wonder whether there may be a way to by-pass it or not...

1

Share this post


Link to post
Share on other sites

I use 5.2 on XP SP3, and it remains working OK. So the problem is just another MS device to force people to upgrade.

I wonder whether there may be a way to by-pass it or not...

I'm actually 100% sure that there is a way.

Why? This is a modified version of Skype for Android. You are unable to use the official Skype 2.x any more because it won't allow you to log in (same thing as with Skype 4.2 for Windows described above). However, with the modified versions you can log in and make calls even with the oldest one (v2.0.0.47) which means that the limitation is purely artificial.

0

Share this post


Link to post
Share on other sites

There was a way to bypass the MSN Messenger upgrade requirement by going into the actual exe file and changing the version number to something later than the particular file in question was. So for example, setting it from 11 to 13, the servers saw it as a newer version than it really was and it continued to work. So perhaps something like this here would work too? I think it was when MS required people to upgrade to the new MSN Live Messenger or whatever it was called. So maybe that could be a workaround???

0

Share this post


Link to post
Share on other sites

Interesting, Skype 3.5.0.239 still works under Windows 98. I can make calls and it doesn't force me to upgrade nor does it throw me out of the program.

0

Share this post


Link to post
Share on other sites

This is indeed interesting.

I've just checked two versions of Skype:

  • Skype 3.5.0.239
  • Skype 3.8.0.188
None of them work ("can't connect"). Is your Skype installation in Windows 98 new, or have you been using it for some time? I have a strange feeling that it may not work again if you reinstall and try to log in from scratch.
0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.