Idvd won't start, missing file

Used idvd without a problem, then later in the day idvd wouldn't start. Had to force quit and low and behold hidden under the idvd window was a message "unable to locate Billows01.dv I did a search for that file name to no avail. I did a reinstall from CD and I'm still getting that message. Any idea where I can find this file?
Thanks, Jim
20" imac, intel duo core, 2gb RAM Mac OS X (10.4.9)

Quit iDVD.
Locate a file named com.apple.iDVD.plist and get rid of it. iDVD will create a new one the next time it runs. Empty the trash and run a permission repair using the Disk Utility.
The files can be found here:
-->/Users/YourName**/Library/Preferences/com.apple.iDVD.plist
Sue

Similar Messages

Won't start - missing file

Suddenly AW will not open. Even trying to open a file gets the spinning coloured ball and the message "missing file cross dissolve 04. Cannot find file. Without this file the movie cannot play properly.
I'm not doing anything with a movie. I tried reinstall software but no help. All other programmes operate OK.
Any ideas?

Hello, Arthur. Welcome to the discussions. Try this, for starters:
http://discussions.apple.com/thread.jspa?threadID=121704
Also, are you opening your documents by double clicking them? Does appleworks open okay from the applications folder? It sounds like your appleworks docs got associated with imovie or something. After you follow Peggy's user tip, click once on a closed AW file icon, then press command + i for the get info window and change Open with to Appleworks.

[SOLVED] - X won't start - Missing modules??

