Is "print sequence" enabled in RH7 Packager for AIR?

I can't get "print sequence" to enable. I'm also unsure of what exactly the "sequence" is that would be printed. Any topic I navigate to is the "end" of a browse sequence. The previous elements in the browse sequence are always folders in the table of contents. I don't understand what, other than the end topic, is ever printed.

Hi again
You define a Browse Sequence in RoboHelp by clicking Tools > Browse Sequence Editor. You then choose the topics that are part of each sequence you define.
Breadcrumbs are based on the path to each topic based on the Table of Contents. They are actually calculated by RoboHelp at the time you generate your output.
Cheers... Rick
Helpful and Handy Links
RoboHelp Wish Form/Bug Reporting Form
Begin learning RoboHelp HTML 7 or 8 within the day - $24.95!
Adobe Certified RoboHelp HTML Training
SorcerStone Blog
RoboHelp eBooks

Similar Messages

Here is how to enable full screen mode for AIR Mac Desktop Apps

I just discovered that with a very simple native extension method, I can enable full screen mode for AIR Mac Desktop Applications.
This gets you the full screen icon in the top right, and it works perfectly with no changes to my code. (Obviously only works on Lion and above, since this is a Lion feature)
Enjoy.
Here's the code:
    FREObject _EnableFullScreenMode(FREContext ctx, void* functionData, uint32_t argc, FREObject argv[])
        //We should be okay to do this, even on 10.6, according to this post:
        //http://www.cocoabuilder.com/archive/cocoa/311124-implementing-full-screen-for-10-7-but-app-should-also-run-on-10-6.html
        //We can't use [NSApp mainWindow] - didn't appear to work
        //This seems to though:
        NSArray * allWindows = [NSApp windows];
        if (allWindows.count > 0)
            NSWindow *mainWindow = [allWindows objectAtIndex: 0];
            NSWindowCollectionBehavior behavior = [mainWindow collectionBehavior];
            behavior |= NSWindowCollectionBehaviorFullScreenPrimary;
            [mainWindow setCollectionBehavior:behavior];
        //TODO: Return a boolean instead depending on if we found the main window
        return NULL;

Press Control + Command + F on your keyboard to enter or exit full screen mode.

BSoD Packager for AIR

I'm running v1 of TCS on a Dell Optiplex 755 w/4GB RAM. When
I run RoboHelp Packager for AIR on any output, repeat "any output,"
after I review the output and exit the packager, I get a BSoD. This
is dependable and replicable...10 times so far today trying to
diagnose it. Test has rulled out a RAM issue. Any advise?

I may have found the issue:
When I spin an AIR application from WebHelp output and
preview the AIR application, or
when I Preview an application from the AIR Packager Generate
dialog,
if I Cancel the dialog before I close the AIR application,
the OS will BSoD every time;
if I Cancel the Generate dialog without first closing the AIR
application, the AIR Packager exits and returns control to me
without error, every time.
This sounds like a memory management bug of a garbage
collection bug.
When I close the fresh AIR application before I exit the AIR
Packager, apparently the AIR Packager attempts to clear memory,
finds that <some address> is already clear, and barfs with
"PAGE_FAULT_IN_NONPAGED_AREA" every time.

Packager for AIR

I used the RoboHelp Packager for AIR on a WebHelp file
created RoboHelp 7. The WebHelp file works fine. However, when I
open the AIR version, many of the individual help topics do not
display. All of the TOC entries are present. And, all the files
display correctly when I use the Preview function.
Does anyone know where I can look to fix this?
Thanks

Hi Peter and thanks for reply. I know that there is an
article on my site about AIR help. It's useful and explanatory but
i din't find any useful tip regarding the issue. Any other idea?.
Thanks.

Robohelp Packager for Air

I downloaded robohelp_airpkgr.exe (actually, uninstalled,
downloaded and reinstalled) and clicked on it to install
WebHelpPackager.exe and all the related files. OS is Windows XP
Media Center. When I run Packager, the Help will not operate. When
I click on PackagerHelp.air I get a message in Application Install
that the air file is damaged. How can I correct this or how can I
get a clean Air help file? Air forum suggests that I post here.
Don

Please click on the link below to access the Packager help in
PDF format.
https://share.acrobat.com/adc/document.do?docid=7adfccf6-7e8f-42d4-a137-79042d94a161

Business Package for Colloboration Projects

