111 replies to this topic

[Killer UT]

I downloaded the latest version as advised, and was able to get it to work fine on my home workstation, as well as my work workstation. However, I think part of the problem with APUP stopping downloading might be a speed issue.

I ran some tests between home and work. At home, I have a 15Mbps Cable connection, and I was able to run APUP completely. It downloaded everything, and finished without a problem. However, when I took my same machine to work and ran APUP on our 1Gbps connection, I had to restart the download numerous times.

[Cyrus]

Antonis will create a feature which will retry the download if it gets stuck, but he also has things in the non-digital world which require a large amount of his time, so I don't know when the next version will be released which may fix that problem.

Edited by Cyrus, 06 December 2007 - 09:43 PM.

[Docfxit]

I thought a little feed back might help resolve the issues.

The latest version 1.00.0003 file dated 12/3/07 is defiantly much better. I'm not getting the runtime error any more.
It is getting stuck downloading a MS file.

My Log

The log looks fine to me. To help resolve the issues he might consider including information in the log that might help in resolving the bugs.

This was run in XP Pro sp2.

Call Stacks:
Thread ID: 0x844
WinMainBody(0x400000, , , 1)
WinMainBody::FindLatestConfiguration
WinMainBody::StartupDialog
WinMainBody::inicialization
WinMainBody::load_config
WinMainBody::message_loop
CMainWindow::WindowProc(0x111, 0x32A, 0x0)
----
Thread ID: 0xB70
ThreadCacheHandlesBody()
CCacheHandles::WaitForObjects(,)
----
Thread ID: 0xC88
ThreadCheckPathFBody()
----
Thread ID: 0xD24
ThreadSnooperBody()
----
Thread ID: 0xE18
ThreadFindCloseChangeNotificationBody()
----
Thread ID: 0x4C4
IconThreadThreadFBody()
----
Thread ID: 0x96C
IconThreadThreadFBody()
----
Thread ID: 0xC0C
ThreadSafeWaitWindowFBody()

