Vault errors under Leopard

Greetings all,
With Aperture 1.5.6 & leopard installed now, trying to update a vault to an external Fat-32 drive results in errors. Sometimes the error message says that there were 9 errors, and it is showing the first 5, other times it says that there were 22 errors (not consistent, nor necessarily the same files?). Never had a single problem with this under Tiger, as recently as last week.
I verified rebuilt the startup disk permissions both before and after upgrading to Leopard; other aspects of Aperture seem fine.
I have not set up time machine.
Is there a fix I can do for this, or should I wait for an apple update? Thanks!

You'll have more success if you put the Vault on an HFS+ filesystem.
Some of the filename characters that Aperture uses don't get mapped very well onto FAT/FAT-32 by Mac OS X, and I've not seen anything that suggests its fixed in 10.5 (Leopard).

Similar Messages

Automator errors under Snow Leopard

Hi everyone,
Since upgrading my MacBook to Snow Leopard (I have the latest 10.6.3 update), Automator behaves very erratically. The window ‘AppleScript Error; The result of a numeric operation was too large. (-2702)’ pops up frequently at various stages of opening, using, or modifying my workflows previously created under Leopard.
I still get this erratic behavior even if I try to remake my workflows from scratch in Snow Leopard. Even stranger is that I can get a workflow to behave fine for a little while, and then it starts getting crazy again. Some Automator actions (Rename Finder item, Get Specified URLs, Run Applescript) seem to be especially prone to triggering the error.
This problem is general and very annoying, and I was thus surprised to find very few threads about this issue when I searched the Apple forums (assuming I searched correctly) or using Google.
Because of this issue, I have refrained from upgrading my Mac Pro to Snow Leopard, while waiting for future updates to hopefully fix the problem (which hasn’t happened so far).
Did anyone else encounter this problem, and if so, how do you solve it?
Any hint would be much appreciated.

I was loosing hope for a solution. But running Automator in 32-bit mode does work! Thank you Lupus42.
Now I can dare to install Snow Leopard on my Mac Pro. But because of this Automator error story, I’m still anxious about making the transition. So I’ll seek the safest way to try Snow Leopard. I know I can reinstall Leopard if Snow Leopard still causes me trouble, but I’d prefer not to mess with my current system at all. I’ve heard you can upgrade a disk image of your system instead, or create a new partition on your disk. I don’t know if these options are actually feasible and better, but I’d to explore these alternatives before altering my current system. Maybe I’ll start a new thread about this if needed.
Thanks everyone for sharing your similar problems (and showing me I wasn’t crazy) and your solution to the problem.

Problems with ViaVoice under Leopard, especially key mapping problems