hi, experts
I would like to know about the deployment about PPDMC (Projects, Portfolio Management and Design Collaboration). I need to deploy the PPMDC to EP 7.0.
As follows the xRPM installation guide, I need to install the CPRXRPM_UI. Is it right?
Actually, I can not find the the installation guide of PPMDC for cProjects. I got the installation guide for xRPM.
If we do not need to follow the xRPM installation guide, can I upload the PPMDC without CPRXRPM_UI using JSPM?
Please, let me know how to figure it out.
Thank you for your concern.
from beginner (Alex)
<b>reference</b> as belows, from the BP for PPMDC40SP6
The Business Package for Projects, Portfolio Management and Design Collaboration
(PPMDC) 4.0 enables you to combine strategic portfolio management with operational project
management by offering access to SAP cProject Suite (cProjects and cFolders) and SAP
xApp Resource and Portfolio Management (xRPM) via SAP Enterprise Portal.
For information about the configuration process to enable the Business Package for Projects,
Portfolio Management, and Design Collaboration (PPMDC) 4.0 to run in the SAP Enterprise
Portal, see the SAP xRPM 4.0 Java Component Installation Guide on SAP Service
Marketplace at http://service.sap.com/instguides → SAP xApps → SAP xApp
Resource and Portfolio Management → SAP xRPM 4.0.

Hi Santosh
You can view the entire list of Business Packages on SDN itself. Just browse to the Developer Areas -> Enterprise Portal -> Portal Content Portfolio. On the Quick Links area, click on List of Packages. You will then be able to see the list. Check if what you are looking for is available there.
Hope that helped.
Best Regards
Priya

RoboHelp Packager for Adobe AIR is GM

RoboHelp Packager for Adobe AIR is GM now and you can
download it now for FREE from Adobe site –
http://www.adobe.com/products/robohelp/robohelp-packager-for-air
Adobe AIR runtime enables applications to deliver both the
benefits of server connectivity and the compelling end user
experience of a desktop application. With a seamless offline-
online experience, end-users of Adobe AIR applications can continue
to work when they are temporarily offline. RoboHelp Packager for
Adobe AIR now enables you to publish in Adobe AIR format. Neither
of the popular help output options - CHM or WebHelp or WebHelp on a
Server provide the array of features as RoboHelp Packager for Adobe
AIR does today. That said, in my opinion, RoboHelp Packager for
Adobe AIR is a beginning, beginning of a new revolution in help
authoring. Here is a list of what you get today
· Auto Update - Adobe AIR applications that can update
themselves when online connection is available and that can work
perfectly when desktop is offline. For example, Adobe AIR help file
created with RoboHelp Packager for Adobe AIR will prompt the
end-users when an update is available. With a single click, the
help file will update itself.
· Get Web 2.0 features - Adobe AIR applications can
store information locally – for example, when you add
comments to Online Help, they are stored locally and can be viewed
after you have closed the application. End users can also comment
on external pages and store the comments as part of help file.
Comments are still available when Online Help has been updated
(provided file names don’t change) or when you are offline.
· Extensibility - Unlike HTML Help which depends on the
CHM viewer, the functionality of the Adobe AIR is extensible and
customizable. For example, organizations can add branding
information to Adobe AIR help file, including icons for help file,
branding imagery on the top of the help file and so on.
· Multiple tab – never before end user experience
- Adobe AIR help file also allows you to open multiple tabs within
the tri-pane enabling multiple help topics and threads to be
navigated at the same time.
· Integrated interface to everything your end users need
- You can also add resource links to your help files –
enabling a single access point for product pages, user forums,
knowledge base, online help and external web pages.
· Multiple templates to choose from - Organizations get
to chose from several of the templates and can select a particular
skin or theme for each of these templates. With RoboHelp Packager
for Adobe AIR, there are three templates come out of the box -
Multi-Tab Accordion, Unipane and Classic Help.
· End user preferences - RoboHelp Packager for Adobe AIR
enables the help users to customize their help by selecting their
preferences (something they can’t do for a CHM or for WebHelp
output – which is not hosted on a Server).
· Cross Platform - Adobe AIR is cross-platform and
cross-browser, supported on Windows, Mac and Linux (currently in
pre-release).
Needless to say, Adobe AIR has attracted a lot of interest
among the help community and some of the experts believe that
within two years, Adobe AIR will be the preferred help format for
40% of all help authors.
If you have not tried it, you can download it now from
http://www.adobe.com/products/robohelp/robohelp-packager-for-air
Thanks and regards
Vivek Jain
Group Product Manager, Adobe Systems
Adobe Technical Communication Suite, FrameMaker and RoboHelp
www.adobe.com/products/technicalcommunicationsuite/
blog-
http://blogs.adobe.com/techcomm/

When you are comparing this to Flash, does this comparison
extend to the requirement for each end user to install the Air
runtime on their PCs before they can access our RoboHelp system?
And that they will also get reminders to update to the latest
version of Air runtime?