Hello all, thanks for looking.
I have installed from the Arch from the latest media, and followed the Begginers Guide.
I have installed to a partition on my hard disk, one of many, and installed Grub and the mbr.
The system boots fine. ALSA works, Xorg is installed, and pacman -Syu says "nothing to do"
It all seems fine except... X won't start.
I type startx and get the following errors in the /var/log/Xorg.0.log file :
[ 263.878]
X.Org X Server 1.13.1
Release Date: 2012-12-13
[ 263.879] X Protocol Version 11, Revision 0
[ 263.879] Build Operating System: Linux 3.7.0-1-ARCH i686
[ 263.879] Current Operating System: Linux midnightsun 3.6.11-1-ARCH #1 SMP PREEMPT Tue Dec 18 12:58:46 CET 2012 i686
[ 263.879] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=64b15d8f-85f1-412a-8fa9-fd054849176e ro quiet
[ 263.880] Build Date: 16 December 2012 04:52:09PM
[ 263.880]
[ 263.880] Current version of pixman: 0.28.2
[ 263.880] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 263.880] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 263.881] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Jan 14 23:36:51 2013
[ 263.882] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 263.882] (==) No Layout section. Using the first Screen section.
[ 263.882] (==) No screen section available. Using defaults.
[ 263.882] (**) |-->Screen "Default Screen Section" (0)
[ 263.882] (**) | |-->Monitor "<default monitor>"
[ 263.882] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 263.882] (==) Automatically adding devices
[ 263.882] (==) Automatically enabling devices
[ 263.882] (==) Automatically adding GPU devices
[ 263.882] (WW) The directory "/usr/share/fonts/TTF/" does not exist.
[ 263.882] Entry deleted from font path.
[ 263.882] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 263.882] Entry deleted from font path.
[ 263.882] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[ 263.882] Entry deleted from font path.
[ 263.882] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 263.882] Entry deleted from font path.
[ 263.882] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 263.882] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 263.882] Entry deleted from font path.
[ 263.882] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 263.882] (==) FontPath set to:
/usr/share/fonts/misc/
[ 263.882] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 263.882] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 263.882] (II) Loader magic: 0x825a640
[ 263.882] (II) Module ABI versions:
[ 263.882] X.Org ANSI C Emulation: 0.4
[ 263.882] X.Org Video Driver: 13.1
[ 263.882] X.Org XInput driver : 18.0
[ 263.882] X.Org Server Extension : 7.0
[ 263.883] (II) config/udev: Adding drm device (/dev/dri/card0)
[ 263.884] (--) PCI:*(0:1:0:0) 10de:0402:0000:0000 rev 161, Mem @ 0xfd000000/16777216, 0xd0000000/268435456, 0xfa000000/33554432, I/O @ 0x0000cc00/128, BIOS @ 0x????????/131072
[ 263.884] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 263.885] Initializing built-in extension Generic Event Extension
[ 263.885] Initializing built-in extension SHAPE
[ 263.885] Initializing built-in extension MIT-SHM
[ 263.885] Initializing built-in extension XInputExtension
[ 263.886] Initializing built-in extension XTEST
[ 263.886] Initializing built-in extension BIG-REQUESTS
[ 263.886] Initializing built-in extension SYNC
[ 263.886] Initializing built-in extension XKEYBOARD
[ 263.887] Initializing built-in extension XC-MISC
[ 263.887] Initializing built-in extension SECURITY
[ 263.887] Initializing built-in extension XINERAMA
[ 263.887] Initializing built-in extension XFIXES
[ 263.887] Initializing built-in extension RENDER
[ 263.888] Initializing built-in extension RANDR
[ 263.888] Initializing built-in extension COMPOSITE
[ 263.888] Initializing built-in extension DAMAGE
[ 263.888] Initializing built-in extension MIT-SCREEN-SAVER
[ 263.888] Initializing built-in extension DOUBLE-BUFFER
[ 263.889] Initializing built-in extension RECORD
[ 263.889] Initializing built-in extension DPMS
[ 263.889] Initializing built-in extension X-Resource
[ 263.889] Initializing built-in extension XVideo
[ 263.889] Initializing built-in extension XVideo-MotionCompensation
[ 263.889] Initializing built-in extension XFree86-VidModeExtension
[ 263.890] Initializing built-in extension XFree86-DGA
[ 263.890] Initializing built-in extension XFree86-DRI
[ 263.890] Initializing built-in extension DRI2
[ 263.890] (II) LoadModule: "glx"
[ 263.890] (WW) Warning, couldn't open module glx
[ 263.890] (II) UnloadModule: "glx"
[ 263.890] (II) Unloading glx
[ 263.890] (EE) Failed to load module "glx" (module does not exist, 0)
[ 263.890] (==) Matched nouveau as autoconfigured driver 0
[ 263.890] (==) Matched nvidia as autoconfigured driver 1
[ 263.890] (==) Matched nv as autoconfigured driver 2
[ 263.890] (==) Matched nouveau as autoconfigured driver 3
[ 263.890] (==) Matched nvidia as autoconfigured driver 4
[ 263.890] (==) Matched nv as autoconfigured driver 5
[ 263.890] (==) Matched vesa as autoconfigured driver 6
[ 263.890] (==) Matched modesetting as autoconfigured driver 7
[ 263.890] (==) Matched fbdev as autoconfigured driver 8
[ 263.890] (==) Assigned the driver to the xf86ConfigLayout
[ 263.890] (II) LoadModule: "nouveau"
[ 263.891] (WW) Warning, couldn't open module nouveau
[ 263.891] (II) UnloadModule: "nouveau"
[ 263.891] (II) Unloading nouveau
[ 263.891] (EE) Failed to load module "nouveau" (module does not exist, 0)
[ 263.891] (II) LoadModule: "nvidia"
[ 263.891] (WW) Warning, couldn't open module nvidia
[ 263.891] (II) UnloadModule: "nvidia"
[ 263.891] (II) Unloading nvidia
[ 263.891] (EE) Failed to load module "nvidia" (module does not exist, 0)
[ 263.891] (II) LoadModule: "nv"
[ 263.891] (II) Loading /usr/lib/xorg/modules/drivers/nv_drv.so
[ 263.891] (II) Module nv: vendor="X.Org Foundation"
[ 263.891] compiled for 1.13.0, module version = 2.1.20
[ 263.891] Module class: X.Org Video Driver
[ 263.891] ABI class: X.Org Video Driver, version 13.0
[ 263.891] (II) LoadModule: "vesa"
[ 263.891] (WW) Warning, couldn't open module vesa
[ 263.891] (II) UnloadModule: "vesa"
[ 263.891] (II) Unloading vesa
[ 263.891] (EE) Failed to load module "vesa" (module does not exist, 0)
[ 263.891] (II) LoadModule: "modesetting"
[ 263.892] (WW) Warning, couldn't open module modesetting
[ 263.892] (II) UnloadModule: "modesetting"
[ 263.892] (II) Unloading modesetting
[ 263.892] (EE) Failed to load module "modesetting" (module does not exist, 0)
[ 263.892] (II) LoadModule: "fbdev"
[ 263.892] (WW) Warning, couldn't open module fbdev
[ 263.892] (II) UnloadModule: "fbdev"
[ 263.892] (II) Unloading fbdev
[ 263.892] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 263.892] (II) NV: driver for NVIDIA chipsets: RIVA 128, RIVA TNT, RIVA TNT2,
Unknown TNT2, Vanta, RIVA TNT2 Ultra, RIVA TNT2 Model 64,
Aladdin TNT2, GeForce 256, GeForce DDR, Quadro, GeForce2 MX/MX 400,
GeForce2 MX 100/200, GeForce2 Go, Quadro2 MXR/EX/Go,
GeForce2 Integrated GPU, GeForce2 GTS, GeForce2 Ti, GeForce2 Ultra,
Quadro2 Pro, GeForce4 MX 460, GeForce4 MX 440, GeForce4 MX 420,
GeForce4 MX 440-SE, GeForce4 440 Go, GeForce4 420 Go,
GeForce4 420 Go 32M, GeForce4 460 Go, Quadro4 550 XGL,
GeForce4 440 Go 64M, Quadro NVS, Quadro4 500 GoGL,
GeForce4 410 Go 16M, GeForce4 MX 440 with AGP8X,
GeForce4 MX 440SE with AGP8X, GeForce4 MX 420 with AGP8X,
GeForce4 MX 4000, GeForce4 448 Go, GeForce4 488 Go, Quadro4 580 XGL,
Quadro4 NVS 280 SD, Quadro4 380 XGL, Quadro NVS 50 PCI,
GeForce4 448 Go, GeForce4 MX Integrated GPU, GeForce3,
GeForce3 Ti 200, GeForce3 Ti 500, Quadro DCC, GeForce4 Ti 4600,
GeForce4 Ti 4400, GeForce4 Ti 4200, Quadro4 900 XGL, Quadro4 750 XGL,
Quadro4 700 XGL, GeForce4 Ti 4800, GeForce4 Ti 4200 with AGP8X,
GeForce4 Ti 4800 SE, GeForce4 4200 Go, Quadro4 700 GoGL,
Quadro4 980 XGL, Quadro4 780 XGL, GeForce FX 5800 Ultra,
GeForce FX 5800, Quadro FX 2000, Quadro FX 1000,
GeForce FX 5600 Ultra, GeForce FX 5600, GeForce FX 5600XT,
GeForce FX Go5600, GeForce FX Go5650, Quadro FX Go700,
GeForce FX 5200, GeForce FX 5200 Ultra, GeForce FX 5200,
GeForce FX 5200LE, GeForce FX Go5200, GeForce FX Go5250,
GeForce FX 5500, GeForce FX 5100, GeForce FX Go5200 32M/64M,
Quadro NVS 55/280 PCI, Quadro FX 500/600 PCI,
GeForce FX Go53xx Series, GeForce FX Go5100, GeForce FX 5900 Ultra,
GeForce FX 5900, GeForce FX 5900XT, GeForce FX 5950 Ultra,
GeForce FX 5900ZT, Quadro FX 3000, Quadro FX 700,
GeForce FX 5700 Ultra, GeForce FX 5700, GeForce FX 5700LE,
GeForce FX 5700VE, GeForce FX Go5700, GeForce FX Go5700,
Quadro FX Go1000, Quadro FX 1100, GeForce 6800 Ultra, GeForce 6800,
GeForce 6800 LE, GeForce 6800 XE, GeForce 6800 XT, GeForce 6800 GT,
GeForce 6800 GT, GeForce 6800 GS, GeForce 6800 XT, Quadro FX 4000,
GeForce 6800 GS, GeForce 6800, GeForce 6800 LE, GeForce 6800 XT,
GeForce Go 6800, GeForce Go 6800 Ultra, Quadro FX Go1400,
Quadro FX 3450/4000 SDI, Quadro FX 1400, GeForce 6600 GT,
GeForce 6600, GeForce 6600 LE, GeForce 6600 VE, GeForce Go 6600,
GeForce 6610 XL, GeForce Go 6600 TE/6200 TE, GeForce 6700 XL,
GeForce Go 6600, GeForce Go 6600 GT, Quadro NVS 440, Quadro FX 550,
Quadro FX 550, Quadro FX 540, GeForce 6200, GeForce 6500,
GeForce 6200 TurboCache(TM), GeForce 6200SE TurboCache(TM),
GeForce 6200 LE, GeForce Go 6200, Quadro NVS 285, GeForce Go 6400,
GeForce Go 6200, GeForce Go 6400, GeForce 6250, GeForce 7100 GS,
GeForce 6800, GeForce 6800 LE, GeForce 6800 GT, GeForce 6800 XT,
GeForce 6200, GeForce 6200 A-LE, GeForce 7800 GTX, GeForce 7800 GTX,
GeForce 7800 GT, GeForce 7800 GS, GeForce 7800 SLI, GeForce Go 7800,
GeForce Go 7800 GTX, Quadro FX 4500, GeForce 7350 LE,
GeForce 7300 LE, GeForce 7300 SE, GeForce Go 7200, GeForce Go 7300,
GeForce Go 7400, GeForce Go 7400 GS, Quadro NVS 110M,
Quadro NVS 120M, Quadro FX 350M, GeForce 7500 LE, Quadro FX 350,
GeForce 7300 GS, GeForce 7650 GS, GeForce 7600 GT, GeForce 7600 GS,
GeForce 7300 GT, GeForce 7600 LE, GeForce 7300 GT, GeForce Go 7700,
GeForce Go 7600, GeForce Go 7600 GT, Quadro NVS 300M,
GeForce Go 7900 SE, Quadro FX 550M, Quadro FX 560, GeForce 7900 GTX,
GeForce 7900 GT, GeForce 7900 GS, GeForce 7950 GX2, GeForce 7950 GX2,
GeForce 7950 GT, GeForce Go 7950 GTX, GeForce Go 7900 GS,
GeForce Go 7900 GTX, Quadro FX 2500M, Quadro FX 1500M,
Quadro FX 5500, Quadro FX 3500, Quadro FX 1500, Quadro FX 4500 X2,
GeForce 6150, GeForce 6150 LE, GeForce 6100, GeForce Go 6150,
Quadro NVS 210S / NVIDIA GeForce 6150LE, GeForce Go 6100,
GeForce 6150SE, GeForce 6100 nForce 405, GeForce 6100 nForce 400,
GeForce 6100 nForce 420, GeForce 7150M / nForce 630M,
GeForce 7000M / nForce 610M, GeForce 7050 PV / nForce 630a,
GeForce 7050 PV / nForce 630a, GeForce 7025 / nForce 630a,
GeForce 8800 GTX, GeForce 8800 GTS, GeForce 8800 Ultra,
Quadro FX 5600, Quadro FX 4600, GeForce 8600 GTS, GeForce 8600 GT,
GeForce 8600 GT, GeForce 8600 GS, GeForce 8400 GS, GeForce 9500M GS,
GeForce 8300 GS, GeForce 8600M GT, GeForce 9650M GS,
GeForce 8700M GT, Quadro FX 370, Quadro NVS 320M, Quadro FX 570M,
Quadro FX 1600M, Quadro FX 570, Quadro FX 1700, GeForce GT 330,
GeForce 8400 SE, GeForce 8500 GT, GeForce 8400 GS, GeForce 8300 GS,
GeForce 8400 GS, GeForce 8600M GS, GeForce 8400M GT,
GeForce 8400M GS, GeForce 8400M G, Quadro NVS 140M, Quadro NVS 130M,
Quadro NVS 135M, GeForce 9400 GT, Quadro FX 360M, GeForce 9300M G,
Quadro NVS 290, GeForce GTX 295, GeForce GTX 280, GeForce GTX 260,
GeForce GTX 285, GeForce GTX 275, GeForce GTX 260, GeForce GTX 295,
Quadroplex 2200 D2, Quadroplex 2200 S4, Quadro CX, Quadro FX 5800,
Quadro FX 4800, Quadro FX 3800, GeForce 8800 GTS 512,
GeForce 9800 GT, GeForce 8800 GT, GeForce GT 230, GeForce 9800 GX2,
GeForce 9800 GT, GeForce 8800 GS, GeForce GTS 240, GeForce 9800M GTX,
GeForce 8800M GTS, GeForce GTX 280M, GeForce 9800M GT,
GeForce 8800M GTX, GeForce 8800 GS, GeForce GTX 285M,
GeForce 9600 GSO, GeForce 8800 GT, GeForce 9800 GTX/9800 GTX+,
GeForce 9800 GTX+, GeForce 9800 GT, GeForce GTS 250,
GeForce 9800M GTX, GeForce GTX 260M, Quadro FX 4700 X2,
Quadro FX 3700, Quadro VX 200, Quadro FX 3600M, Quadro FX 2800M,
Quadro FX 3700M, Quadro FX 3800M, GeForce 9600 GT, GeForce 9600 GS,
GeForce 9600 GSO 512, GeForce GT 130, GeForce GT 140,
GeForce 9800M GTS, GeForce 9700M GTS, GeForce 9800M GS,
GeForce 9800M GTS, GeForce 9600 GT, GeForce 9600 GT,
GeForce GTS 160M, GeForce GTS 150M, GeForce 9600 GSO,
GeForce 9600 GT, Quadro FX 1800, Quadro FX 2700M, GeForce 9500 GT,
GeForce 9400 GT, GeForce 9500 GT, GeForce 9500 GS, GeForce 9500 GS,
GeForce GT 120, GeForce 9600M GT, GeForce 9600M GS, GeForce 9600M GT,
GeForce 9700M GT, GeForce 9500M G, GeForce 9650M GT, GeForce G 110M,
GeForce GT 130M, GeForce GT 120M, GeForce GT 220M, GeForce 9650 S,
Quadro FX 380, Quadro FX 580, Quadro FX 1700M, GeForce 9400 GT,
Quadro FX 770M, GeForce 9300 GE, GeForce 9300 GS, GeForce 8400,
GeForce 8400 SE, GeForce 8400 GS, GeForce 9300M GS, GeForce G100,
GeForce 9300 SE, GeForce 9200M GS, GeForce 9300M GS, Quadro NVS 150M,
Quadro NVS 160M, GeForce G 105M, GeForce G 103M, GeForce G105M,
Quadro NVS 420, Quadro FX 370 LP, Quadro NVS 450, Quadro FX 370M,
Quadro NVS 295, GeForce 9100M G, GeForce 8200M G, GeForce 9200,
GeForce 9100, GeForce 8300, GeForce 8200, nForce 730a, GeForce 9200,
nForce 980a/780a SLI, nForce 750a SLI, GeForce 8100 / nForce 720a,
GeForce 9400, GeForce 9400, GeForce 9400M G, GeForce 9400M,
GeForce 9300, ION, GeForce 9400M G, GeForce 9400, nForce 760i SLI,
GeForce 9400, GeForce 9300 / nForce 730i, GeForce 9200,
GeForce 9100M G, GeForce 8200M G, GeForce 9400M, GeForce 9200,
GeForce G102M, GeForce G102M, ION, ION, GeForce 9400, ION, ION LE,
ION LE, GeForce GT 220, GeForce 315, GeForce 210, GeForce GT 230M,
GeForce GT 330M, GeForce GT 230M, GeForce GT 330M, NVS 5100M,
GeForce GT 320M, GeForce GT 240M, GeForce GT 325M, Quadro FX 880M,
GeForce G210, GeForce 205, GeForce 310, ION, GeForce 210,
GeForce 310, GeForce 315, GeForce G105M, GeForce G105M, NVS 2100M,
NVS 3100M, GeForce 305M, ION, GeForce 310M, GeForce 305M,
GeForce 310M, GeForce 305M, GeForce G210M, GeForce 310M,
Quadro FX 380 LP, Quadro FX 380M, GeForce GT 330, GeForce GT 320,
GeForce GT 240, GeForce GT 340, GeForce GT 330, GeForce GTS 260M,
GeForce GTS 250M, GeForce 315, GeForce GT 335M, GeForce GTS 350M,
GeForce GTS 360M, Quadro FX 1800M
[ 263.895] (++) using VT number 1
[ 263.895] (EE) NV: The PCI device 0x10de0402 (GeForce 8600 GT) at 01@00:00:0 has a kernel module claiming it.
[ 263.895] (EE) NV: This driver cannot operate until it has been unloaded.
[ 263.895] (EE) NV: The PCI device 0x10de0402 (GeForce 8600 GT) at 01@00:00:0 has a kernel module claiming it.
[ 263.895] (EE) NV: This driver cannot operate until it has been unloaded.
[ 263.895] (EE) No devices detected.
[ 263.895]
Fatal server error:
[ 263.895] no screens found
[ 263.895] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 263.895] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 263.896] (EE)
It appears that some modules are missing, and indeed none of those mentioned in the errors are there if I do lsmod.
But that is about the limit of my understanding.
Can anyone tell me how to add the modules if they aren't even on the machine at all.
Pacman doesn't find them. For example pacman -S glx gives package not found.
Any ideas or pointers much appreciated.
Last edited by Midnight Sun (2013-01-16 00:01:35)