ViaVoice's behavior has changed considerably under Leopard. First I will discuss the key mapping problem, since I'm eagerly looking for an answer to this problem. At the end of this post, I will voice some of the other problems I've experienced for those who may be interested. The key mapping problem may be specific to the fact that I use a foreign keyboard with a US version of ViaVoice.
INTRO:
I have used ViaVoice on my Mac for years, more or less without problems (ViaVoice's bugginess is notorious).
Those who know ViaVoice will know that one has two general options for dictation. One can dictate into ViaVoice's so-called SpeakPad, which allows special formatting, editing and dictation error correction within the dictated text, or one can dictate into "external" software such as Microsoft Word, in which case ViaVoice just sends a string of characters to that software. SpeakPad appears to make strong use of the operating system's built-in functionality for character formatting, document formatting, etc.
*MY PROBLEM*
I have a German keyboard on my PowerBook, yet dictate in US English. When I dictated into SpeakPad under Tiger, all characters appeared correctly. However, when I dictated into Microsoft Word using Tiger, I had to switch the keyboard mapping from German to US to get all characters (that means including the characters that are located at different positions on a German keyboard than they are on a US keyboard such as y, z, apostrophes and parentheses) to appear correctly.
Under Leopard, things have changed. Now it doesn't matter whether I dictate into SpeakPad or Word; the results are the same and many characters do not appear correctly.
If set to a German keyboard, y and z appear as expected. To name a few irregularities:
"(" appears as ")"
")" appears as "="
apostrophes appear as "#" and
";" appears as ","
If set to a US keyboard, y and z are interchanged. "(" and ")" appear as expected. Apostrophes appear as "\" and ";" appears as ","
By comparison, if typed (as opposed to dictated, as in the examples above) "correctly" (i.e. based on the letters printed on the keyboard) on a German keyboard set to imitate a US keyboard:
y and z are interchanged
apostrophes appear as "|"
"(" appears as "*"
")" appears as "(" and
";" appears as the symbol for "less than"
Since I don't have a US keyboard, I can't say how it would behave if set to imitate a German keyboard, i.e. if there's a correlation to the results I get when I dictate.
Since I was previously able to dictate correctly into SpeakPad by setting the keyboard to "German" and into Word by setting the keyboard to "US," I presume that this is a problem in Leopard, not ViaVoice.
*OTHER PROBLEMS WITH VIAVOICE UNDER LEOPARD*
In addition to the aforementioned key mapping problems (that may be specific to those of us with foreign keyboards), ViaVoice appears to have lost considerable functionality in Leopard. I cannot access SpeakPad's Preferences and the correction window. Moreover, the traffic-light like window buttons have disappeared from the VoiceCenter (although they work if you click where they should be). SetupAssistent appears to function.
I've written to Nuance about these problems, but have little hope that they will invest the time in producing a patch since they haven't released any updates since 2003.

Thrums1,
I've never had to "register" ViaVoice after updating the system. I thus suspect you haven't fully followed my above, three-step advice (particularly step 3).
1) Reinstall ViaVoice from CD.
2) Update to the latest version (using the patch downloadable from Nuance's website).
3) Replace the “temp” and “users” folders (in the "ViaVoice" folder at the upper level of your home directory) by a previous copy thereof. When I say previous copy, I mean a copy from when ViaVoice was still working properly, e.g. a copy from when it was running under Tiger.
As I said, I've gotten ViaVoice to survive several system updates by following the above steps. To my knowledge, the last step is critical since it saves you from having to reconfigure ViaVoice under the new operating system (in this case Leopard). I suspect that ViaVoice is crashing on your system because it's trying to start some module of the SetUpAssistant that is incompatible with Leopard (as many are). If you instead use old copies of the "temp" and "users" folders (from the previous system), then ViaVoice doesn't have to go through the initial "registration" process; ViaVoice doesn't need the SetUpAssistant; and all is (more or less) fine.
Good luck!
BTW, to my knowledge, Dictate only runs on Intel Macs. It thus won't run on a G4 iBook, just as it won't run on my PowerBook G4.

CUPS printing to remote server doesn't work under Leopard