Main Thread WayPoints:
wp=14 cd1=0x0 cd2=0x0 t=-10812
wp=2 cd1=0x200 cd2=0x0 t=-10797
wp=4 cd1=0x0 cd2=0xC0157 t=-10797
wp=5 cd1=0x0 cd2=0x0 t=-10797
wp=6 cd1=0x0 cd2=0x0 t=-10797
wp=7 cd1=0x0 cd2=0xC0157 t=-10797
wp=8 cd1=0x0 cd2=0x0 t=-10797
wp=9 cd1=0x0 cd2=0x0 t=-10797
wp=10 cd1=0x1 cd2=0x0 t=-10797
wp=12 cd1=0x0 cd2=0x0 t=-10797
wp=13 cd1=0x0 cd2=0x0 t=-10797
wp=14 cd1=0x0 cd2=0x0 t=-10797
wp=2 cd1=0x200 cd2=0x0 t=-10781
wp=4 cd1=0x0 cd2=0xC0156 t=-10781
wp=5 cd1=0x0 cd2=0x0 t=-10781
wp=6 cd1=0x0 cd2=0x0 t=-10781
wp=7 cd1=0x0 cd2=0xC0156 t=-10781
wp=8 cd1=0x0 cd2=0x0 t=-10781
wp=9 cd1=0x0 cd2=0x0 t=-10781
wp=10 cd1=0x1 cd2=0x0 t=-10781
wp=12 cd1=0x0 cd2=0x0 t=-10781
wp=13 cd1=0x0 cd2=0x0 t=-10781
wp=14 cd1=0x0 cd2=0x0 t=-10781
wp=2 cd1=0x200 cd2=0x0 t=-10781
wp=4 cd1=0x0 cd2=0xC0155 t=-10781
wp=5 cd1=0x0 cd2=0x0 t=-10781
wp=6 cd1=0x0 cd2=0x0 t=-10781
wp=7 cd1=0x0 cd2=0xC0155 t=-10781
wp=8 cd1=0x0 cd2=0x0 t=-10781
wp=9 cd1=0x0 cd2=0x0 t=-10781
wp=10 cd1=0x1 cd2=0x0 t=-10781
wp=12 cd1=0x0 cd2=0x0 t=-10781
wp=13 cd1=0x0 cd2=0x0 t=-10781
wp=14 cd1=0x0 cd2=0x0 t=-10781
wp=2 cd1=0x200 cd2=0x0 t=-10765
wp=4 cd1=0x0 cd2=0xC0154 t=-10765
wp=5 cd1=0x0 cd2=0x0 t=-10765
wp=6 cd1=0x0 cd2=0x0 t=-10765
wp=7 cd1=0x0 cd2=0xC0154 t=-10765
wp=8 cd1=0x0 cd2=0x0 t=-10765
wp=9 cd1=0x0 cd2=0x0 t=-10765
wp=10 cd1=0x1 cd2=0x0 t=-10765
wp=12 cd1=0x0 cd2=0x0 t=-10765
wp=13 cd1=0x0 cd2=0x0 t=-10765
wp=14 cd1=0x0 cd2=0x0 t=-10765
wp=2 cd1=0x200 cd2=0x0 t=-10750
wp=4 cd1=0x0 cd2=0xC0153 t=-10750
wp=5 cd1=0x0 cd2=0x0 t=-10750
wp=6 cd1=0x0 cd2=0x0 t=-10750
wp=7 cd1=0x0 cd2=0xC0153 t=-10750
wp=8 cd1=0x0 cd2=0x0 t=-10750
wp=9 cd1=0x0 cd2=0x0 t=-10750
wp=10 cd1=0x1 cd2=0x0 t=-10750
wp=12 cd1=0x0 cd2=0x0 t=-10750
wp=13 cd1=0x0 cd2=0x0 t=-10750
wp=14 cd1=0x0 cd2=0x0 t=-10750
wp=2 cd1=0x201 cd2=0x0 t=-10515
wp=4 cd1=0x1 cd2=0xC0153 t=-10515
wp=5 cd1=0x0 cd2=0x0 t=-10515
wp=6 cd1=0x0 cd2=0x0 t=-10515
wp=7 cd1=0x1 cd2=0xC0153 t=-10515
wp=8 cd1=0x0 cd2=0x0 t=-10515
wp=9 cd1=0x0 cd2=0x0 t=-6281
wp=10 cd1=0x1 cd2=0x0 t=-6281
wp=11 cd1=0x806F cd2=0x180176 t=-6281
wp=2 cd1=0x806F cd2=0x0 t=-6281
wp=4 cd1=0x0 cd2=0x0 t=-6281
wp=5 cd1=0x0 cd2=0x0 t=-6281
wp=6 cd1=0x0 cd2=0x0 t=-6281
wp=7 cd1=0x0 cd2=0x0 t=-6281
wp=8 cd1=0x0 cd2=0x0 t=-6281
wp=9 cd1=0x0 cd2=0x0 t=-6281
wp=10 cd1=0x1 cd2=0x0 t=-6281
wp=11 cd1=0x806F cd2=0x3E022E t=-6281
wp=2 cd1=0x806F cd2=0x0 t=-6281
wp=4 cd1=0x0 cd2=0x0 t=-6281
wp=5 cd1=0x0 cd2=0x0 t=-6281
wp=6 cd1=0x0 cd2=0x0 t=-6281
wp=7 cd1=0x0 cd2=0x0 t=-6281
wp=8 cd1=0x0 cd2=0x0 t=-6281
wp=9 cd1=0x0 cd2=0x0 t=-6281
wp=10 cd1=0x1 cd2=0x0 t=-6281
wp=11 cd1=0x200 cd2=0x270220 t=-6281
wp=2 cd1=0x200 cd2=0x0 t=-6281
wp=4 cd1=0x0 cd2=0x500186 t=-6281
wp=5 cd1=0x0 cd2=0x0 t=-6281
wp=6 cd1=0x0 cd2=0x0 t=-6281
wp=7 cd1=0x0 cd2=0x500186 t=-6281
wp=8 cd1=0x0 cd2=0x0 t=-6281
wp=9 cd1=0x0 cd2=0x0 t=-6281
wp=10 cd1=0x1 cd2=0x0 t=-6281
wp=11 cd1=0x111 cd2=0x2E018E t=-6281
wp=2 cd1=0x111 cd2=0x0 t=-6281
wp=4 cd1=0x32A cd2=0x0 t=-6281
wp=5 cd1=0x0 cd2=0x0 t=-6281
wp=6 cd1=0x0 cd2=0x0 t=-6281
wp=7 cd1=0x32A cd2=0x0 t=-6281
wp=8 cd1=0x0 cd2=0x0 t=-6281
wp=103 cd1=0x0 cd2=0x0 t=-6250
wp=103 cd1=0x1 cd2=0x0 t=0

Global Variables:
StopRefresh = 0
SnooperSuspended = 0
ActivateSuspMode = 0
FullRowSelect = 0
OnlyOneInstance = 0
StatusArea = 0
UseRecycleBin = 1
CnfrmDragDrop = 0
AlwaysOnTop = 0
SortUsesLocale = 1
SortDetectNumbers = 1
SortNewerOnTop = 0
SortDirsByName = 0
SortDirsByExt = 0
EHasOccured = 0, 0, 0, 0, 0, 0, 0, 0, 0
ConfigWasImported = 0
UseSalOpen = 0
AutoSave = 1
IfPathIsInaccessibleGoTo (isMyDocs = 1) =
NoDrives = 0x00000000
NoFind = 0
VisibleDrives = 0x03FFFFFF

Panels:
Left panel (target):
Path = C:\Dnload
PanelType = 0
Dirs = 5
Files = 25
SelectedCount = 0
FileBasedCompression = 1
FileBasedEncryption = 1
FAT32Drive = 0
SupportACLS = 1
Network Drive = 0
DeviceNotification = 0x0017A628
UseSystemIcons = 1
UseThumbnails = 0
SuppressAutoRefresh = 0
MonitorChanges = 1
IconCacheValid = 1
AutomaticRefresh = 1
ViewMode = 1
SortType = 0
ReverseSort = 0
SortedWithRegSet = 1
SortedWithDetectNum = 1
NextFocusName =
FocusFirstNewItem = 0
HiddenDirsFilesReason = 0
HiddenDirsCount = 0
HiddenFilesCount = 0
FilterEnabled = 0
QuickSearchMode = 0
FocusedIndex = 5
FocusVisible = 0
TrackingSingleClick = 0
UserWorkedOnThisPath = 1
StopThumbnailLoading = 0
EnumFileNamesSourceUID = 10

Right panel (source):
Path = C:\Program Files\AutoPatcher Updater
PanelType = 0
Dirs = 3
Files = 11
SelectedCount = 0
FileBasedCompression = 1
FileBasedEncryption = 1
FAT32Drive = 0
SupportACLS = 1
Network Drive = 0
DeviceNotification = 0x00166058
UseSystemIcons = 1
UseThumbnails = 0
SuppressAutoRefresh = 0
MonitorChanges = 1
IconCacheValid = 1
AutomaticRefresh = 1
ViewMode = 1
SortType = 0
ReverseSort = 0
SortedWithRegSet = 1
SortedWithDetectNum = 1
NextFocusName =
FocusFirstNewItem = 1
HiddenDirsFilesReason = 0
HiddenDirsCount = 0
HiddenFilesCount = 0
FilterEnabled = 0
QuickSearchMode = 0
FocusedIndex = 4
FocusVisible = 1
TrackingSingleClick = 0
UserWorkedOnThisPath = 1
StopThumbnailLoading = 0
EnumFileNamesSourceUID = 9