I Can't Believe It
NOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO!
I swear I checked that 6 hours ago when I first tried startx.
OH
MY
GOD
Just give me a moment to calm down..........
OK. Thank you. You are completely and joyously right.
It would seem that I had neglected to install the video driver.
Thanks for that.

[SOLVED] Apache won't start; missing 4 modules

Hello,
Not sure if this is the correct place to post this, but httpd won't start after an update.
First it claims each of these 4 modules are missing:
LoadModule authz_default_module modules/mod_authz_default.so
LoadModule authn_default_module modules/mod_authn_default.so
LoadModule disk_cache_module modules/mod_disk_cache.so
LoadModule mem_cache_module modules/mod_mem_cache.so
If I comment these in httpd.conf, the error changes to
httpd: Configuration error: No MPM loaded.
Can anyone please help?
Thanks!
Last edited by r0cz (2014-03-15 16:45:22)

progandy wrote:
nparasta wrote:Oh okay. Yes I actually removed them. In httpd.conf I had set some apache settings, though most of the settings were on their default values. I should maybe re-install apache to get the new files back and redo my settings since the files are so different.
You might want to do that. that is why pacdiff offers the merge option.
PS: Here is an overview of the changes between 2.2 and 2.4: http://httpd.apache.org/docs/2.4/upgrading.html
This solved my problem. Thank you for all your help :-)
Last edited by nparasta (2014-03-24 06:47:01)