So i have an ubuntu system running cups 1.2.8 as a print server. i have an epson stylus colour 760 plugged in and configured and working.
i also had a macmini running tiger printing to it fine via ipp. now it didn't occur to me that something as simple (and important) as printing would be severely broken under Leopard. basically, after the upgrade, i can't print at all to the remote cups server.
the symptoms are that the job queue will pause; even after clicking on 'resume', it will start the progress bar, and then after 100%, it will just pause again.
i have on the cups server (qbic)
EpsonPrinter
Description: Epson Stylus 760 Colour
Location: Small Bedroom
Make and Model: Epson Stylus Color 760 - CUPS+Gutenprint v5.0.0.99.1
Printer State: idle, accepting jobs, published.
Device URI: usb://EPSON/Stylus%20COLOR%20760
And on the macmini:
qbic
Description: qbic
Location:
Printer Driver: Epson Stylus Color 760 - Gutenprint v5.1.3
Printer State: stopped, accepting jobs, not published.
Device URI: ipp://192.168.1.244/ipp/EpsonPrinter
None of the following work
- used lpd://192.168.1.244/EpsonPrinter
- tried ipp://192.168.1.244/ipp/EpsonPrinter
- tried ipp://192.168.1.244/EpsonPrinter
The error messages from the macmini are:
I [01/Jan/2008:23:19:52 +0000] Printer "qbic" started by "ytl".
I [01/Jan/2008:23:19:52 +0000] [Job 25] Started filter /usr/libexec/cups/filter/cgpdftoraster (PID 791)
I [01/Jan/2008:23:19:52 +0000] [Job 25] Started filter /usr/libexec/cups/filter/rastertogutenprint.5.1 (PID 792)
I [01/Jan/2008:23:19:52 +0000] [Job 25] Started backend /usr/libexec/cups/backend/ipp (PID 794)
E [01/Jan/2008:23:20:02 +0000] [Job 25] Destination printer does not exist!
E [01/Jan/2008:23:20:02 +0000] PID 794 (/usr/libexec/cups/backend/ipp) stopped with status 4!
I [01/Jan/2008:23:20:02 +0000] Hint: Try setting the LogLevel to "debug" to find out more.
I [01/Jan/2008:23:20:02 +0000] [Job 25] Backend returned status 4 (stop printer)
I [01/Jan/2008:23:20:02 +0000] Saving printers.conf...
The job never appears on the cups server jobs list; however a tcpdump does show that there is communication:
x@qbic:~$ sudo tcpdump -i eth0 port 631
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
23:27:55.397616 IP 192.168.1.204.49599 > qbic.ipp: S 3571921204:3571921204(0) win 65535 <mss 1460,nop,wscale 3,nop,nop,timestamp 660419916 0,sackOK,eol>
23:28:05.490215 IP qbic.ipp > 192.168.1.204.49599: S 3610561258:3610561258(0) ack 3571921205 win 5792 <mss 1460,sackOK,timestamp 2498972 660419916,nop,wscale 2>
23:28:05.490269 IP 192.168.1.204.49599 > qbic.ipp: . ack 1 win 65535 <nop,nop,timestamp 660419916 2498972>
23:28:05.490285 IP 192.168.1.204.49599 > qbic.ipp: P 1:155(154) ack 1 win 65535 <nop,nop,timestamp 660419916 2498972>
23:28:05.490301 IP qbic.ipp > 192.168.1.204.49599: . ack 155 win 1716 <nop,nop,timestamp 2498972 660419916>
23:28:05.490315 IP 192.168.1.204.49599 > qbic.ipp: P 155:457(302) ack 1 win 65535 <nop,nop,timestamp 660419916 2498972>
23:28:05.490331 IP qbic.ipp > 192.168.1.204.49599: . ack 457 win 1984 <nop,nop,timestamp 2498972 660419916>
23:27:55.453575 IP qbic.ipp > 192.168.1.204.49599: P 1:26(25) ack 457 win 1984 <nop,nop,timestamp 2498978 660419916>
23:27:55.453705 IP 192.168.1.204.49599 > qbic.ipp: . ack 26 win 65535 <nop,nop,timestamp 660419917 2498978>
23:27:55.453804 IP qbic.ipp > 192.168.1.204.49599: P 26:225(199) ack 457 win 1984 <nop,nop,timestamp 2498978 660419917>
23:27:55.453861 IP qbic.ipp > 192.168.1.204.49599: P 225:354(129) ack 457 win 1984 <nop,nop,timestamp 2498978 660419917>
23:27:55.453919 IP 192.168.1.204.49599 > qbic.ipp: . ack 225 win 65535 <nop,nop,timestamp 660419917 2498978>
23:27:55.453959 IP 192.168.1.204.49599 > qbic.ipp: . ack 354 win 65535 <nop,nop,timestamp 660419917 2498978>
23:27:55.456571 IP 192.168.1.204.49599 > qbic.ipp: F 457:457(0) ack 354 win 65535 <nop,nop,timestamp 660419917 2498978>
23:27:55.456636 IP qbic.ipp > 192.168.1.204.49599: F 354:354(0) ack 458 win 1984 <nop,nop,timestamp 2498978 660419917>
23:27:55.669906 IP qbic.ipp > 192.168.1.204.49599: F 354:354(0) ack 458 win 1984 <nop,nop,timestamp 2498999 660419917>
23:27:55.670050 IP 192.168.1.204.49599 > qbic.ipp: . ack 355 win 65535 <nop,nop,timestamp 660419919 2498999>
23:28:08.470574 IP qbic.ipp > 192.168.1.255.ipp: UDP, length 183
Any help is appreciated!