Modules:
0x00400000 (size: 0x19C000) (ver: 2.5.0.0): SALAMAND.exe (C:\Program Files\Salamander 2.5\SALAMAND.exe)
0x7C900000 (size: 0xB0000) (ver: 5.1.2600.2180): ntdll.dll (C:\WINDOWS\system32\ntdll.dll)
0x7C800000 (size: 0xF5000) (ver: 5.1.2600.3119): kernel32.dll (C:\WINDOWS\system32\kernel32.dll)
0x23900000 (size: 0x30000) (ver: 6.0.0.0): SALRTL.DLL (C:\Program Files\Salamander 2.5\SALRTL.DLL)
0x7E410000 (size: 0x90000) (ver: 5.1.2600.3099): USER32.dll (C:\WINDOWS\system32\USER32.dll)
0x77F10000 (size: 0x47000) (ver: 5.1.2600.3159): GDI32.dll (C:\WINDOWS\system32\GDI32.dll)
0x763B0000 (size: 0x49000) (ver: 6.0.2900.2180): comdlg32.dll (C:\WINDOWS\system32\comdlg32.dll)
0x77F60000 (size: 0x76000) (ver: 6.0.2900.3199): SHLWAPI.dll (C:\WINDOWS\system32\SHLWAPI.dll)
0x77DD0000 (size: 0x9B000) (ver: 5.1.2600.2180): ADVAPI32.dll (C:\WINDOWS\system32\ADVAPI32.dll)
0x77E70000 (size: 0x92000) (ver: 5.1.2600.3173): RPCRT4.dll (C:\WINDOWS\system32\RPCRT4.dll)
0x77FE0000 (size: 0x11000) (ver: 5.1.2600.2180): Secur32.dll (C:\WINDOWS\system32\Secur32.dll)
0x77C10000 (size: 0x58000) (ver: 7.0.2600.3085): msvcrt.dll (C:\WINDOWS\system32\msvcrt.dll)
0x773D0000 (size: 0x103000) (ver: 6.0.2900.2982): COMCTL32.dll (C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.2982_x-ww_ac3f9c03\COMCTL32.dll)
0x7C9C0000 (size: 0x817000) (ver: 6.0.2900.3241): SHELL32.dll (C:\WINDOWS\system32\SHELL32.dll)
0x774E0000 (size: 0x13D000) (ver: 5.1.2600.2846): ole32.dll (C:\WINDOWS\system32\ole32.dll)
0x77120000 (size: 0x8B000) (ver: 5.1.2600.3139): OLEAUT32.dll (C:\WINDOWS\system32\OLEAUT32.dll)
0x71B20000 (size: 0x12000) (ver: 5.1.2600.2180): MPR.dll (C:\WINDOWS\system32\MPR.dll)
0x5AD70000 (size: 0x38000) (ver: 6.0.2900.2523): uxtheme.dll (C:\WINDOWS\system32\uxtheme.dll)
0x21900000 (size: 0x34000) (ver: 2.5.0.0): english.slg (C:\Program Files\Salamander 2.5\lang\english.slg)
0x77920000 (size: 0xF3000) (ver: 5.1.2600.2180): SETUPAPI.dll (C:\WINDOWS\system32\SETUPAPI.dll)
0x77B40000 (size: 0x22000) (ver: 5.1.2600.2180): appHelp.dll (C:\WINDOWS\system32\appHelp.dll)
0x76FD0000 (size: 0x7F000) (ver: 2001.12.4414.310): CLBCATQ.DLL (C:\WINDOWS\system32\CLBCATQ.DLL)
0x77050000 (size: 0xC5000) (ver: 2001.12.4414.258): COMRes.dll (C:\WINDOWS\system32\COMRes.dll)
0x77C00000 (size: 0x8000) (ver: 5.1.2600.2180): VERSION.dll (C:\WINDOWS\system32\VERSION.dll)
0x77A20000 (size: 0x54000) (ver: 5.1.2600.2180): cscui.dll (C:\WINDOWS\System32\cscui.dll)
0x76600000 (size: 0x1D000) (ver: 5.1.2600.2180): CSCDLL.dll (C:\WINDOWS\System32\CSCDLL.dll)
0x5B860000 (size: 0x55000) (ver: 5.1.2600.2976): NETAPI32.DLL (C:\WINDOWS\system32\NETAPI32.DLL)
0x20000000 (size: 0x2C5000) (ver: 5.1.2600.2180): xpsp2res.dll (C:\WINDOWS\system32\xpsp2res.dll)
0x723A0000 (size: 0xF000) (ver: 5.1.2600.2180): mmcshext.dll (C:\WINDOWS\System32\mmcshext.dll)
0x76080000 (size: 0x65000) (ver: 6.2.3104.0): MSVCP60.dll (C:\WINDOWS\System32\MSVCP60.dll)
0x723B0000 (size: 0xE000) (ver: 5.2.3790.2453): hhsetup.dll (C:\WINDOWS\System32\hhsetup.dll)
0x21100000 (size: 0x40000) (ver: 1.2.2.0): zip.spl (C:\Program Files\Salamander 2.5\plugins\zip\zip.spl)
0x31100000 (size: 0x11000) (ver: 1.2.2.0): english.slg (C:\Program Files\Salamander 2.5\plugins\zip\lang\english.slg)
0x10000000 (size: 0xF000) (ver: 1.0.0.1004): SASCTXMN.DLL (C:\Program Files\SUPERAntiSpyware\SASCTXMN.DLL)
0x018D0000 (size: 0x12000) (ver: 1.0.0.2): ue32ctmn.dll (C:\Program Files\UltraEdit-32\ue32ctmn.dll)
0x01C70000 (size: 0x37000) (ver: 3.8.0.0): PWRISOSH.DLL (C:\Program Files\PowerISO\PWRISOSH.DLL)
0x73000000 (size: 0x26000) (ver: 5.1.2600.2180): WINSPOOL.DRV (C:\WINDOWS\system32\WINSPOOL.DRV)
0x01940000 (size: 0x10000) (ver: unknown): ContextMenuExt.dll (C:\WINDOWS\ContextMenuExt.dll)
0x01CC0000 (size: 0x18000) (ver: 8.4.0.24): avshlext.dll (C:\Program Files\eTrust\CA Anti-Virus\avshlext.dll)
0x708F0000 (size: 0x13000) (ver: 5.1.2600.2180): asycfilt.dll (C:\WINDOWS\system32\asycfilt.dll)
0x02200000 (size: 0x14000) (ver: 1.0.0.1008): SASSEH.DLL (C:\Program Files\SUPERAntiSpyware\SASSEH.DLL)
0x7E1E0000 (size: 0xA2000) (ver: 6.0.2900.3199): urlmon.dll (C:\WINDOWS\system32\urlmon.dll)
0x76C30000 (size: 0x2E000) (ver: 5.131.2600.2180): WINTRUST.dll (C:\WINDOWS\system32\WINTRUST.dll)
0x77A80000 (size: 0x94000) (ver: 5.131.2600.2180): CRYPT32.dll (C:\WINDOWS\system32\CRYPT32.dll)
0x77B20000 (size: 0x12000) (ver: 5.1.2600.2180): MSASN1.dll (C:\WINDOWS\system32\MSASN1.dll)
0x76C90000 (size: 0x28000) (ver: 5.1.2600.2180): IMAGEHLP.dll (C:\WINDOWS\system32\IMAGEHLP.dll)
0x0FFD0000 (size: 0x28000) (ver: 5.1.2600.2161): rsaenh.dll (C:\WINDOWS\system32\rsaenh.dll)
0x02020000 (size: 0x2F000) (ver: 5.1.2600.2180): xpsp1res.dll (C:\WINDOWS\system32\xpsp1res.dll)
0x76F60000 (size: 0x2C000) (ver: 5.1.2600.2180): WLDAP32.dll (C:\WINDOWS\system32\WLDAP32.dll)
0x769C0000 (size: 0xB3000) (ver: 5.1.2600.2180): USERENV.dll (C:\WINDOWS\system32\USERENV.dll)
0x76E10000 (size: 0x25000) (ver: 5.1.2600.2180): adsldpc.dll (C:\WINDOWS\system32\adsldpc.dll)

Unloaded Modules:
(885359 ms) 0x519A0000 (size: 0x11000) (ver: 5.7.0.16535): wshext.dll (C:\WINDOWS\system32\wshext.dll)
(4815359 ms) 0x5C7E0000 (size: 0x9000) (ver: 5.1.2600.2180): SlayerXP.dll (C:\WINDOWS\system32\SlayerXP.dll)
(4815359 ms) 0x5D680000 (size: 0xD000) (ver: 5.1.2600.2180): rshx32.dll (C:\WINDOWS\system32\rshx32.dll)
(885359 ms) 0x60980000 (size: 0x7000) (ver: 3.1.4000.1823): MSISIP.DLL (C:\WINDOWS\system32\MSISIP.DLL)
(4815359 ms) 0x62C30000 (size: 0x10000) (ver: 6.0.3800.2721): twext.dll (C:\WINDOWS\system32\twext.dll)
(4815359 ms) 0x6C840000 (size: 0xF000) (ver: 5.1.2600.2180): docprop2.dll (C:\WINDOWS\system32\docprop2.dll)
(4815359 ms) 0x6C850000 (size: 0x10000) (ver: 5.1.2600.0): docprop.dll (C:\WINDOWS\system32\docprop.dll)
(4815359 ms) 0x6DC20000 (size: 0xF000) (ver: 5.131.2600.2180): cryptext.dll (C:\WINDOWS\system32\cryptext.dll)
(4815359 ms) 0x71550000 (size: 0x1F000) (ver: 5.1.2600.2180): aclui.dll (C:\WINDOWS\system32\aclui.dll)
(4815359 ms) 0x754D0000 (size: 0x80000) (ver: 5.131.2600.2180): CRYPTUI.dll (C:\WINDOWS\system32\CRYPTUI.dll)
(4815359 ms) 0x76B20000 (size: 0x11000) (ver: 3.5.2284.0): ATL.DLL (C:\WINDOWS\system32\ATL.DLL)
(4815359 ms) 0x76BB0000 (size: 0x5000) (ver: 5.1.2600.2180): sfc.dll (C:\WINDOWS\system32\sfc.dll)
(4815359 ms) 0x76C60000 (size: 0x2A000) (ver: 5.1.2600.2180): sfc_os.dll (C:\WINDOWS\system32\sfc_os.dll)
(4815359 ms) 0x771B0000 (size: 0xAA000) (ver: 6.0.2900.3199): WININET.dll (C:\WINDOWS\system32\WININET.dll)
(4815359 ms) 0x776C0000 (size: 0x11000) (ver: 5.1.2600.2622): AUTHZ.dll (C:\WINDOWS\system32\AUTHZ.dll)
(4815359 ms) 0x77CC0000 (size: 0x32000) (ver: 5.1.2600.2180): ACTIVEDS.dll (C:\WINDOWS\system32\ACTIVEDS.dll)


Bug Report Time: 5.12.2007 - 08:13:20
System Started Before: 1:16:45:53