IPhoto won't start (Missed theme font)

This is my first Apple experience at all and I'm enjoying it, but I have encountered a problem.
iphoto won't start, it just says: "The font required to run this application is missing"
I'm in Mavericks 10.9.3, fresh installation with few programs, I never touched any fonts or anything in font book.
I tried to reinstall with no luck ... so I don't know which is the problem.
Here just few lines of error log:
Application Specific Information:
*** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'System font path not found in bundle at path: /Applications/iPhoto.app/Contents/Frameworks/ProKit.framework'
abort() called
terminating with uncaught exception of type NSException
No problem so far with imovie, just iphoto let me go crazy.
Any idea to solve the issue?

Open FontBook. It's in your Applications folder.
From the FontBook menu bar click File > Restore Standard Fonts
Restart your Mac then try iPhoto.

Installer won't initialize, "missing file"?

Hey all, I'm pounding my head against the wall here trying to install CS6 Design Standard on my Mac (OSX 10.7.3). I first tried to install last night, and everything seemed to be going just fine. The installer opened, I entered my serial number and selected the products I wanted to install. The problem started when my damned computer locked up in the middle of the install. I tried to restart the install multiple times last night, but I think I had to many other things going on for the system to handle and it kept locking up.
I went to bed last night without having time to troubleshoot. This morning, I try again and now the installer gives me the "installer failed to initialize. this could be due to a missing file." error. Never seen that before. I immediately thought there could be something wrong with my disc, from all the locking up last night, so I did a system-wide virus scan, verified and repaired the permissions, verified and repaired the disc using the Startup Disc Utility. I came back and the installer still gives me the same error. I deleted the entire 4GB package I downloaded from Amazon, emptied my trash bin and downloaded a "fresh" copy from Amazon. Same problem.
I have no idea what to do now. Please help.
Regards,
James