The default setting under Tiger was CUPS, under Leopard it is Bonjour.
To access CUPS
http://localhost:631/printers/

IPhoto 7.1.1 Under Leopard 10.5.1 Will not print photo under "save as PDF"

iPhoto 7.1.1 Under Leopard 10.5.1.
Select a photo, choose "print" icon at bottom of iPhoto window.
Choose "print".
Choose "Save as PDF".
Result: Unknown error message appears with white space (no text) in message box, but with "OK" button.
Hit "OK button".
RESULT: iPhoto prints a screen shot of the iPhoto window and renders it to a PDF file.
In other words, *the print function under iPhoto does not work*. It yields an error every time that does not have a message, then *instead of printing the selected photo, takes a PDF screen shot of the iPhoto window*.
This is an example of poor programming. And of course, there is no way to fix it, or to get help.
Is anyone else having this problem?

This is an example of poor programming.
How do you come to this conclusion. It's working fine for me. You're the first to report such an issue.
First repair disk permissions with Disk Utility and delete the iPhoto preference file, com.apple.iPhoto.plist, that resides in your User/Library/Preferences folder. A corrupted pref file can cause all sorts of unusual performance problems. If that doesn't help, log into another account and try from there. If it still doesn't work a reinstall of iPhoto seems warranted. To reinstall iPhoto you'll have to delete the current application and all files with "iPhoto" in the file name that reside in the HD/Library/Receipts folder.
It iPhoto performs correctly in the other account then your primary account is the culprit and may be a preference file other than iPhoto's that's at fault. To determine if that's the case try the following;
Trouble Shooting Preferences
Go to HD/Users/Your_name/Library. Move the Preferences folder (in its entirety) to the Desktop and make a second copy of it so you have Copy A and B. Now try the the process again and determine if problem is fixed.
If the problem IS fixed, then go to the new Prefs folder that the OS will have created and open it up.
Open Copy B on the Desktop and select all of the items inside. Drag them into the open new library folder. When the Copy window comes up check the Apply to All check box and then click on the Don't Replace button as seen here. That will keep the new files created and bring back all of the others.
If the problem is NOT fixed, trash the new Prefs folder and move the intact Copy A folder back to the Library folder .
TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto database file and keep it current. If problems crop up where iPhoto suddenly can't see any photos or thinks there are no photos in the library, replacing the working Library6.iPhoto file with the backup will often get the library back. By keeping it current I mean backup after each import and/or any serious editing or work on books, slideshows, calendars, cards, etc. That insures that if a problem pops up and you do need to replace the database file, you'll retain all those efforts. It doesn't take long to make the backup and it's good insurance.
I've created an Automator workflow application (requires Tiger), iPhoto dB File Backup, that will copy the selected Library6.iPhoto file from your iPhoto Library folder to the Pictures folder, replacing any previous version of it. It's compatible with iPhoto 08 libraries and Leopard. iPhoto does not have to be closed to run the application, just idle. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.

Solution for File Vault Error.

I just got off the phone from Apple Tech support (Holding for 20 minutes on a 10th attempt) I could not get past the log-in screen. "File Vault error needs to be repaired". This is what Brandon from Apple told me to do.
1)Restart Computer holding down the "c" key.
2)Follow the onscreen instructions until you get to "Select Drive to install to"
3)Select your drive-click customize
4)Select the 2nd option, (install and do back of of files) and uncheck the box below the option...sorry I can't remember what the option is...Im in the middle of trying it now.
5)continue.
6)If you have already screened the install DVD, there is no reason to do this step again, it is ok to skip to install.
If this does not work you need to erase and install, however, you will need to do a file transfer to another mac computer via fire-wire by holding down the "T" key during start up prior to erasing the drive and installation of Leopard.