Module Name: C:\Program Files\Salamander 2.5\SALAMAND.exe
Built: Apr 27 2007, 11:54:07
Country: 1 (United States)
Language: 0409 (English)
Code Page: 1252

System Version:
Microsoft Windows XP Professional Service Pack 2 (Build 2600)
Version 5.1 (Build 2600) SP 2.0, Service Pack 2
System directory: C:\WINDOWS\system32
Windows directory: C:\WINDOWS
IE Version: 6.0.2900.2180 Build: 62900.2180
COMCTL32.DLL Version: 6.0
ProductName (from registry): Microsoft Windows XP
CurrentVersion (from registry): 5.1

Other Information:
User is Admin: yes
Terminal Services: running on the console

Hardware Information:
OEM ID: 0x0
Number of Processors: 2
Processor Type: 586
Processor Architecture: 0
Processor Level: 15
Processor Vendor Name: GenuineIntel
Processor Name: Intel® Pentium® D CPU 3.40GHz
Processor Speed: ~3391 MHz
Page size: 4096
Minimum app address: 0x10000
Maximum app address: 0x7FFEFFFF
Active processor mask: 0x3
Mouse is installed
Total Physical Memory: 1046756 KB
Free Physical Memory: 308744 KB
Total Virtual Memory: 2097024 KB
Free Virtual Memory: 2031716 KB
BIOS Version: LENOVO - 37
BIOS Date: 07/12/07
Monitor 1: (0,0)-(1024,768) 1024x768 pixels, planes: 1, bits per pixel: 32, primary display
Monitor 1 Device Name: Radeon X1600 Series

Drives:
A:\ [removable]
Device: \Device\Floppy0
C:\ [fixed]
SN: A080-8373 FL: 0x000700FF FS: NTFS LN: yes
BytePerSec: 512 SecPerClus: 8 Clusters: 59,913,215
Capacity: 229 GB Free: 216 GB Used: 13 GB
Device: \Device\HarddiskVolume2
D:\ [cdrom]
Device: \Device\CdRom0
E:\ [cdrom]
Device: \Device\SCDEmu\SCDEmuCd0

End.

Thank you for your efforts,

Docfxit

[Cyrus]

That's a known bug in apup, it will just randomly stop downloading. If you close it, select the same list, and hit download again, it should continue from where it left off.

[James]

It also sounds very like a bug in Microsoft's Winsock control (MSWINSCK.OCX) that APUP uses.

I am by no means an expert VB6, or network protocol programmer, but MSWINSCK.OCX has a well-known flakey history of dropping bytes, overflowing its internal buffers and trying to send/receive data after the "Close" event has been triggered.

A Google search on "Winsock control bugs" will bring enough relevant hits to put most people off!!
--
James

[cwq1]

I just ran into a problem running APUP after downloading it a couple of hours ago on a semi-fresh install of Windows XP OEM w/Service Pack 2. Since this machine was due to be Ghosted, I had not activated with WGA yet, but I had downloaded all the updates that Windows Update allowed (IE7 and a few others).

Upon launching apup.exe I was presented with a graphical window with this text:

What AutoPatcher was trying to do
It appears that the error occured while AutoPatcher was trying to get commandline arguments.

Where: mdlInitialization.Main()
Error Code: 0x174: Failed to load control 'ProgressBar' from COMCTL32.OCX.  Your version of COMCTL32.OCX may be outdated.  Make sure you are using the version of the control that was provided with your application.

And here is what was contained in the View Log screen:

Attempting to initialize common controls.
Accessing filesystem...
AutoPatcher 5.6 loaded the filesystem.

Detected English (1033) Windows XP Professional Service Pack 2

System Components:
	Internet Explorer: 7.0.6000.16544
	Windows Media Player: 9.0.0.3354
	.NET Framework: 
	Windows Installer: 3.1.4000.1823
	DirectX: 4.09.00.0904
	MSN/Live Messenger: 

Office Components:
	Microsoft Word: 
	Microsoft Excel: 
	Microsoft PowerPoint: 
	Microsoft Outlook: 
	Microsoft Access: 
	Microsoft Project: 
	Microsoft Publisher: 
	Microsoft OneNote: 
	Microsoft FrontPage: 
	Microsoft InfoPath: 
	Microsoft Visio: 
	Microsoft SharePoint Designer: 
	Microsoft Groove:

I managed to resolve this by downloading the Visual Basic 6 Common Controls attached to this Microsoft KB Article: KB 896559

I hope this helps!

[italianstyle]

just my 2 cents about "solving" freezes.
i've never been able to download all at once so waiting for the fixes in apup this could work... well... it did for me ^^