Any reason you're downloading from Amazon instead of from the Adobe website?
The "failed to initialize" error usually indicates that the extraction process after the download did not complete correctly. In most cases, you can re-extract to resolve the issue, but sometimes you need to download again.
http://helpx.adobe.com/x-productkb/global/installation-launch-log-errors-creative.html
You may want to try the direct download link from here: http://prodesigntools.com/adobe-cs6-direct-download-links.html
(Be sure to follow the instructions on the page _before_ clicking the link, or you will get an access denied error.)
HTH

Another Itunes Won't Run - Missing Files

I installed iTunes 10.2.1 on my XP computer.
However it wouldn't run - missing files; please reinstall.
So I uninstalled it and tried again but the same thing happened.
I tried uninstalling the Apple progs etc as well but no joy.
I uninstalled and went back to version 9.2 but it didn't fix it.
Is there anyway of fixing this as I now have an iphone that I cannot use. No wonder people don't like iTunes.

Got it working now by disabling Bonjour Service at startup......
Right click on My Computer and select Manage.
Select Services and Applications and then Services.
Scroll down to Bonjour Service and right click Properties.
Under the General Tab, select the startup type as Disabled.
Restart your computer.

Onestep iDVD won't start reliably

I am unable to get the Onestep iDVD feature to start up reliably. I have connected my digital camcorder via firewire cable to my Mac and when I launch the Onestep iDVD feature I can't get it to get started except with a lot of fidgeting with restarting the application then the camcorder, and re-inserting the blank DVD.
Is there only one correct sequence?
What is causing failure to complete? I have been able to get it started once out of ~10 trys, but it was very frustrating. Any ideas?
My Mac is a 933 Mhz G4, 1.5 GB Ram with superdrive, 20 GB free HD space, OS 10.3.9 with iDVD life 5.0.1
I verified that the camcorder is mounted on the firewire bus. By the way is it possible that it has to be connected to firwire port #1. It was connected to port #2, since port #1 normally has a hard drive but was disconnected. Should I be using the camcorder only on port #1?
Thanks,
Brian

I can't get it to get started
What happens?
20 GB free HD space
That's minimal... We recommend 20GB+.
FireWire ports shouldn't be an issue; especially if you have the other one empty.
How many hard drives in there? Names similar?
I can't believe I'm responding to a OneStep question... I dislike (hate) OneStep.

Toshiba M45-s269 Windows won't start-missing or corrupt file

Toshiba M45-s269 Windows xp sp3
Recently got the message upon a restart that "Windows cannot start because a file is missing or corrupt" then names the file "<Windows root>\system32\ntoskrnl.exe."
Screen show options to restart windows normally, in last known good config, safe mode, safe mode with command prompt or with networking. All options only have the result of a 2-minute freeze-up and returning to the same screen after showing the Toshiba splash screen.
I was able to F12 at splash screen which gives the option of what to reboot from: Multiple discs, single disc, floppy or networked. Otherwise all options have same looped result notifying cannot start due to missing/corrupt file.....
Having the factory recovery disc, I was able to select the single disc option with F12 at splash and try running a recovery from D:/.
The disc, however, says it will reload Windows 98 (the computer came with XP Home) and wants to re-format which will blow out EVERYTHING I have on the hard drive which is NOT an option for me!
A while ago I was given a disc from a friend that has XP Professional. I have been trying to restore from that with less than expected results. Have gotten to a DOS promt and tried to COPY the file from XP Pro disc but being told cannot find the file. I'm most likely not doing something right. Don't know what destination to send it IF I'm able to copy the file anyway.
Tried to load XP Pro on hard drive but computer sees the Home version and gives the message that loading 2 OS's is not recommended. Was hoping that XP Pro would simply over-write Home.
Any help appreciated. Thanks in advance,
Rob