I would really love to try this, as I am having the same problem, but even after removing everything possible in the customization, I don't have enough disk space to do so. Probably because I used it all installing the operating system the FIRST time. I don't want to have to do an erase and re-install. I didn't back up nearly enough stuff last time because I was assured I wouldn't need to.
Now, it's after hours so I can't talk to apple and I am stuck with my husband's PC. Ew.

Update Vault Error

I can no longer update my Apertue 2.1.4 vault. Since installing Snow Leopard, I first noticed my iPhone would no longer sync pictures via Aperture 2, but would via iPhoto. Now I find I also cannot update vault to an external drive. Have redone permissions, rebuilt Aperture library, tried to create new vaults on the original external drive and the internal drive. Always get same "Update Vault Error" response and images don't appear to go into the vault. I see similar posts with no solution. My Aperture Library has 14000 photos.
I wonder if these problems will carry over to an Aperture 3 library.
Hoping for some advice

No, I thought of that, I tried to make it simple:-
Lacie/backup/Vault
Or on the internal:-
Users/me/pictures/vault
It may be that one of the images or possibly a sidecar file in my project is corrupt, thus making the library itself corrupt.
Therefore, when Aperture tries to compare its internal library structure to the Vault, it finds an error and blames the Vault for being corrupt; even so it still finds errors trying to backup to a blank brand new vault. I have a problem with the fact that it is suggestng that the vault be deleted(!) and replaced, even though the problem is likely to be with the internal Library itself and not the vault. And replacing the vault with a new one is impossible (still has same error).
Unfortunately I have no way of finding out which one of the 2500 or so images in the library has the problem. I thought that the commandoptionrestart Aperture to rebuild the library would have worked, but unfortunately it doesn't.
L

Apache "Forbidden" Error after Leopard Upgrade

Hopefully this is really simple.
I have just upgraded from Tiger to Leopard and as part of that process Apache 2.2 was installed where before I had Apache 1.3. Interesting the upgrade turned Web Sharing OFF - nice - however that was easily overcome in System Preferences.
However, I know next to nothing about Apache so cannot easily solve the next problem. Now whenever I try to access http://localhost/~Username Apache returns "Forbidden - You do not have permission".
It would be much appreciated if anyone could let me know where I need to put the 'tick-in-the-box' or amend some configuration setting. Thanks in advance.

I finally got my Leopard Apache configuration working with PHP5 and with MySQL. I also solved (finally) the forbidden errors I was seeing. Here are some of the changes I made.
1. My read permissions on my website files and directories were configured correctly so I suspected that something inside my httpd.conf file was amiss. Inside /etc/apache2/httpd.conf, I commented out two lines in the <Directory> block. This fixed the "forbidden" messages I was seeing for my virtual hosts. See below:
<Directory />
Options FollowSymLinks
AllowOverride None
# Order deny,allow
# Deny from all
</Directory>
2. I used the system.log in Console to detect and fix httpd.conf syntax errors. If you have syntax errors in any of your httpd.conf files, apache2 under Leopard will not start.
3. I removed the comment character from the start of the line below inside httpd.conf:
LoadModule php5_module libexec/apache2/libphp5.so
I am now back to where I was with Tiger.

Hotsync under Leopard

I'm fearful there is no good answer to my problem
I'm trying to get my Handspring Visor Platinum synching with Apple Calendar, etc., on nice new MacBook Pro running Leopard OS.
The installer on the Palm download site specified for my Visor will not run successfully. Installer errors.
Is there a version of Hotsync that will work with the Visor under Leopard?
Reading the Palm support site had given me hope I could get this working.
If I'm at a dead end, Palm should have the courtesy of saying so clearly in its support notes. But if there is some way to get the sync working that someone knows of then thanks in advance for answering.
Post relates to: Visor Platinum

