[Raport błędu] teamtalk.vbs 1.01Wouldn't it be nice, if the script developer, 
in the Package manager, had the chance of deciding the language, in which he 
wanted the error messages? Just like you can choose the main language for your 
script package. 

Also, many softwares, these days, throw upon you an error code. It doesn't tell 
the user much, but if there was some way of making WE give a certain code, and 
a list (online) of what these codes means, maybe we all could have benefitted. 
I am not of any help, in this particular case, as the text your user sent you, 
is way beyond my linguistic abiliies. So, I just put out these ideas, on a 
general base. 


  ----- Original Message ----- 
  From: Chip Orange 
  To: [email protected] 
  Sent: Monday, January 04, 2010 3:02 AM
  Subject: RE: [Raport bÅ,ÄTdu] teamtalk.vbs 1.01


  ROFL!!!

  ok, maybe I can help: I recently did have a TeamTalk error, and I couldn't 
send it to you because the toolkit locked up window eyes (as it sometimes 
does), after it began reading the error aloud.

  the problem was that the script hadn't shutdown after I had shutdown 
TeamTalk, and it gave me an error trying to process a windows explorer window.  
just an fyi in case this user had a similar issue.

  Chip





------------------------------------------------------------------------------
  From: J.J. Meddaugh [mailto:[email protected]] 
  Sent: Sunday, January 03, 2010 7:41 PM
  To: [email protected]
  Subject: Fw: [Raport bÅ,ÄTdu] teamtalk.vbs 1.01


      Hmmm,
  You know this is readable, but interesting because this user has the Toolkit 
script in another language that I get their errors in that language as well.

  J.J. Meddaugh - ATGuys.com
  A premier Licensed Code Factory and KNFB Reader distributor
  ----- Original Message ----- 
  From: [email protected] 
  To: [email protected] 
  Sent: Saturday, January 02, 2010 8:59 PM
  Subject: [Raport błędu] teamtalk.vbs 1.01



  Komentarz użytkownika: Brak komentarzy. 

  Wystąpił błąd teamtalk.vbs w 02:59:00 w 3 stycznia 2010.
  Name: teamtalk.vbs
  Wersja: 1.01
  Źródło: Microsoft VBScript - błąd czasu wykonywania
  Opis: Obiekt nie obsługuje tej właściwości lub metody.: 
'win.Parent.ModuleName'
  Kolumna: 1
  Linia: 138
  Ścieżka: C:\Documents and Settings\rolabik\Dane aplikacji\GW 
Micro\Window-Eyes\Users\Default
  Kod błędu: 800A01B6
  Skojarzenie skryptu: if instr(Win.Parent.ModuleName, 
myStrings("tModuleMain")) then
  Klasa Overlap Aktywnego Okna: 
  Tytuł aktywnego okna: 
  Moduł aktywnego okna: 
  Klasa aktywnego okna: 
  Klasa pochodzenia aktywnego okna: 
  Typ aktywnego okna: 0
  Typ pochodzenia aktywnego okna: 0
  Aktywne okno jest ważne: Fałsz
  Plik konfiguracyjny aktywnego okna: 
  Klasa Overlap Okna punktu uwagi: 
  Moduł okna puktu uwagi: 
  Klasa okna punktu uwagi: 
  Klasa pochodzenia punktu uwagi: 
  Typ okna punktu uwagi: 0
  Typ pochodzenia okna unktu uwagi: 0
  Okno punktu uwagi jest ważne: Fałsz
  Ścieżka programu Window-Eyes: C:\Program Files\GW Micro\Window-Eyes
  Ścieżka katalogu użytkownika Window-Eyes: C:\Documents and 
Settings\rolabik\Dane aplikacji\GW Micro\Window-Eyes\Users\Default\
  Wersja Window-Eyes: 7.11
  Język Window-Eyes: 1
  Aktywny syntezator: SMP lub Kajetek
  Aktywna linijka brajlowska: Brak
  Uruchom w tle: Fałsz
  Uruchom przy starcie: Fałsz
  Wersja sytemu operacyjnego: 5.1 (2600) SP: 3.0
  Wersja WSH: VBScript 5.8.18702
  Internet Explorer: 8.0.6001.18702
  GW Toolkit: 8.0.3
  Język XML: 1045
  Czas startu systemu: 2010-01-02 20:56:28
  Pojemność dysku twardego: 41,94GB
  Wolne miejsce na dysku twardym: 20,55GB
  Wielkość pamięci RAM: 2,01GB
  Wolna pamięć RAM: 1296,48MB
  Rozdzielczość: 1024x768 (32bit)
  Informacje o procesie: 
  System Idle Process ID:0, CPU Time:40954,17, MEM:0MB, VM:0MB
  System ID:4, CPU Time:61,08, MEM:0,2MB, VM:0MB
  smss.exe ID:676, CPU Time:0,05, MEM:0,4MB, VM:0,2MB
  csrss.exe ID:748, CPU Time:6,69, MEM:4,4MB, VM:1,5MB
  winlogon.exe ID:772, CPU Time:1,05, MEM:4,8MB, VM:7,6MB
  services.exe ID:816, CPU Time:4,34, MEM:3,4MB, VM:1,8MB
  lsass.exe ID:828, CPU Time:1,64, MEM:2MB, VM:3,8MB
  svchost.exe ID:988, CPU Time:0,17, MEM:5,1MB, VM:3,1MB
  svchost.exe ID:1048, CPU Time:2,22, MEM:4,4MB, VM:1,9MB
  svchost.exe ID:1136, CPU Time:7,69, MEM:29,9MB, VM:18,2MB
  svchost.exe ID:1248, CPU Time:0,11, MEM:3,6MB, VM:1,4MB
  svchost.exe ID:1360, CPU Time:0,16, MEM:7,5MB, VM:3,4MB
  spoolsv.exe ID:1572, CPU Time:0,03, MEM:4,8MB, VM:3,1MB
  explorer.exe ID:136, CPU Time:23,73, MEM:29,9MB, VM:21,2MB
  svchost.exe ID:492, CPU Time:0,02, MEM:3,7MB, VM:1,3MB
  AVKProxy.exe ID:560, CPU Time:0,77, MEM:1,3MB, VM:3,1MB
  networx.exe ID:596, CPU Time:2,17, MEM:12,2MB, VM:7,5MB
  rundll32.exe ID:608, CPU Time:0,28, MEM:3,9MB, VM:3MB
  AVKService.exe ID:616, CPU Time:4,28, MEM:2,1MB, VM:1,3MB
  AVKTray.exe ID:416, CPU Time:0,06, MEM:1,3MB, VM:1,8MB
  AVKWCtl.exe ID:744, CPU Time:2,09, MEM:9,6MB, VM:6,5MB
  jusched.exe ID:792, CPU Time:0,19, MEM:5,3MB, VM:1,5MB
  CTHELPER.EXE ID:120, CPU Time:0,45, MEM:4,2MB, VM:2,6MB
  RTHDCPL.EXE ID:1032, CPU Time:2,17, MEM:23,5MB, VM:20,4MB
  jqs.exe ID:1264, CPU Time:24,38, MEM:1,4MB, VM:15,7MB
  ctfmon.exe ID:1356, CPU Time:1,53, MEM:4,4MB, VM:1,6MB
  NBService.exe ID:1392, CPU Time:0,16, MEM:6,5MB, VM:4,2MB
  nvda_service.exe ID:944, CPU Time:0,08, MEM:6MB, VM:3,6MB
  nvsvc32.exe ID:192, CPU Time:0,16, MEM:4MB, VM:2,6MB
  svchost.exe ID:264, CPU Time:0,33, MEM:4,2MB, VM:2,4MB
  searchindexer.exe ID:1156, CPU Time:3,22, MEM:16,4MB, VM:19,2MB
  GDScan.exe ID:2100, CPU Time:37,64, MEM:12MB, VM:38,9MB
  wmiapsrv.exe ID:2164, CPU Time:0,14, MEM:4,5MB, VM:1,9MB
  alg.exe ID:2424, CPU Time:0,08, MEM:3,5MB, VM:1,2MB
  TeamTalk4Classic.exe ID:3548, CPU Time:875,28, MEM:19,4MB, VM:10,5MB
  wineyes.exe ID:1832, CPU Time:127,72, MEM:64,3MB, VM:116,5MB
  bdisplay.exe ID:2964, CPU Time:0,2, MEM:3,3MB, VM:1,6MB
  winamp.exe ID:5340, CPU Time:2,47, MEM:25,6MB, VM:14,6MB
  iexplore.exe ID:3736, CPU Time:1,28, MEM:17,2MB, VM:8,8MB
  iexplore.exe ID:1040, CPU Time:9,56, MEM:46MB, VM:36,9MB
  searchprotocolhost.exe ID:900, CPU Time:0,14, MEM:5,6MB, VM:4,6MB
  searchfilterhost.exe ID:5088, CPU Time:0,05, MEM:3,6MB, VM:2,3MB
  iexplore.exe ID:1488, CPU Time:2,11, MEM:18,2MB, VM:11,3MB
  AVK.exe ID:2224, CPU Time:0,03, MEM:4MB, VM:2,2MB
  wmiprvse.exe ID:364, CPU Time:0,08, MEM:4,8MB, VM:2,7MB
  wmiprvse.exe ID:4764, CPU Time:0,12, MEM:6,8MB, VM:2,6MB
  Inne: 

Reply via email to