Hi
Setup CD is not delivered with your notebook, just recovery CD and recovery CD does not offer repair option.
Try to obtain Microsoft Installations CD. Talk with your friends. I am pretty sure someone has this WXP installations CD. Check if you can do something using R option.
Check also what Microsoft wrote about this issue:
http://support.microsoft.com/?kbid=307545
http://support.microsoft.com/kb/269075/en-us
Good luck!

Mac won't start up - files not backed up - Genieo behind problem?

Hey guys,
I'll give you some background information on the matter so far; I bought my iMac 21.5in last year. It's currently running OS X Mountain Lion. I've had this problem where whenever my mac freezes (which has been quite often over the past two months) and it's still frozen after 10 minutes, I just turn it off manually. Then when I switch it back on, a kernel or folder with a question mark on a white screen of startup comes back to haunt me. Usually when this happens, I just unplug the power point and switch it back on after a few hours or the day after, which seems to fix the problem. Well that's not working this time.
Yesterday I tried updating my flash player and I clicked a link which I thought was the official adobe site and pressed download. Upon downloading, it was standard procedure, until the Genieo icon popped up on my desktop. I've encountered Genieo once before (around a month ago) and it froze my computer. When I was able to start it up again (unplugging power point and turning on computer after a few hours) I was able to get rid of it by deleting everything Genieo related. Well, not this time. When I first saw the icon I quickly put it in the trash and emptied it, but it was too late. It had already put the "InstallMac" as all my browser home pages. My computer then froze and I had to manually switch it off.
Now, when I start up my computer it won't make the start up noise anymore. I can't get past the the folder with the question mark on normal start up. Here's what I've tried so far and what happens:
- Holding "Shift" to start up "Safe Mode". Folder with question mark comes up and nothing happens.
- Holding "Option" for "Start Up Manager". I click my volume and the kernel comes up.
- Holding down "Command + R" for "Recovery Mode". This works and the globe comes up on my screen and then takes me to the "Recovery Mode" menu.
So we've established the only thing I can do upon start up is go into "Recovery Mode" (unless there are any other startup key combinations that will assist my problem that I don't know about). The options it provides me with are:
- Restore from Time Machine backup
- Reinstall OS X
- Get help online
- Disk Utility
Because I'm an idiot and thought nothing would ever happen to my iMac, I have never backed up my files onto an external hard drive, so Time Machine isn't an option.
I've tried reinstalling OS X. When I click here it gives me the option to reinstall Mountain Lion OS X. I click on it and it comes up with a pop up along the lines of this is already installed on this volume. One time I clicked on Reinstall OS X and Mavericks came up instead of Mountain Lion. This only happened once and I'm not sure why. I clicked on install and waited for it to install Mavericks OS X for like 30 minutes, but then came up with an error telling me it was unsuccessful. I've also tried installing OS X onto an external hard drive but it failed. So that isn't an option.
Now there's only Disk Utility left. The "First Aid" tab gives me the option to verify and repair my disk.
Now, the majority of the times, I verify my disk and it tells me that there's nothing wrong with it, so I restart my computer and the folder with the question mark or kernel come up upon start up.
Only a few times have I encountered where I verify my disk and it tells me to repair it. Then when I repair it tells me it was unsuccessful and to back up all my files. But I haven't got my files backed up.
I've tried restoring my disk onto an external hard drive through the "Restore tab" but it always fails.
I'm a noob when it comes to mac, so here I am. The thing is, the kernel/folder with question mark on start up screen has happened many times before without Genieo, just whenever it freezes or whenever something goes wrong. But this time with Genieo I can't get past it.
If any of you guys could help me that'd be sweet. If I have no luck I'll have to take it to the apple store, which is really a last resort, and something I don't want to do.
Thanks heaps,
Chris.
P.S. I made a post before this regarding the same matter, but decided to make it again with a bit more information. On that last post Genieo_support commented on it acting innocent saying Genieo wouldn't be behind this, and have also provided an uninstall link, which I can probably get to through the "Get help online" option on "Recovery Mode". I don't trust Genieo as it is already, but is this link actually an uninstall link?

That is a great site and provides some good information on removing the adware Genieo. He has posted some information on removing Genieo when not being able to get onto my computer, which is exactly my situation. Under this heading he has put a terminal command to remove the Genieo file. He has also written:
After you have executed the “rm” command successfully, you should be able to restart the computer successfully. If you get an error saying “No such file or directory,” you have made an error somewhere in the file path and will need to correct it. If you cannot figure out how to correct it, seek professional assistance.
Unfortunately for me, I got the "No such file or directory" error, so I don't think there are any other ways to fix my problem.
I've checked many sites on removing Genieo, fixing the kernel and fixing the folder with the question mark, but I seem to have an extreme problem that the solutions can't resolve. My only option now is to seek assistance for the apple store.

CS5 - Photoshop won't start: preferences file was invalid (it has been deleted)