RoboHelp 8 for AIR - Comment Feature

I'm currently using RH7. I noticed in the marketing blitz for
RH8 it mentions that the RH packager for AIR allows user comments
to be posted within your help project. I'm trying to understand if
this means:
a. User makes comment on their C drive for their own personal
reference
b. User posts comment to a web server for all to see (and
help author to moderate)

While Peter's feverishly going back through his hand-written
notes (he keeps them on wax tablets), let me jump in here.
Comments stay with the AIR file wherever it is located.
Comments are identified by machine username, whether the AIR
file is on your local machine or on a server.
1. I copied an AIR file to a server location.
2. I made a comment which, when added, displayed my username.
3. I copied the AIR file back to my machine.
4. The new comment appeared.
In addition, you can sync comments from multiple local
machines, by exporting/importing comment file (
Send and Receive comments > Send to file/Receive from
file). For testing, I: 1) exported two comments; 2) edited the
file by changing <authorname> and <comment> values; and
3) imported the edited comments, which appeared along with my old
ones (but identified by the different author name).
Based on my initial observations, then, you could even share
comment files between your customers and your organization (after
moderating the entries, if need be).
How your customers use the help (shared or loaded on users'
local machines) will determine how you instruct them to use the
comments feature, as well as how to possibly interact with you, the
vendor.
Good luck,
Leon

Installation Directory for AIR

Is there a setting in the RoboHelp Packager for AIR that can control where the .exe file is placed upon installation? My AIR help always installs in the C:Program Files directory. I would like it to install in C:\Program Files\Hyland (a submenu off the existing Program Files).

Your help will automatically be put into a folder with the name of the help file. In the Program Menu Folder field you can specify a sub-folder name such as Hyland and then you help would be something like C:\Program Files\Hyland\Help A. Without specifying that it would be C:\Program Files\Help A.
http://www.grainge.org/pages/authoring/air/7/air_rh7.htm shows the screen in the RH7 Air Packager. It's a different layout in RH8 but the field will be the same.
See www.grainge.org for RoboHelp and Authoring tips

Package for print

Hi all,
I'm creating a javascript that makes a package for print in Indesign CS5. All goes well, the package gets created, but afterwards the fonts in the package seems to be in use until I quit Indesign. Has anyone had this problem, or can anyone help me with this.
Thanks a million.
Best regards,
Jan.
var doc = app.activeDocument;
var ThePackagePath = Folder("~/Desktop/input/test");
doc.packageForPrint(ThePackagePath, true, false, false, false, false, false,false,"",false);

Hi Harbs,
The problem is that we can't process the package in our workflow because
the fonts in the package are still in use by Indesign on the client
machine.
Jan.

Help! 'Package for Print' Script

Hi all,
I have a specific 'Package For Print' script, that needs a small modification, and and I was hoping someone could help me.
Essentially, I need to OMIT 'Include PDF' option when packaging, since this makes things a bit wonky on my script (see below).
Let me know if you need to see the script, and I'll post it.
Thank you.

