PacsOne Server

I've ran the install.sh script and it does indeed install most of PacsOne.

The issue comes when it tries to run Setup.exe - it doesn't

Configuring PacsOne Server...
./install.sh: line 164: /Applications/PacsOne/Setup.exe: cannot execute binary file
PacsOne Server Installation Complete.

The PacsOne Installation Guide states that Setup.exe can run on the Mac OS X Platform. I understand .exe files are for Windows and DOS, and am confused as to how this installation would ever work on Mac OS X unless there was a requirement needed for installation that I'm missing.

Could someone please point me in the right direction.

Thank you very much,

Brandon

This looks like a file corruption problem, as the filename does not really matter (whether it's Setup.exe or even Setup.doc).

Can you run the following command to check if the Setup.exe is corrupted?
If the Setup.exe is valid, then the output of the above "otool -L" command should report no shared library which is "Not Found".

When I run those commands

# ls -l /Applications/PacsOne/Setup.exe
-rwxr-xr-x 1 crouseb admin 3991892 Apr 10 23:32 /Applications/PacsOne/Setup.exe


# otool -L /Applications/PacsOne/Setup.exe
/Applications/PacsOne/Setup.exe:
/usr/local/lib/libmysqlpp.1.dylib (compatibility version 2.0.0, current version 2.0.0)
/usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.3)
/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 368.28.0)
/System/Library/Frameworks/IOKit.framework/Versions/A/IOKit (compatibility version 1.0.0, current version 275.0.0)
/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 7.4.0)
/usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 1.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 88.3.6)

Looks like all the required shared libraries are present, so this seems like a security permission issue.

Try copying any binary executable program into /Applications/PacsOne/, and try to run it from there:
where dummy is any binary executable program.

More updates on this topic:

The errors turned out to be the results of the wrong processor type (PowerPC instead of x86), as the current MacOS X version of PacsOne Server only supports Intel/AMD x86-based processors and MacOS X version 10.4 or later.