Yes, that's the version of the software I tried to install. It does NOT install. The installer errors out. System is clean and brand new.
iSync is on the computer. The installer just will not run to completion, doesn't matter whether I try to install Palm Desktop along with Hotsync Manager, or not.
Does this install have some "Carbon" components? That may be part of the problem.
Is there a later version that might work with the Visor Platinum that's all OSX? With those of us who are older device owners, you ought to just keep the sync software up to date and charge us something for upgrades. $25 every computer or three would be a fair price to pay to maintain old habits and organization we're happy with. You'd retain more of your customers and sell us more of your new devices. Obviously your executives have dismissed that idea. Probably one more reason iTouch/iPhone sales are so hot.
But "solid and works for me" would still make a lot of pure software sales, and if people were convinced they could transition easily more would stick with Palm.
I bet you get told this all the time....Anyway, is there an installer around that's going to actually install software that will let me sync my Visor Platinum to my new MacBook Pro with Leopard. Pity if not -- the colours of the two devices go so well together. ;-)
Post relates to: Visor Platinum

Any luck with Aperture under Leopard problems. Here's the problem I'm havin

So, I can tell you that Apple knows of this problem. Two days ago I begun a thread that was a "roll call" for all those having problems with this app under Leopard.
Apple sent me a custom email back saying they had to remove the thread because it would be better to have seperate indiv's with their specific problems.
Ok, I buy that. But I know they are well aware of this problem. Not one mention of what they are trying to do to fix this. I have about 95 pct of my work in Aperture library and the Aperture vault. I will not use the other product from Adobe because, I paid for Aperture, I paid for Leopard and I really don't see why I have to purchase another product to do the work I've already paid for.
Anywho, my problem is still the crashing of Aperture not only when exporting but just randomly at anytime. I've kept Aperture closed not because it just is not worth my time to open the app at all. What a shame. I'm such a huge Apple advocate but now......
Why not at least a open letter from the Sr. Project Manager Joe Schoor? Anthing?
Has anyone found a sure fire fix for these issues? Thus far, I've tried to rebuild the Library, Re-install 1.5 and then upgrade online to 1.5.6 etc....

