Command line version

[Travis Bowen]

Is there a command line version of this tool? I saw the version 1.5 but after downloading it to my computer it does not run.

[-]

There's nothing more recent than version 1.5 I believe, unfortunately.

[Travis Bowen]

I thought so based on what I've read so far. Is there instructions or guidance on how to get that version up an running?

[Travis Bowen]

When I run the command line version, it opens and closed co quickly it's hard to see. I'm using windows server 2019. Is there something I need to do to get the command line version runnning? Thank youl.

[Travis Bowen]

I have the 1.5 version running now on a test machine. When I move it to something more robust, it crashes. So when I try to run it on a really large volume, it crashes. Is this possibly because this is a 32 bit version? Is there a way to make it work with 64 bit, if so? Sorry for the flurry of questions.

[-]

I remembered something: you can actually use other versions of the program (including 7.5.1) as a console program too. The only thing you need to do is to change the "Subsystem" bit in the .exe's "optional header" from 2 (Windows GUI) to 3 (Windows Console).

You can either do this in any of 3 ways:

• Via an app like CFF Explorer
• Via PowerShell:

$f = [System.IO.File]::Open('C:\SwiftSearch.exe', [System.IO.FileMode]::Open); $f.Position = 60; $x = 0 + $f.ReadByte(); $x += $f.ReadByte() * 0x100; $f.Position = $x + 0x5C; $f.WriteByte(0x3); $f.Close();

• Via Python:

python -I -c "import struct, sys; f = open(sys.argv[1], 'r+b'); f.seek(60); f.seek(struct.unpack('I', f.read(4))[0] + 0x5C); f.write(struct.pack('H', 0x3));" SwiftSearch.exe

You might want to rename it from .exe to .com after you do this.

Once you make this change, you should be able to run the program as follows:

SwiftSearch * "C:|D:" *
SwiftSearch * * *

Hopefully you won't see any crashes then.

[Travis Bowen]

Thank you. I'll give it a try!

[Travis Bowen]

So far this is working out really well. Still need to test on really big volumes. I'm able to export to .csv files from powershell using SwiftSearch. But the export does not include the Name and Type fields. Is there a way to get them to export? Thanks, this is a great tool.

[Anonymous]

Glad to hear! Unfortunately no there isn't. The Name column I didn't include because it's redundant and takes up extra space when the path is already there. The Type I didn't include because it would be far too slow if I included it. (It can easily take several minutes.)