Here you go, and thank you. I know notes are also included in it. Sorry about this.
//Package the active document and setup the dockets folder structure.
//The active document shouldn't have been saved (has no name), so provide a name
//taken from the first and only link. After creating the dockets folder structure,
//close and delete the original file and open the file in the docket's originals
//folder.
#target InDesign
//Constants
const PROOF_PREFIX = 'Proof_';
const OUTPUT_SUFFIX = ' Folder';
const ORIGINALS_FOLDER = 'Originals';
const PRINT_FOLDER = 'Print';
const DIGITAL_PROOF_FOLDER = 'Digital Proof';
const CLIENT_FOLDER = 'Client Provided Files';
const DEFAULT_MAC_DOCKETS = '/Users/parham/Desktop';
const PDF_PROFILE = 'Linx_Proof'
function Err() {}
//Use a more user-friendly version than throwing an error.
Err.FatalError = function (msg) {
alert(msg, 'Fatal Error', true);
exit();
function makeShowUI(runtime) {
var doc = runtime.doc;
var window = (function () {
var windowDef = "Window {\
type: 'dialog', \
properties: { \
resizeable: false, \
closeButton: true, \
maximizeButton: false, \
minimizeButton: false \
text: 'Dockets Package', \
orientation: 'column', \
var w = new Window(windowDef);
//Folder name
w.add("StaticText { text:'New Folder Name', alignment: 'left' }");
var defaultName = doc.name;
if (defaultName.slice(-5) == '.indd') {
var origlength = defaultName.length;
defaultName = defaultName.substr(0, origlength - 5);
w.folderText = w.add("EditText { alignment: 'left', characters: 30, justify: 'left', " +
"text:'" + defaultName + OUTPUT_SUFFIX + "'}");
//Destination dir
w.add("StaticText { text:'Save To', alignment: 'left' }");
var dirGroup = w.add("Group { orientation: 'row', alignment: 'fill' }");
w.dirText = dirGroup.add("EditText { characters: 30, justify: 'left', " +
"text:'" + DEFAULT_MAC_DOCKETS + "'}");
w.dirBrowseBtn = dirGroup.add("Button { text: 'Browse...' }");
w.dirBrowseBtn.textBox = w.dirText;
//Package Options
w.options = w.add("Panel { orientation: 'column', alignment: 'fill', \
text: 'Package Options', alignChildren: 'left'}");
w.options.fonts = w.options.add("Checkbox { text: 'Copy Fonts' }");
w.options.links = w.options.add("Checkbox { text: 'Copy Linked Graphics' }");
w.options.profiles = w.options.add("Checkbox { text: 'Copy Color Profiles' }");
w.options.update = w.options.add("Checkbox { text: 'Update Graphic Links In Package' }");
w.options.hiddenContent = w.options.add("Checkbox { text: 'Include Fonts and Links From Hidden and Non-Printing Content' }");
w.options.ignore = w.options.add("Checkbox { text: 'Ignore Preflight Errors' }");
w.options.report = w.options.add("Checkbox { text: 'Create Report' }");
w.options.fonts.value = true;
w.options.links.value = true;
w.options.profiles.value = true;
w.options.update.value = true;
w.options.hiddenContent.value = true;
w.options.ignore.value = true; //Parham's request for true
w.options.report.value = false; //Saeed's request for false (no instructions)
//Digital Proof
w.proof = w.add("Panel { orientation: 'column', alignment: 'fill', \
text: 'Digital Proof', alignChildren: 'left'}");
w.proof.make = w.proof.add("Checkbox { text: 'Make PDF Proof' }");
w.proof.viewAfter = w.proof.add("Checkbox { text: 'View PDF' }");
w.proof.make.value = false;
w.proof.viewAfter.value = false;
//OK / Cancel
var buttonDef = "Group { orientation: 'row', alignment: 'right', alignChildren: 'right' }";
w.bg = w.add(buttonDef);
var okDef = "Button { text: 'OK', alignment: 'right' }";
var cancelDef = "Button { text: 'Cancel', alignment: ['right', 'center'] }";
w.okBtn = w.bg.add(okDef);
w.cancelBtn = w.bg.add(cancelDef);
return w;
runtime.window = window;
window.dirBrowseBtn.onClick = (function () {
var result = Folder.selectDialog('Choose destination directory');
if (null !== result) {
//Replace string with selected path
this.textBox.text = result.fullName;
return window.show();
function deleteFolder(folder) {
if (!folder.exists) {
return;
var children = folder.getFiles();
for (var i = 0, im = children.length; i < im; i++) {
if (children[i] instanceof Folder) {
deleteFolder(children[i]);
} else {
children[i].remove();
folder.remove();
//Main path
try {
var a = app.activeDocument;
} catch (e) {
Err.FatalError("No document open");
var runtime = {};
var doc = app.activeDocument;
runtime.doc = doc;
if (doc.saved) {
//Document has already been saved (already has a name), so stop.
Err.FatalError("Document has already been saved");
//Ensure at least one link, since multipaged PDFs end up as more than 1 link.
if (doc.links.length < 1) {
Err.FatalError("Document has " + doc.links.length + " links.");
//Save the existing file in a temporary place, same dir as first link.
//Take the name from the first link
var link = doc.links.firstItem();
var defaultName = link.name;
if (defaultName.slice(-4) == '.pdf') {
var origlength = defaultName.length;
defaultName = defaultName.substr(0, origlength - 4);
} else {
//Placed item is not a pdf, as per Parham's request, don't warn about it.
//Just take the filename best guess and go with it.
// if (confirm('Linked item is not a PDF. Package anyways?',
// true, 'Package non-PDF')) {
//break on the last '.'
var lastIndex = defaultName.lastIndexOf('.');
if (lastIndex > -1) {
defaultName = defaultName.substr(0, lastIndex);
} else {
defaultName = defaultName;
// } else {
// alert('Did not package.');
// exit();
//filePath should be a File, but is actually a string, so make a file.
var linkFile = new File(link.filePath);
var origFile = new File(linkFile.path + '/' + defaultName + '.indd');
if (origFile.exists) {
//Folder already exists, get user to confirm
if (confirm("File " + defaultName + '.indd already exists. Replace?',
true, 'Replace File')) {
//Erase the temp file
origFile.remove();
} else {
alert('Did not overwrite existing files, did not package.');
exit();
doc.save(origFile);
if (2 == makeShowUI(runtime)) {
//User pressed cancel
exit();
//Main code, do the packaging and make the directories.
//But first check for existing folder.
var folderName = runtime.window.folderText.text;
var destinationPath = runtime.window.dirText.text;
if (destinationPath.slice(-1) == '/') {
var newFolderPath = destinationPath + folderName;
} else {
var newFolderPath = destinationPath + '/' + folderName;
var outputRoot = new Folder(newFolderPath);
if (outputRoot instanceof Folder && outputRoot.exists) {
//Folder already exists, get user to confirm
if (confirm('Dockets folder ' + folderName + ' already exists. Replace?',
true, 'Replace Folder')) {
//Erase the destination directory
//Get all contained files + folders, then delete them.
deleteFolder(outputRoot);
} else {
alert('Did not overwrite existing files.');
exit();
} else if (outputRoot instanceof File) {
//Destination folder exists as a file, fail.
Err.FatalError('File named ' + folderName + ' already exists, cannot make folder.');
//Destination doesn't exist, create it.
if (!outputRoot.create()) {
Err.FatalError('Error creating folder ' + folderName);
//We have an empty directory, now do the packaging and everything else.
var printFolder = new Folder(newFolderPath);
printFolder.changePath(PRINT_FOLDER);
if (!printFolder.create()) {
Err.FatalError('Error creating Print folder.');
var digitalProofFolder = new Folder(newFolderPath);
digitalProofFolder.changePath(DIGITAL_PROOF_FOLDER);
if (!digitalProofFolder.create()) {
Err.FatalError('Error creating Digital Proof folder.');
var clientFolder = new Folder(newFolderPath);
clientFolder.changePath(CLIENT_FOLDER);
if (!clientFolder.create()) {
Err.FatalError('Error creating Client folder.');
var originalsFolder = new Folder(newFolderPath);
originalsFolder.changePath(ORIGINALS_FOLDER);
if (!originalsFolder.create()) {
Err.FatalError('Error creating Originals folder.');
//Do the package
var f = runtime.window.options;
if (doc.packageForPrint(originalsFolder, f.fonts.value, f.links.value, f.profiles.value, f.update.value, f.hiddenContent.value, f.ignore.value, f.report.value, false, true)) {
} else {
Err.FatalError('Failed to package.');
//Do the PDF proof
if (runtime.window.proof.make.value) {
var proofname = PROOF_PREFIX + doc.name;
if (proofname.slice(-5) == '.indd') {
var origlength = proofname.length;
proofname = proofname.substr(0, origlength - 5);
proofname = proofname + '.pdf';
var proofFile = new File(digitalProofFolder.fullName + '/' + proofname);
if (proofFile.exists) {
Err.FatalError('Digital proof already exists.');
} else {
var exportProfile = app.pdfExportPresets.itemByName(PDF_PROFILE);
//We get an object even if the profile doesn't exist, have to check isValid
if (!exportProfile.isValid) {
Err.FatalError('PDF profile ' + PDF_PROFILE + " doesn't exist, digital proof not created.");
//Explicitly set to export all pages.
app.pdfExportPreferences.pageRange = PageRange.ALL_PAGES;
//Set view preference
app.pdfExportPreferences.viewPDF = runtime.window.proof.viewAfter.value;
doc.exportFile(ExportFormat.PDF_TYPE, proofFile, false, exportProfile);
//Open the Originals folder .indd, close the current file and delete it.
var newFile = new File(originalsFolder.fullName + '/' + doc.name);
if (!app.open(newFile)) {
Err.FatalError("Failed to open packaged .indd");
doc.close();
origFile.remove();

AUR package for konica minolta laser printer (CUPS)

Hi there,
currently I'm writing a AUR package for the Konica Minolta Magicolor 5430 Desklaser.
I have a question to put the ICC profiles files and special KM files to the cups tree.
The Konica Minolta makefile put the binary "rstertokm5430" to the directory "/usr/lib/cups/filter/" which is completely correct but the *.ppd file and *.icm files are going by default to /usr/share/KONICA_MINOLTA/mc5430DL/Profiles (icm files) and to
/usr/share/cups/model/KONICA_MINOLTA/km5430dl.ppd.gz (ppd file)
The directory in my running archlinux is
usrsharecupsmodel*.ppd and
usrsharecupsprofiles*.icm
Additionally there are "Halftones" files (*.bmp)
usrshareKONICA_MINOLTAmc5430DLHalftones*.bmp
I think about to put the Konica Minolta files in to this (new) directory tree:
usrsharecupskm5430dlmodel*.ppd
usrsharecupskm5430dlprofiles*.icm
usrsharecupskm5430dlhalftones*.bmp
How do I have to copy these files to be archlinux compliant ?
best regards,
Frank

frigg, my apologies for overlooking an important point in my last post. The three magicolor drivers have different version numbers, unlike the other examples of multiple printer drivers in one PKGBUILD. This means you will need one PKGBUILD for each driver, in order to have the correct Arch version number. There is still value in doing them together, since they have many common elements.
As a consequence of this change, I think it might be best to put the single PPD file in /usr/share/cups/model/, rather than have a directory with one ppd file in it. It appears that the KM_PPDDIR variable in the configure script controls this location, so I have added a sed command to the build script accordingly.
As another consequence, the package names need to be changed. I would suggest cups-mc2430dl, etc. This uses the short internal names used by the drivers, and Arch package names are supposed to be lower-case. This means that your awk script no longer works for all three drivers. Rather than write three different awk scripts, I have ported your directory change to a sed command. When you package a stand-alone script with the PKGBUILD, you have to also maintain its md5sum, so it is simpler to do everything inside the build script if you can.
Following are the three incomplete PKGBUILD scripts incorporating these changes. They are complete enough that when you run makepkg, they will download the tarball (if it isn't already present), check its md5sum, copy it into the src directory, uncompress it, and modify the configure script. One way for you to proceed from here is to add lines to the build script, run makepkg, check that the right things happen in the src directory, and then that the correct things are put into the correct place in the pkg directory. The next line in the build script runs configure, which won't finish on my system due to the lack of libjbig.
# Contributor: Frank Ickstadt (frank dot ickstadt at gmail dot com)
# For Konica Minolta magicolor 2430 Desklaser
pkgname=cups-mc2430dl
pkgver=1.6.0
pkgrel=1
pkgdesc="CUPS driver for Konica Minolta magicolor 2430 Desklaser printer"
url="http://konicaminolta.com/"
license="GPL"
depends=('cups' 'gcc')
source=(http://www.linuxprinting.org/download/printing/konicaminolta/magicolor2430DL-$pkgver.tar.gz)
md5sums=('a97b4ee5c949ca791764457ead3a5b9c')
build() {
cd $startdir/src/magicolor2430DL-$pkgver
sed -i '/KM_PPDDIR/s//KONICA_MINOLTA//' ./configure
sed -i "/KM_DATADIR/s/KONICA_MINOLTA/$pkgname/" ./configure
#./configure --prefix=/usr
#make || return 1
#make prefix=$startdir/pkg/usr install
# Contributor: Frank Ickstadt (frank dot ickstadt at gmail dot com)
# For Konica Minolta magicolor 5430 Desklaser
pkgname=cups-mc5430dl
pkgver=1.8.0
pkgrel=1
pkgdesc="CUPS driver for Konica Minolta magicolor 5430 Desklaser printer"
url="http://konicaminolta.com/"
license="GPL"
depends=('cups' 'gcc')
source=(http://www.linuxprinting.org/download/printing/konicaminolta/magicolor5430DL-$pkgver.tar.gz)
md5sums=('1460477f2dd195c301e961a6cbfe1f54')
build() {
cd $startdir/src/magicolor5430DL-$pkgver
sed -i '/KM_PPDDIR/s//KONICA_MINOLTA//' ./configure
sed -i "/KM_DATADIR/s/KONICA_MINOLTA/$pkgname/" ./configure
#./configure --prefix=/usr
#make || return 1
#make prefix=$startdir/pkg/usr install
# Contributor: Frank Ickstadt (frank dot ickstadt at gmail dot com)
# For Konica Minolta magicolor 5440 Desklaser
pkgname=cups-mc5440dl
pkgver=1.2.0
pkgrel=1
pkgdesc="CUPS driver for Konica Minolta magicolor 5440 Desklaser printer"
url="http://konicaminolta.com/"
license="GPL"
depends=('cups' 'gcc')
source=(http://www.linuxprinting.org/download/printing/konicaminolta/magicolor5440DL-$pkgver.tar.gz)
md5sums=('abd54f32517ebeb7a56f902b159c7dea')
build() {
cd $startdir/src/cups-mc5440DL-$pkgver
sed -i '/KM_PPDDIR/s//KONICA_MINOLTA//' ./configure
sed -i "/KM_DATADIR/s/KONICA_MINOLTA/$pkgname/" ./configure
#./configure --prefix=/usr
#make || return 1
#make prefix=$startdir/pkg/usr install

RDP users with Printer redirection enabled, cause Terminal Server 2008R2 to hang for about 10 seconds

We have several 2008R2 Terminal Servers with roughly 40 users working on each of them. Everytime a user logs on or off with printer redirection enabled in his RDP client (we use the Easy print feature), all other users experience a freeze of
10 seconds on that server. Needless to say, this behaviour of the server is not acceptable. We searched all of Google and implemented and tested every proposed solution, including the registry additions to the lanman part but all with no effect. Can anyone
provide us with a possible solution? It would be immensely appreciated!

Hi,
Thank you for your posting in Windows Server Forum.
Once user is successfully log on, can able to print the document easily?
Which version of client OS & RDP using for your environment?
Initially I would like you to try installing latest RDP 8.1 if you are using Windows 7 and if using Windows XP then please use RDP 7. In addition check .Net Framework 3.5 or higher installed. Apart as Bruno suggested, please check the latest driver installed
on RDS server. Also check the Event log for any information. For more detail, refer below article.
Using Remote Desktop Easy Print in Windows 7 and Windows Server 2008 R2
http://blogs.msdn.com/b/rds/archive/2009/09/28/using-remote-desktop-easy-print-in-windows-7-and-windows-server-2008-r2.aspx
Hope it helps!
Thanks,
Dharmesh

AIR Help - Why is Print Sequence Disabled?

Hi all,
I have experimented with a copy of a client's Help system in
both RH7 w/packager and the RH8 trial, generating output to the AIR
Help format. After generating & installing the .air package,
and viewing the new .exe help file, I notice the following: Click
the dropdown next to the Print icon and three options are listed
(Print this page, Print sequence, Print entire Help). No matter
what is selected below, Print sequence is always unavailable
(grayed out). This is the case when I generate with either version.
Am I missing something in the settings?
Thanks,
Katie
Katie Carver
Senior Technical Writer
Docs-to-You, LLC

Hi all
In addition to what my colleague and fellow Adobe Community
Expert Peter suggested, I read this thread and am inferring that
perhaps Katie doesn't fully understand how Browse Sequences work.
Particularly in WebHelp. So I see this could impact the operation
of things.
Please allow me to try and explain.
A Browse Sequence is merely a pre-defined path that traverses
two or more topics so that they are presented in a logical order.
You said that you created a Browse Sequence using the Auto-create
feature so I'm assuming you now have several different sequences.
This is because until you change the number of Book levels, you end
up with several sequences. If you wanted a single sequence that
spanned all of the TOC, you would need to auto-create the sequence
and specify 0 as the book levels.
That bit will hopefully help you sort the sequence creation.
Now let's address the sequence *USE*.
When you have created WebHelp output by clicking File >
Generate Primary Layout (assuming the primary is WebHelp) you see
four or five intermediate dialogs that allow you to specify
different parameters that govern how that layout is created.
Typically on the second dialog is an option for Browse Sequences.
So once you have created a sequence, you have to remember to enable
it in WebHelp in order to see it work. At this point, I'm thinking
you *MAY* have done this but it isn't clear. After all, if you have
never used them before, you may not have realized you needed to do
this step. You also may not realize how the sequence appears in
WebHelp.
So once you have defined the sequence and told WebHelp to
present it, you generate and the sequence is presented as two icons
in the "Navigation mini-toolbar". The little toolbar that sits
majestically perched at the top of the TOC, Index, Search, Glossary
and just below the main toolbar. So here's why you may think it's
not working in WebHelp. The behavior of the Previous and Next icons
will change depending on which topic you are viewing. If the topic
presented in the Topic pane is part of a sequence, one or both of
the buttons will be enabled. If the topic is the *FIRST* topic of a
sequence, the Next button will be enabled but Previous will not be.
This is because you cannot go further backward. The topic begins
the sequence. Assuming there are more than two topics in the
sequence, you click the Next button and the next topic in the
sequence is presented in the topic pane. This should then cause the
Previous button to enable and work when you click it. Once the last
topic in a sequence is presented, the Next button disables as you
cannot go further.
The bottom line here is that if you are displaying a topic
that is not part of a browse sequence, bot buttons will be disabled
and dead to the user.
Now shift focus to AIR Help. It seems reasonable to me that
if the AIR Help is presenting a topic that isn't part of the Browse
Sequence, just as WebHelp disables both the Previous and Next
buttons in the mini toolbar, AIR Help may disable the Print
Sequence feature.
Now that it's hopefully clear how this all works, please
ensure you are displaying a topic that is included in a Browse
Sequence and see if you now have an available option. I'm not
looking at AIR Help at the moment as I have no access to RoboHelp
8. So you might be seeing a bug or you might find it now works as
designed. Only you can say for certain.
Keep in mind that when you create AIR Help, I believe it has
to be installed after created in order to see it work. So just to
be on the safe side, after you ensure things are configured as
outlined, try generating to a different output file name, then
install and test that.
Whew... Rick

RoboHelp Packager for Adobe AIR - Beta 2 Announced

RoboHelp Packager for Adobe AIR is now updated. You can
download the new version for FREE from Adobe labs -
http://labs.adobe.com/technologies/robohelp/.
It has added a long list of novel features - first time for a HATT.
Now, besides multiple tabs, favorites, commenting and multiple
skins like Multi-Tab Accordion and Uni-pane Help, you have another
set of new features.
Designed for End Customers - Adobe AIR based Help templates
have been designed keeping in view the end customer. They have some
high-end navigation features like Mini TOC, Breadcrumbs, etc. Apart
from these capabilities, the new Adobe AIR based Help also empowers
the end customers to customize the Help. An end customer can set
their own preferences and customize Help as desired.
Compelling Rich Branded Experience- RoboHelp Packager for
Adobe AIR provides a compelling rich user experience. It includes
templates that help authors package the same content into three
completely different styles – Multi-Tab Accordion, Uni-Pane
or the Classic Tri-Pane Help. Apart from this it also helps the
Authors brand the Help as per Corporate Branding Guidelines. It
provides support for the addition of a Company Logo and a Punch
line in the main Help window. Apart from this it also provides an
About Box in the Help that details the version, description,
copyrights, logos etc.
Auto Update -Adobe AIR based Help applications provide an
Auto Update feature using which updates can be pushed to all
installed connected versions of Help. Usually, the Help content
bundled with the application is never updated, while the web
content is updated with current feature enhancements and additional
resources. Adobe AIR based Help provides you with the option to
publish updates for your end users at a common server location. The
Adobe AIR based Help is intelligent enough to check for updates and
prompts users to apply updates when it detects a new version is
available.
Review Workflows / Personalization of Help
Adobe AIR based help files can be configured in such a way
that you can add comments to topics and publish those comments at a
common location. This feature enables a complete review workflow,
whether or not the reviewer is a part of your group/organization.
* Reviewers within your network: Reviewers can publish their
comments to an XML file on a shared folder. They can also
synchronize the comments from other reviewers on the same network.
This enable multiple reviewers to simultaneously view the comments
being made by other reviewers as they review.
* Reviewers outside your network: You can send the .air file
to these reviewers who can then export their comments to an XML
file and send it to you. You can import these comments into your
Adobe AIR application.
Apart from the rewire workflow, the feature is designed to
help an end customer personalize Help by adding comments on the
same. These comments will not be uploaded to the server, however
can be exported to a file and shred with friends over email.
New Classic help Template - A new template called Classic
Help has been added. It is named Classic because it is a Tri-Pane
Help. Apart from that it has got all the power of any other Adobe
AIR based Help template. This template has a new feature called
“How do I” that lists all the browse sequences defined
in the WebHelp. We recommend that authors design their browse
sequences in such a way that they provide complete workflow
information to end customers.
Supports Packaging of Merged WebHelp- RoboHelp Packager for
Adobe AIR now supports merged WebHelp. If an author specifies the
WebHelp folder of a Master project, the Packager is intelligent
enough to detect and convert all referenced projects in the Master
Project. However, one needs to be careful while using this feature.
It doesn’t provide as much flexibility as Merged WebHelp. A
new Package needs to be created every time even when you update any
of the sub projects.
In Beta 2, zoom works flawlessly and search results has been
further improved.
If you have not tried the RoboHelp Packager for Adobe AIR,
you can download it now for FREE (Adobe RoboHelp 7 required).
Thanks and regards
Vivek Jain
Group Product Manager, Adobe Systems
Adobe Technical Communication Suite, FrameMaker and RoboHelp
www.adobe.com/products/technicalcommunicationsuite/
blog-
http://blogs.adobe.com/techcomm/
RoboHelp Packager for Adobe AIR-
http://labs.adobe.com/technologies/robohelp/

When you are comparing this to Flash, does this comparison
extend to the requirement for each end user to install the Air
runtime on their PCs before they can access our RoboHelp system?
And that they will also get reminders to update to the latest
version of Air runtime?

Is "print sequence" enabled in RH7 Packager for AIR?

Similar Messages

Maybe you are looking for