AllDup does not work in WinPE

[alldupper]

AllDup is a great piece of software, thank you for creating and maintaining it!

My only issue is that I have been unable to make it work under WindowsPE environment. This is very sad, it is really best/safest using such a utility *offline*, running it under a separate OS, off a USB stick.

Doubtless, WindowsPE, depening on configuration, is usually a somewhat limited environment, still, there should be nothing preventing AllDup from working under it, really. I am happy to help with testing to make it work.

Last I tried WinPE_SE latest version, from 2019-02-03 - it is a Windows 7 PE x64 environment.

First I tried a more compact configuration without IE integrated. AllDup loads, all configuration ca be set, but it crashes the moment I start the actual search for duplicates. This is the error message thrown:

===========================================================
Now: 2018-06-05 22:17:43
App: AllDup 4.0.47
ExeInst: 2018-06-05 22:14:57
IniCreate: 2018-06-05 22:14:57
Modul: frmMain
Func: StartSearchForDups
Line: 660
Err: 339 - Component 'ieframe.dll' or one of its dependencies not correctly registered:
a file is missing or invalid
Path: R:\AllDup\AllDupPortable.exe
AppUp: 0:00:06
SysUp: 0:07:56
OS: Windows 7 Professional Edition SP1 (Build 7601) Version: 6.1 ID: 2
64bit: True
IE: 8.0.7601
PhysRAM: 14 445,36 MB Free / 16 203,18 MB Total
MemLoad: 10%
RAM used: 21,64 MB
Pagefile: 10 807,16 MB Free / 16 201,38 MB Total
VirtMem: 3 970,00 MB Free / 4 095,88 MB Total
CPU: Intel(R) Core(TM) i7-4700HQ CPU @ 2.40GHz
Screen: 1920x1080xTrueColor (4294967296)
Portable: True
User: SYSTEM
Comp: Win7PESE
Apptitle: AllDup 4.0.47 PE
Datapath: R:\AllDup
Admin: True
Errcount: 1
Lang: 9
Stop:0,0
SM:001100000
============================================================

This was back in the summer. Obviously, there is a dependency on ieframe.dll, and thus the crash without IE.

Now, it might well be possible for you to get around this IE-dependecy by changing the reference for Microsoft Internet Controls from the existing ieframe.dll to shdocvw.ocx. Would you mind, please, trying this?

[alldupper]

On 2nd try, I created a less compact WinPE_SE (still Win7 PE x64), with more features, with IE 8 integrated.

Unfortunately, I get a crash again, at the very same spot, right after starting the search for dups, but this time the error message is different:

=======================================================================
Now: 2019-02-19 12:53:10
App: AllDup 4.2.0
ExeInst: 2019-02-19 12:06:41
IniCreate: 2019-02-19 12:06:42
Modul: frmMain
Func: StartSearchForDups
Line: 660
Err: 7 - Out of memory
Path: Y:\Programs\AllDup\AllDupPortable.exe
AppUp: 0:00:17
SysUp: 0:33:15
OS: Windows 7 Professional Edition SP1 (Build 7601) Version: 6.1 ID: 2
64bit: True
IE: 8.0.7601
PhysRAM: 13 840,32 MB Free / 16 267,17 MB Total
MemLoad: 14%
RAM used: 23,77 MB
Pagefile: 10 501,13 MB Free / 16 265,37 MB Total
VirtMem: 3 947,80 MB Free / 4 095,88 MB Total
CPU: Intel(R) Core(TM) i7-4700HQ CPU @ 2.40GHz
Screen: 1920x1080xTrueColor (4294967296)
Portable: True
User: SYSTEM
Comp: 7PESE
Apptitle: AllDup 4.2 PE
Datapath: Y:\Programs\AllDup
Admin: True
Errcount: 1
Lang: 9
Stop:0,0
SM:001100000
======================================================================

Well, this is a weird one. AllDup used 24MB of RAM, when I had 14GB free, yet it is an out of memory error! Any idea what it might be?

Another difference I just noticed is that in the previous case AllDup was started from a RAM drive, while this time from the USB stick. I doubt it should much, if at all, I am just pointing it out.

[Administrator]

The error message "7 - Out of memory" is misleading. This has nothing to do with your RAM.
At line 660 AllDup show up the GUI of the search result and judging by your bugreport something at your WinPE-SE is still missing to work properly!

Now, it might well be possible for you to get around this IE-dependecy by changing the reference for Microsoft Internet Controls from the existing ieframe.dll to shdocvw.ocx.

AllDup uses the IE window to display different data. so there is a IE-dependecy. no other ocx/dll can change this.


Its a long trial and error task to find out what is missing if you create a SE of Windows.
First you should create a full Windows PE w/o excluding system components and you will see if this works or not.
After that you can start excluding components.

[alldupper]

Thanks a lot for the quick response.

Fortunately - but embarrassingly for me - this has since turned out to be a false alarm. AllDup works perfectly in my WinPe with IE8 integrated after all.

It seems that there was something in the configuration files that caused the crash initially. I had copied portable files to the USDB drive together with ini files, yet those had been created with an earlier version of AllDupPE.

I am very sorry for my dumb mistake.