Pay attention! Maybe you have to change 127.0.0.1 with your lan address. you can find the correct one for you opening hfs.exe and looking in the address bar. For me it was 192.168.1.2 for example.

single quotes are there as markers, remove them.
1) create a new folder called 'wwwroot'. create two subfolders called 'updates' and 'releases'.
2) download 'www.autopatcher.com/releases.list' and save it inside 'wwwroot'.
3) download needed .script files from www.autopatcher.com and save them inside 'releases'. The links are inside the 'releases.list' file. 
4) from a command prompt navigate to your 'releases' folder, then execute 'copy *.script download.html'
5) open 'download.html' with yout text editor and replace 'DownloadFrom=' with '<a href="' and 'DownloadTo' with '">link</a>'.
6) save, open it in your browser and use your download manager to save everything in the folder 'updates'
7) download hfs.exe and, recommended, Notepad++
8) open 'releases.list' with Notepad++ and press CTRL+H. replace 'www.autopatcher.com/.*/' with '127.0.0.1/releases/' and be sure to flag the regex expression checkbox. save and close.
8a) additionally it is advisable to remove from 'releases.list' every script you don't need.
9) do the following replacements as explained before in every .script file in the 'releases' folder and save. remember to flag the regex expression checkbox. replace 'www.autopatcher.com/.*/', 'download.microsoft.com/.*/' and 'download.windowsupdate.com/.*/' with '127.0.0.1/updates/'.
10) add '127.0.0.1 www.autopatcher.com' to 'c:\windows\system32\drivers\etc\hosts'
11) start hfs.exe, right click in the left panel and choose "add folder from disk". locate your 'releases' folder and press OK. choose real folder when asked. repeat to include your 'updates' folder. right click one more time, "add files" this time and choose 'releases.list' from your 'wwwroot' folder. check the program is active (F4 to switch or Menu->switch On) and the firewall is not blocking it. moreover uncheck the flag from "Menu->limits->prevent leeching".
12) now you are ready to start apup.exe as usual. if you have followed 8a) you should have only the scripts you need in the main window. 

Of course when you're done restore your HOSTS file removing the '127.0.0.1 www.autopatcher.com' line.

feel free to remove/modify this post if considered inappropriate.

[Erik Ramey]

Makes perfect sense but unsure if the above post would be a good idea for the typical everyday user. Renato or Antonis will make this decision as Full Administrators to this forum.

[sh1leshk4]

IMHO, too much fuss for a workaround that isn't necessarily needed; probably'd generate more posts that'd ask about how to properly get the workaround to actually work instead of apup.exe bug reports.

But, again, that's just my opinion. =)

[noorman]

.


I 've tried two versions of apup now; both can't give me the complete download of the complete package I 'ticked'.

The last version (from only a few days ago) did go to ~65 % and then stopped.
An exit and restart didn't yield the promised re-take ...

I 've proceeded (for the 2nd time) to apply all 'Critical' patches by hand from the download folder.

I had tried twce or thrice with the first version.
this way my monthly data volume will be eaten very quickly and I will be switched to 64kb/s surfing !
NOT VERY PLEASANT !


If this is possible with the latest version, HOW do I re-take the download without starting at ZERO, please ???



.

[Rudy]

you don't need to start at zero

if you have downloaded 65% in the first take, and stops/freezes, it would continue from 65% when you run apup.exe again.

apup.exe checks if files have been downloaded, and only downloads missing files or new ones

[sh1leshk4]

@noorman

Which "two versions"...?
Both the older 1.0.3 and newer 1.0.3...? What?

Anyway if you're trying "both versions" don't mix it up in the same directory as the previous one you tried.
i.e. don't put the newer 1.0.3 in the same directory of the older 1.0.3, overwriting the old one.
You should extract the newer one in another empty directory and then just copy over the modules folder; don't copy anything else.

apup.exe will never restart a download unless the file doesn't have the same MD5 hash; otherwise it won't download it again.
On the other hand, apup.exe doesn't resume halfway stopped downloads either.
So if you're in the middle of downloading a patch file and then transmission stops halfway and then you quit, the next time you start apup.exe it will start the download of that file from scratch.

What apup.exe will "resume" is the download list; it will start downloading from what you don't already have.

Whatever it is, if what you meant by "first version" is the older 1.0.3, don't use it.

Edited by sh1leshk4, 14 December 2007 - 06:30 PM.

[Rudy]

@sh1leshk4 date='Dec 15 2007, 05:30 AM' post='1183'
@noorman

maybe my post was not clear

i agree with your comments, which was the same as mine, just different wording.

[sh1leshk4]