Environment:
Win7 Ultimate - 4 gig ram - CS5 Design Premium
Seemingly out of the blue - Photoshop stopped loading and I'm getting two error messages :
first: ADOBE PHOTOSHOP CS5 Extended: "Could not load actions because an unexpected end-of-file was encountered
second: ADOBE PHOTOSHOP CS5 Extended: "could not initialize Photoshop because the preferences file was invalid (it has been deleted).
I've deleted the two Preferences Files - but they don't seem to repopulate on startup - (or if they do they are deleted per the error message)
I tried copying a Preferences file from another working machine but that failed as well.
In addition: Dreamweaver is kicking out the following error messages - but opens and seems to work normally.
The following JavaScript error(s) occurred: Unable to open script file C:\Program Files (x86) Adobe\Adobe Dreamweaver CS5\Configuration\Shared\Spry\Designtime\EditingUtils.js (error 2).
The following JavaScript error(s) occurred: Unable to open script file "C:\Program Files (x86) \Adobe\Adobe dreamweaver CS5\Configuration\Shared\Common\Scripts\dwscripts.js" (error 2).
I'm in the middle of a big project and need to get back up quickly - any help would be much appreciated.
Thx.

Run photoshop as administrator holding Ctrl + Alt + Shift, that should trigger a preferences reset prompt.
If that won't work I would do a backup and delete the entire Adobe Photoshop CS5 Settings folder, not just the two files you mentioned.
As for your Dreamweaver issue, try deleting WinFileCache-********.dat (or FileCache.dat) from your Dreamweaver Config folder.
Otherwise try deleting your preferences
Exit Dreamweaver.
In Windows Explorer, navigate to C:\Users\Your User Name\AppData\Roaming\Adobe.
Rename the Dreamweaver preferences folder:
Dreamweaver CS5: Rename the Dreamweaver CS5 folder to, for example, Old Dreamweaver CS5.
Choose Start, type regedit in the Start Search, and then press Enter.
In the left pane of the Registry Editor, navigate to the following key:
HKEY_CURRENT_USER\Software\Adobe
Remove the Dreamweaver preferences registry entries.

Updated to iLife '08 and now iMovie and iDVD won't Start

I received a copy of iLife '08 for Christmas and finally got around to upgrading today. The new iPhoto works just fine but when I try to start iMovie, it crashes (I have included part of the Problem Report below). I have tried restarting and it doesn't help. Then I tried to start iDVD and it flashes the "Welcome" / "Open" screen and then quits before I can do anything -- no error report. Any ideas on how to:
1) Fix both programs so they will launch -OR-
2) Restore the old versions of iMovie and iDVD
Thanks!
Process: iMovie [345]
Path: /Applications/iMovie.app/Contents/MacOS/iMovie
Identifier: com.apple.iMovie7
Version: 7.0 (471)
Build Info: iMovieApp-4710000~2
Code Type: X86 (Native)
Parent Process: launchd [104]
Date/Time: 2008-01-02 15:53:31.019 -0500
OS Version: Mac OS X 10.5.1 (9B18)
Report Version: 6
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Crashed Thread: 0
Application Specific Information:
* Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Creating more than one Application'

Run Software Update (under the Apple menu) and update that software.

TS3423 17" macbook pro won't start blue file with question mark is all that appears on the screen

My old macbook pro will not start up. Worked fine yesterday, today all I gat is the startup sound and a blank blue screen. After a while the screen shows a file folder icon with a question mark in it. Any ideas

Question (?) Mark, Blinking Folder, or Gray Screen at Startup
These are related but not identical issues. Their causes are outlined in Intel-based Mac- Startup sequence and error codes, symbols. Solutions may be found in:
A flashing question mark appears when you start your Mac
Mac OS X- Gray screen appears during startup
In most cases the problems may be caused by:
Problem with the computer's PRAM - See Resetting your Mac's PRAM and NVRAM.
Boot drive's directory has been corrupted - Repair with Disk Utility.
Critical system files are damaged or deleted - Reinstall OS X.
The disk drive is physically non-functional - Replace the hard drive.
Repair the Hard Drive and Permissions
Boot from your Snow Leopard Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer.
If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
The main difference if you are using Lion or Mountain Lion is that you must first boot from the Recovery HD:
Boot From The Recovery HD:
Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
Reinstall Snow Leopard Without Erasing The drive
1. Repair the Hard Drive and Permissions
Boot from your Snow Leopard Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer.
If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
2. Reinstall Snow Leopard
If the drive is OK then quit DU and return to the installer. Proceed with reinstalling OS X. Note that the Snow Leopard installer will not erase your drive or disturb your files. After installing a fresh copy of OS X the installer will move your Home folder, third-party applications, support items, and network preferences into the newly installed system.
Download and install Mac OS X 10.6.8 Update Combo v1.1.
Reinstalling Lion/Mountain Lion Without Erasing The Drive
Boot to the Recovery HD: Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
Repair the Hard Drive and Permissions: Upon startup select Disk Utility from the main menu. Repair the Hard Drive and Permissions as follows.
When the recovery menu appears select Disk Utility. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the main menu.
Reinstall Lion/Mountain Lion: Select Reinstall Lion/Mountain Lion and click on the Continue button.
Note: You will need an active Internet connection. I suggest using Ethernet if possible because it is three times faster than wireless.

AfterFX.exe won't start - missing FTL.dll error

This is part of the Creative Suite CS3. All other components work. AfterfX.exe will not start. I reinstalled but no change.
I'm on a Gateway FX540b with Vista Home Premium. I have not applied SP1 yet.
Any ideas?

Is your system up to the latest patch level otherwise? Do you use any CoDec packs on your system? The issue is not dependent on the DLL - there is no such a thing as an ftl.dll (though it would be nice, as according to "Galactica" lore it means "faster than light" and would accelerate your computer a trillion times *giggle*) :-) Remove any CoDec packs you may have on your system. Also look into alternate media players like MPlayer Classic or VLC - they sometimes bent your media file handling assignments in unpredictable ways and may thus screw AE. As an last item, temporarily disable any security tools you may have on the system. If they are protecting or deep-scanning some files, they will respond to any access of those files in similarly unpredictable ways.
Mylenium