hi, tom
what are you running Aperture on?
when you reinstalled Aperture did you delete the Aperture folder in the applications folder and also the Aperture preferences, presets, caches files tucked away in the Home>Library and OSX>Library? if an application is misbehaving and you reinstall it but not remove all of it's files it may continue to misbehave.
I'm not an advocate of deleting Preference files and reinstalling but I might consider deleting the following files if I were in your shoes:
1. User\Library\Preferences\com.apple.Aperture.plist
2. Home>Library>Caches>Aperture - (Delete entire folder)
Maybe even the following:
3. Home>Library>Application Support>Aperture - (Delete entire folder. This will get rid of your presets and keywords)
4. Main Hard Drive>Library>Application Support>ProApps>Aperture System ID - (this will delete your serial number and you'll have to re-enter it).)
if any of the above files were corrupt the problem will be solved on start up or reinstall.
victor

Workaround to import video in FCP 6.0.5 under Leopard

On behalf of a FCP user under Leopard with FCP 6.0.5 I would like to ask you how to import video from a Panasonic camcorder using some strange format. The workaround now is to import it on another machine under Snow Leopard with iMovie, export it as one .mov 'for computer use' and import it in FCP 6.0.5 on the Leopard machine. The video from the camcorder does not play under Leopard, probably because of the QT version 7.6.6.
The Panasonic camcorder has an SD card with video which is recognised as a Camera Archive. It has folders with a name like PRG001 containing files like MOV001.MOD and MOV001.MOI and PRG001.PGI.
Possibly there is some plugin, extention or other workaround?
It is currently too expensive to upgrade FCP 6.0.5 to the latest version, although the 2006 MacBook Pro with Intel might be able to run it. I was advised not to upgrade to Snow Leopard without upgrading FCP, because it will cause all kinds of trouble.

Although I would still need to buy the "QuickTime MPEG-2 Playback Component for Mac OS X" to work with it, right? At least that is what MPEG Streamclip suggests when I try to open the MOVxxx.MOD files with it.

Unable to save HP printer presets under Leopard

I frequently print a colored first page from the manual paper tray and the rest of the document from another tray. Presets previously saved, work flawlessly under Tiger. I am not able to save presets under Leopard - all attempts revert to default settings. Maddening because we do numerous different print jobs - some requiring staples and collating, some with a color first page, some a mix of both. One of a kind -- no problem -- print 50 and you have to set the preset for each copy. AARG!! Solution -- unacceptable!! Boot under Tiger.

This is a known problem and will most likely require an update form Apple:
http://discussions.apple.com/message.jspa?messageID=5685294#5685294
http://discussions.apple.com/message.jspa?messageID=5684428#5684428
http://discussions.apple.com/message.jspa?messageID=5704164#5704164

Download error under apps. After following download steps multiple times still showing error message.

Download error under apps. After following download steps multiple times still showing error message.

Hi There,
Kindly try the below mentioned links.
Creative Cloud Help | Download Error in Apps tab of Creative Cloud Desktop Application
Creative Cloud - Download error - stubborn error
Thanks,
Atul Saini

Lexmark Optra S 1250 - Working under Leopard

I wanted to let people know that the Lexmark Optra S 1250 printer can work under leopard (10.5.1). It was quite a (stressful) experience getting it working but here were the essential steps:
1. After installing 10.5.1, reinstall the latest Optra S printer driver.
2. Ensure the printer is connected and powered on - mine is connected using a USB to Parallel converter cable but could also use an Ethernet cable
3. In the 'Printer & Fax Preference pane click the "+" to add a new printer.
4. Let the search for the printer driver complete(by gosh it is extremely slow!)
5. Click "Add" and when the drop-down box starts looking for 'printer options', don't wait (it never completes) but click the "Configure" button. Select your options and then exit.
6. Hopefully the printer now shows up as added on the left side of the Preference pane.
7. Close and then Restart the computer. I couldn't get the printer to respond to print commands (drove me crazy!) until after I decided to shut down and restart the computer.
8. If you still have problems, you may need to go back to the Printer & Fax Preference Pane, control-click on the printer icon in the left side of the pane and select "Reset print system". After that, redo steps 1 to 7.
Good luck
Rudy

Explain #8.
Did you restart after adding the drivers?
If you open the System Profiler, under Firewire or Printers what do yo see?
(Apple Menu/About this Mac/More Info/Firewire or Printer)
If it sees them then you know it's a configuration problem.

Forms compilation Errors under Linux

Hello,
I have a main form called Tbdoctrk.fmb.
This forms compiles and runs perfectly through Oracle 9i iDS.
When transfering the fmb file under Linux, and attempting to recompile using the f90genm.sh utility, I get the following compilation errors:
FRM-18108: Failed to load the following objects.
FRM-30436: Parent window not specified for canvas.View Canvas H_TOOLBAR
FRM-30041: Position of item places it off of canvas.
Item: BUTTON_HELP
Block: VARIABLE
Form: TBDOCTRK
FRM: Unable to adjust form for output.
====
I noticed that most of the object that failed to load (1 data block object, 1 canvas and a number of property classes and visual attributes) are contained in a file called TOOLBAR.fmb.
The TOOLBAR.fmb file compiles without errors under Linux/WIndows + is located in the same folder as the Tbdoctrk.fmb file.
1) How can I resolve this issue ?
PT
PS: I tried renaming the fmb files to upper/lower case without success.

Hello,
My main form called Tbdoctrk.fmb in turn calls a form called Pre_bord.fmb in a Program Unit.
Most but not all Class and Value Attributes are included in a file called toolbar.fmb. I did not find any specific reference to the toolbar.fmb file.
However, at compile time, I find that those objects are not loaded.
1) In what part of the main form Tbdoctrk.fmb should I find any such reference to the toolbar.fmb file ?
2) How should I create those symbolic links under Linux ?
PT

Vault errors under Leopard

Similar Messages

Maybe you are looking for