Rudy, I was replying straight to noorman, not you; hence the bolded @noorman. =)

[PsiMoon314]

Hi Guys,

Well the latest version of the APUP downloader seems to be getting worse for download issues than the earlier versions

At this stage I am running APUP.EXE 1.0.0.3 dated 03/12/07 and the download process is stalling all over the place.

If I am able to download 1 hotfix in the pending list then the next one will stall the download process completely

I have run APUP now about a dozen times and the same behaviour is been seen on each time it is run.

Why is the download process so fraught with issues and problems? The application is not crashing as such, just stalling and failing to continue further.

I have just finished running the latest build of the Ct' Offline-Updates package and this was able to download all of the updates and patches needed in no time at all. From this I conclude there is nothing wrong with my Internet connection or it's speed (around 8 Mbits download)

If you need any log files I have them but they don't show much in the way of useful information.

Is it time to scrap the priyan.tk download code and replace it with another solution?

Kind Regards

Simon

[Rudy]

@PsiMoon314

can't agree that its getting worse, from my side it looks like its becoming more stable - runtime errors has disappeared, scripts are much more stable

BIG NOTE - software is in BETA mode.

I occasionally have a stalled download - but it always continues without any problems. Currently the aim is to get all the download scripts stable, and then move over to enhancements and fixes.

[PsiMoon314]

Hi,

I am aware that this software is beta! :-)

However my observations are still the same, the downloads are continuing to stall, which was an issue I did not see on earlier builds.

I have had occasional Run Time errors, which do appear to have stopped, however a smooth download process seems to have stopped also.

What could be causing these issues?

Kind Regards

Simon

[sh1leshk4]

Unfriendly WinSock. Probably.

Is it time to replace with another solution?
What kind of solution?
Would you really know what's wrong with the current apup.exe if you could see the source code?

But if asked what is wrong, it's still a guessing game at best.

AFAIK, me and some other people (w/ the 1.0.3) have also experienced stalled downloads, but it's resumable until it really finished.
No more runtime errors unless a faulty script or two (*ahem* j/k) stumbling apup.exe.
Aside from the date display issue and not too informative status report whenever it finishes downloading something (which is just a UI problem; not exactly the end of the world), apup.exe is pretty much stable now.

There are stalled downloads, yes, but it's not like we can't resume it.
I don't know about others, but the last time I downloaded a full 3.4 Beta WinXP updates I stalled less than 10 times.
Might be a bit much for some but it always stalled when it finishes downloading a file, never in the middle of downloading a file.
Which is why I never bothered to report; it's already being reported by (many?) others anyway.

But there are always a few exceptions here and there.

Some still running into runtime errors, a weird behavior with the /log switch, etc.
Is this apup.exe at fault?
I have no idea, since I've never experienced those problems when using 1.0.3.

Keep in mind that the system conditions of every user in this forum (or any AP users) are different.

Different localization settings caused a bug in the date display in one system while on others that uses a different locale setting doesn't have that bug.
Different kinds of WinXP "compile" may also affect this; there is one user that report 1.0.3 works fine on a normal WinXP system of his while it spews a runtime error in his other system that uses TinyXP.

It is known that many of us install, repair, modify and uninstall each and every apps in our own system.
Who knows what system file that's seldom used but being removed because it supposedly "lacks usage" or "seems no longer needed" that's actually needed by apup.exe?

Well, Antonis maybe could tell us what files are supposed to be present (or installed) in a system to run apup.exe out-of-the-box.

That said, apup.exe is currently moving to a right direction.
Some may call it regressions but hey, you can always move on to another solution that some of us probably have pointed before. =)

Me?
I stick to what I already comfortable with.

Edited by sh1leshk4, 17 December 2007 - 03:39 AM.

[Cyrus]

sh1leshk4, you said that the Xp 3.4 list stalled 10 times during a download. I downloaded the entire list with only 1 restart of apup. Do you have a slow DSL connection or a slow computer? also, are you on a wireless network?

[sh1leshk4]

Less than 10 times, and it didn't bother me at all; as long as the downloads are complete it's fine for me.

Slow DSL connection...well, it's a 512kbps connection so it's not that slow; it tops at 44~46KB/s when downloading the patches.

Slow PC...now that's an abstract question nowadays.
It's an A64 3500+ (Venice) with 1GB (single stick; single channel of course) PC3200 DDR DRAM.
Well, of course it's slow compared to dual core systems but I don't think it's that old.

And, yeah, I'm on a wireless network.
But keep in mind that my downloads stalled whenever it finishes downloading a file (it stalled when it tries to start downloading the next file) but never in the middle of a file download.
So network problem is probably out of the question.