cab files fail to expand with autobuild

[Nukley]

When using autobuild, I get this error

expand: unknown option -- F Try 'expand --help' for more information. Cannot expand _umpdddi.lib_00315 from work\WDK\wxplibs_x86fre_cab001.cab. Cannot continue.

I would also like to mention that, every time the build fails, it adds a fake drive inside of my drives list, which stays there until a reboot.

[leecher1337]

subst drive can be removed with subst w: /D Quoting the docs:

if directory path length exceeds 30 characters, a virtual SUBST drive letter is created.
To avoid this step, use a build directory with a very short path name,
i.e. C:\NTVDMBLD

So I would recommend to make a build directory near the root level to avoid these problems i.e. C:\NTVDMBLD as suggested by the documentation.

[Nukley]

That fixed the drive issue, but it still is giving me the same problem with cab files

[Nukley]

Er, wait, let me clean out the build folder

[Nukley]

nope, same issue

[leecher1337]

Hm, I don't know an expand version that doesn't support the -F switch. My guess is that you have a program called "expand" in your search path that isn't the Microsoft cabinet expansion tool but some other tool by the same name. expand.exe normally resides in Windows\System32 folder. You can try to find the offending program with this command:

for %i in (expand.exe) do @echo. %~$PATH:i

Which output do you get?

[Nukley]

c:\devkitPro\msys2\usr\bin\expand.exe

[Nukley]

Seems to have compiled, but I got this error at least twice

[leecher1337]

May be a problem with your symbosl, check loader output with DebugView upon start of application.

[Nukley]

Like this?

[InterSyncz]

I haven't installed it yet btw, just compiled it, the error came up during compilation.

[leecher1337]

Ah, ok, during compilation, so running exe2bin is not your test case then, as I assumed.

This is a PATH issue then, the SDK ships with a WIN32 version of exe2bin, however, if exe2bin.exe is in your Windows\system32 path, it may get precedence. As the real exe2bin is a DOS program, it cannot run (until NTVDMx64 is installed). As exe2bin gets reinstalled with NTVDMx64 too, you can just delete it from your system32 directory and retry compilation.

[leecher1337]

No further update was given on the ticket, assuming ticket is solved by deleting exe2bin.exe in system32 directory.