Another PSCS5 Won't Start/Scratch File/Permissions Thread

Win 7 x64, PS CS5 12.0.3. 12GB RAM, SSD for C:, HDD for D:, >900GB available on D:.
PS starts fine with only C:/ selected as scratch file location. But when I add a secondary scratch file location of D:/, I get the following errors on PS startup,
I have searched and read everything I can find about this problem but to no avail. In exploring this problem, I have set permissions for C: and D: to Full Control for my user account, administrator account, System, and authenticated users. No change in behavior. I have deleted the Preferences file, although as shown above, PS itself is deleting it. After the prefs file is deleted, whether by me or PS, PS starts fine, but with only C:/ as scratch. If I again add D:/ it again errors on next start.
I know of no problem with D:, no error messages except the one from PS. It is also used for a second Windows pagefile location and Windows TEMP/TMP files.
PS will start with D:/ selected as a scratch file location if I Run As Administrator.
I don't see any relevant error in Event Viewer, although I am incompetent and ignorant of that tool.
Any help will be appreciated.
Hold on, before hitting the Post button, I tried one more thing. I did the CTRL-ALT thing on PS startup and added D:/ as a scratch file location in that dialog. Then close PS, start it again. No problems. So it appears that PS just doesn't like to have a secondary scratch file location added from the running application by calling up the Edit/Preferences/Performance dialog.
I'll go ahead and make this post, hoping it might help someone else, and I will watch things for a while, maybe back off on some of the permissions, and report back with any findings.
Stan

No, I haven't been unable to access the scratch folder. I have been unable to successfully have Photoshop use my D: drive as the location for a secondary scratch file if it has insufficient room on C:. Going into the Edit/Preferences/Performance dialog and telling Photoshop to add the D: drive as the secondary location for a scratch file does not work. It appears to work, and a new preferences files is written, but when Photoshop opens the next time, it says it encountered a disk error and that the preferences file is invalid and then it deletes the preferences file. Then I can open Photoshop and it will make a new preferences file and works OK, but with only C: as the scratch file location, per default. If instead, I press CTRL-ALT immediately after starting Photoshop, it opens a dialog to ask me where I want scratch files. I can tell it C: and D:, it makes a preferences file with that information, and then everything is fine. I just don't know why I can't accomplish that from within Photoshop using the Edit/Preferences dialog. As I said, this behavior does not depend on file permissions.
As to what I have been through, it is pretty much what I have described, elevating file permissions to Full Control for all user categories, resulting in no change in behavior, and then trying the CTRL-ALT procedure, which solves the problem, and then lowering the permissions to where they were before, and the CTRL-ALT procedure still works. Every time. And the Edit/Preferences dialog never works (for this purpose).
Uh, oh, there is more to this. Although the CTRL-ALT procedure solved the problem specifically for setting the secondary scratch file location, I just tried setting some more preferences from within Photoshop, and got the same behavior as before, namely that the two error messages appear the next time Photoshop tries to open. So it appears to be more general, occuring whenever Photoshop creates a preferences file from the Edit/Preferences dialog. [Note: not right, further experiment results later.]
Now what?
Noel, if you believe this is due to security settings, I am willing to try whatever you recommend, but I believe you think I should solve the problem by elevating file permissions (which I have already tried) and running on an administrator account, and dealing with security issues in Windows and with procedures. But does everyone else using two drives for scratch files have to do that? I think I have something messed up somewhere but I don't know what.
Here are three scenarios:
Scenario #1:
1. Delete preferences file.
2. Open PS running as user.
3. A prefs file is created, but with 0 bytes, as observed in Windows Explorer.
4. Using Edit/Preferences/Performances, add D: as a secondary scratch drive.
5. Close PS.
6. The prefs file now has 190 KB. .
7. Open PS running as user.
8. Error messages received, PS does not start. Prefs file is deleted.
Scenario #2:
1. Start PS using CTRL-ALT procedure.
2. In the Scratch Disk Preferences dialog that comes up before PS, set D: as a secondary scratch drive.
3. A prefs file is created, but with 0 bytes.
4. Close PS.
5. The prefs file now has 190 KB.
6. Start PS, running as user.
7. Look in Prefs, shows C: and D: as scratch drives.
8. Close PS.
9. Time stamp of prefs file is updated.
Scenario #3:
1. Delete prefs file.
2. Start PS, Run As Administrator.
3. Using Edit/Preferences/Performances, add D: as a secondary scratch drive.
4. A prefs file is created, but with 0 bytes.
5. Close PS.
6. The prefs file now has 190 KB.
7. Start PS, Run As Administrator.
8. Look in Prefs, shows C: and D: as scratch drives.
9. Close PS.
10. Time stamp of prefs file is updated.
11. Start PS, running as user.
12 Get errors, prefs file is deleted.
Note that I used scratch file locations in these scenarios. I do't think it has anything to do with scratch files, as it turns out. It seems to just be how the prefs file is created.
Further experiment.
Open PS as user, Edit/Preferences/Cursors, don't change anything, hit OK, close PS.
Open PS as user, opens OK. Edit/Preferences/Performance, don't change anything, hit OK, close PS.
Open PS as user, get errors.
Open PS as user, Edit/Preferences/Performance, don't hit OK, switch to Cursors dialog, no changes, hit OK, close PS.
Open PS as user, get errors.
Open PS as user, Edit/Preferences/Performance, don't change anything, Cancel, close PS.
Open PS as user, opens OK.
OK, so it doesn't have anything to do with scratch files, it just has to do with visiting the Preferences/Performance dialog. Unless the only action taken is to Cancel the dialog.
My head hurts.
Stan

Idvd won't start, missing file

Similar Messages

Maybe you are looking for