.
Andrew Edge:Are you running ustation.exe with customized command-line arguments, or using another technique to run MicroStation in a non-standard manner?
You should not have to specify the workspace names in the print style, and it is better off that you don't. That's an advanced feature that is supposed to allow printing designs using a different workspace than the one loaded in the current MicroStation session. If the print definition workspaces are blank in Print Organizer, the designs will be printed using the current workspace, which is likely what you want.
If ustation.exe is not being invoked with any command-line arguments, then you may fall into one of the custom configuration situations where designs do not display correctly in read-only mode. Is this the case? You can test it easily enough by opening your design in read-only mode and seeing the symbology is correct. If that's the problem, then you can change the Print Organizer preferences to load the design files in read-write mode. The default is read-only.
Print Organizer does not currently support ustation.exe command-line workspace customization, although a priority build might be available that adds that capability via a configuration variable. Bentley Support can offer more information on that. Refer to CR 262657.
In the commercial release, you would need to remove the command-line options and launch ustation.exe normally (which is how Print Organizer launches its background MicroStation process). You could modify the standard mslocal.cfg to use your customized settings.
You can still run the Batch Print cmd, mdl load batchplt.
You can put Batch Print cmd in a key-in, or as a modification to "File" as a site/network task dgnlib pointed to by MS_GUIDGNLIBLIST.
Andrew, has there been any progress in fixing these issues,
We would like to move forward with V8i, but until these issues are resolved we will most likely have to shelf V8i.