This includes PlanetPress Design (database-driven sample data file), PlanetPress Workflow (Database input) and PlanetPress Capture (Capture Database). This limitation affects all parts of the Suite where database connectivity is possible. In order to create ODBC connections, you will need to access the 32-bit legacy version of the ODBC Connections application, located in C:\Windows\SysWOW64\odbcad32.exe. Since the "ODBC" icon in the control panel of your operating system is the 64-bit one, creating a connection here will not work for use in PlanetPress. PlanetPress cannot communicate with 64-bit ODBC drivers and connections. ODBC Databases (Design, Workflow, Capture) This can help resolve the error " The selected driver must be installed remotely from an x86 computer using Type 3 (User mode) drivers."Ĭlick here to download the PDF containing these instructions. This is useful when in an environment that mixes 32-bit and 64-bit computers, so that the 32-bit machines may install the driver directly from the server instead of manually. The following guide is used to add the 32-bit version of the Objectif Lune Printer driver directly into a 64-bit version of Windows Server 2008. Adding the 32-bit printer drivers to Windows Server 2008 64-bit On a 64-bit OS with more than 4GB of RAM, this will enhance performances. However, since some parts of PlanetPress are multithreading (Image and Workflow with self-replicating processes for example), each thread can use RAM up to this limit. Memory allocation and usageĪs PlanetPress Suite is still a 32-bit software, it is still limited to an effective maximum of 3.5GB of RAM. Note that technical support staff may require you to try your workflow/process/document on a 32-bit OS in the event where any trouble occurs on a 64-bit one. Though PlanetPress may work, we make no attempt at "repairing" these versions in the case where something does not. However, all parts within PlanetPress Suite remain 32-bit software which does have its limitations even while running in the 64 bit environment.įor older versions previous to 7.1.0, 64 bit operating systems are not supported. PlanetPress Suite is supported under 64bit OS since version 7.1.0. I'll update the links in post #1 to refer to those links - thanks for finding them.FAQ-1503: 64-Bit Support in PlanetPress Descriptionĭoes PlanetPress Suite support 64 bit operating system (圆4)? Contents ![]() The 64-bit version of 5.16.3 you reference at CNet is identical to the one I have, which came from ActiveState's site. I'm not going to post the binaries as this might violate some ActiveState terms. Reinstalling 5.16 works fine, so I'd say the only option currently is that version. Version 5.18 does not have certain required modules available, so that's a no-go. Given the unfriendliness here towards anything not JScript or VBScript, I'm not hopeful this will get investigated or resolved. The 32-bit version of ActivePerl 5.20 causes DirectoryOpus to emit to the log the diagnostic "Script Engine 'perlscript' could not be opened". The 64-bit version of ActivePerl 5.20 causes DirectoryOpus 11.12.04 to crash upon selecting a perlscript rename script. there is a download-location on the forum somewhere where you can store 'your'ĪctivePerl? But likely that requires okay from the administrator. ![]() Maybe you can verify the checksums? Alternatively, maybe. Now, I don't know which versions you have available at yours. for 圆4 one might try it from CNet - ActiveState ActivePerl Windows (64-bit)ĭ/ActiveState-Ac. ![]() I am not sure whether the below files are 'reworked' (meaning: added trojans, malware, pups whatever)īut. If that is the case, then the below can be ignored. ![]() So, the latest version of Dynamic Renamer is indeed compatible with v5.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |