Attaching a CRT

I am using a standard DVI to VGA connecter that works fine with my PC. It's not the apple-supplied one, but it should in theory work (tell me if I'm wrong).
The monitor I'm trying to connect is a 21' Sun CRT. It takes VGA input. It works fine connected to my DVI gfx card on my PC, via the dvi->vga adapter.
The Macbook recognises the CRT, and the CRT appears to be getting a signal (if it wasn't, it would sleep), however I am only getting black. I can move windows from the macbook's screen over to the other screen, but I still only see black.
How can I fix this? Is it just a problem because I'm not using the Apple adapter?

I think I figured out the problem. The Refresh rate is too low. How can I change the res / refresh rate of the other monitor?
My monitor says "Out of Scan Range". I usually run at about 120Hz, 1600x1200 in Windows. It's set to 1600x1200, 75 Hz here, but I can't figure out how to increase the refresh rate
I can change my macbook's resolution and would be able to change it's refresh rate if it was a CRT.. but there is no where to change settings for the secondary monitor!

Similar Messages

Ripples in CRT Monitor

At work I have a single processor 1.8 G5 with a Veiw Sonic Pro display. All my edges have ripples to them on the windows I open. But if I am in photoshop the box atound the photo is straight. Any Help?

OK. I try different video card(5570) and same thing happens! For ones who hate to read from beginning I can't see whole image(only upper left quarter) when I enter in bios on my P67S-C43 attached to my 4/3 CRT LiteOn monitor over VGA adapter! I tried different adapter, different monitor, GFX card and none help! I can see whole bios only when I attach widescreen monitor! It looks like my motherboard just hate CRT monitors! Latest thing that I'm noticed is some ghost of my cursors when I enter in bios when it's attached to CRT monitor! And also appears that bios is write something before I enter in bios, but I can't see what cos can't see whole image!
Anybody have some suggestion? Anybody knows in witch resolution works my EFI click bios? Should I report to MSI as a bug?

Black screen on boot

Toshiba Satellite L675D-S7013 laptop, Part No.# XXXXXXXXX
The problem started by the display getting dimmer and dimmer until black
screen.
The system attempts to boot, e.g. the DVD light blinks and you can hear
the disk, then nothing. No boot display.
I attached a CRT monitor to the VGA port and tried booting again. No light
on that screen either, not even the light that shows the laptop is sending
a signal.
The CMOS battery is probably okay because the system tries to boot.
The lack of signal to the CRT bothers me; I don't want to replace the LCD
screen if there is no video output.
The laptop is disassembled, but not the screen yet, and I don't see
anything obviously wrong.
What is the next step in finding the problem?
[Moderator edit to remove serial number.]
Solved!
Go to Solution.

It sounds as if the onboard video chip is bad. If the LCD screen were the problem, you would still get video on an external monitor.
Did you notice any dust build-up around the intake vents, cooling fan or heat sink baffles? Overheating will cause the solder joints on the video chip to break connection.
FWIW, I have a laptop with the same problem. I've ran every test that Google and Youtube came up with. Every indication points to a bad GPU. I've ordered a new motherboard and hopefully that fixes the problem.
Hope this helps. Good luck.

Attaching MBP to a crt HDTV

I'll be getting a CRT HDTV soon and i was wondering if the picture, when hooking up the MBP, is as good as a LCD tv? I was wondering because i know if you try to hook up a computer to a non-HDTV CRT the picture is crap. I'll be using a DVI to HDMI cable. thanks

The output looks great on my LCD TV.
But the reason people pick LCDs is that they are light weight, thin, and low power. Nobody picks an LCD because of the superior image quality. While heavy, thick, and power hungry, a CRT should be bright and beautiful. Enjoy it.

I am getting error while attaching Menu Module to FORM

Hi to everyone, I have created a Menu Module(mmx file), now i am trying to attach that menu to a FORM, I have entered the proper Menu Module address in the property window of that FORM, but i am continously facing the following problem.
FRM-40738: Argument 1 to builtin CALL_FORM cannot be null
Also i have applied following code in that Menu Module
call_form('F:\Database Files\Contingent Database\Forms & Reports\Forms\BILL DETAIL.fmx');
but the required FORM is not running.
Please help me to sove out this problem

I did this today, in this way,
I create the menu then CRT-SHIFT K, then CRT -T
then check you have the mmx
- now you put full path to the form
Menu module like c:\aaa\bb\menuname
I did not put extension
Hope this will work.

17in CRT Studio Display (Blue & White)-blinking power button

I have an Apple 17in Studio Display (CRT-Blue and White vintage) connected to my Power Mac G5.
Last night, I went home, and turned it on..or rather tried to turn it on but found it stayed black, with the power button blinking green->amber->green->amber etc.
As far as the computer was concerned, the monitor was still there and working (dual monitors...the mac kept the b&w as if it was turned on).
I swapped the monitors to the different video ports and the other monitor worked fine, so it's not the video card or vga->digital adapters.
I unplugged the monitor and replugged it, and it stayed with the blinking light.
Restarting the computer with the monitor attached had the computer still running as if the monitor was working just fine, so it seems to be getting what ever kind of feedback the mac gets to let it know a video card is there.
Anyone have any idea what could be up?

Addition
http://www.whoopis.com/computer_repair/
is better for a start.

LabVIEW 2009 crashes at startup with the presence of a certain CRT version on the system

When installing our LabVIEW integration package on a system running
LabVIEW 2009 LabVIEW will crash at startup afterwards. Using 'dependency
walker' reveals, that 'nicont.dll' causes this crash because of a
side-by-side configuration problem. After some debugging I found out
that on this particular system installing a certain version of the
Microsoft CRT will stop LabVIEW from functioning. My fix now is to
recompile our code with a newer version of VS. I now ship a VS9 version
of the runtime and everything is working as expected.
However
I guess the real problem lies within the LabVIEW installer. I guess a
needed version of the CRT is not installed by LabVIEW. It still works
because due to some policy files on the machine it gots defaulted to a
compatible version at startup. However when I install the following 2
merge modules on the target system LabVIEW does no longer work:
Microsoft_VC80_CRT_x86.msm (file version inside: 8.0.50727.762)
policy_8_0_Microsoft_VC80_CRT_x86.msm (file version inside: 8.0.50727.4053)
Renaming
the *.policy file in the SxS dir on the target system gets LabVIEW back
to run, but of course other SW needing this file does not run then
I was using XP, 32 bit SP 3
I can provide additional information if needed. Is this a known problem? Is there a fixed version of LabVIEW already?
Message Edited by anotherStefan on 02-05-2010 05:44 AM

Sure! I tried to attach the installer causing the problem to this message.
However I failed miserably(BAD GATEWAY from the upstream server). Where can I upload the installer to or what do I need to do?
It will install some other stuff as well (A bunch of VIs, a DLL and an
OCX(this needs the CRT I have trouble with)and the CRT and MFC runtimes I
mentioned. An updated version of the installer can be obtain here(however it does no longer show the issue):
http://www.matrix-vision.com/functions/count.php?url=products/hardware/family/SC/mvBlueFOX/LabVIEW_a...
The only difference between the two packages is, that the OCX in the
attached file has been build using VS2005SP1 and in the package the link
points to I did use VS2008. Apart from that I changed the 2 merge
modules from Microsoft (CRT and MFC)

Using Mac Mini with 16:9 CRT Standard Def TV by RCA connection!

Hello all,
I realise that there are others who have experienced similar problems but after spending quite a bit of time searching this forum, I wasn't able to find an answer for my particular circumstance. In summary, I can't get my new Mac mini to work with my TV at all. I need to figure out where the problem might lie. Please find the specifics of my setup below.
I have a 1.42GHz Mac Mini G4 with all the possible add-ons . It actually did not come out of the box for the first three months I owned it. I finally got it out this weekend and went to purchase a DVI-Video connector. I connected it to the TV by means of an RCA to Scart cable (which I know for a fact works fine with my Powerbook and iBook) and the TV just showed a blank screen (though there was a second or two of static each time I started up, as if settings were being re-adjusted). The TV only has Scart inputs so there RCA is going to have to be the connection method. The TV is a standard def Sanyo 16:9 CRT.
To make sure the mini was working, and enable VNC access (brand new mini so hadn't been set up at all), I took it to my office (I have no other monitors here) and connected it to a normal Dell LCD monitor. It worked fine, and I set up VNC access so now I can use my powerbook to control it headless.
I brought it back home and connected it to the TV again and VNCed to it expecting to find options to re-adjust resolution, refresh rate etc. All I found was 800x600 or 640x480 and I could not change the refresh rate at all. The TV is PAL but there was no mention of PAL or NTSC options. I took the opportunity to run software update and apply all the necessary updates as well.
After some initial research, I downloaded displayconfigx. It crashes every time I try to open it... so no luck there. Then I tried another application recommended on these fora whose name escapes me now (but it started with an s and also ended with an x) and to keep a long story short, I found it very confusing and wasn't able to find a setting that made things work.
The TV works fine as a secondary display for both my powerbook G4 and iBook G3. In fact, I'm using it with my powerbook now and my powerbook switches to the right settings as soon as I plug it in! However, my powerbook's place is in my lap and this Mac mini is sitting there unused when I really want to be using it as my media center and EyeTV box!
Please help me. Is this a problem with the DVI-Video adapter. Is this a problem with the mini? Should I call Apple Support (I don't have Applecare but it was purchased three months ago)? Please help me solve this problem!
Thanks,
Phaedon

Thank you very much for these helpful suggestions and questions!
I'm at work at the moment but I do remember the answers to most of these questions off the top of my head and will get the rest when I get home.
When everything is working fine for the PowerBook, the resolution list shows a variety of interlaced resolutions ranging from 680 x 480 to 1024 x 768. There are about five or six options. The refresh rate options are PAL 50Hz or NTSC 60Hz.
As for how it identifies the TV when connected, I have to admit I don't remember, but I believe it just identifies it as a generic TV.
The Mac mini doesn't identify it at all. I can confirm this because I tried booting it without the monitor attached and then attaching it and I also booted it with the monitor attached. In all cases, the same options for resolution were shown (1024 x 768 and 800 x 600) and refresh rate is geyed out. To me, this indicates that it is not communicating with the display at all.
I think that adapter may well be broken as it's never been tested with another display so this is the argument I'm going to make when I go back to the Apple Store this evening!
I'll keep you posted on whether the new one works or not.
Please do let me know if you think there are any other tests I should run or not.
Cheers,
Phaedon

Print to windows attached printer

Hi!
I am facing a "small" problem here in my home lan. I have to computers connected. One is running Windows XP and has attached an Epson Stylous C60 printer. The other is running redhat 9 (2.4.8-20smp)
I have managed to make thw two boxes "talk" via samba.
$ rpm -q samba
samba-2.2.7a-7.9.0
I can read/write from one box to another without problem. The windows can see the linux through the lan and the linux can see the windous after mounting the share. But the thing I cannot do is print from linux to the windows attached printer.
First of all I checked if the printer is supported redhat and I found out that it is.
http://www.linuxprinting.org/show_p...pson-Stylus_C60
So this eliminates the obvious question: Can you print with this printer from linux in the first place?
I've read many things about how to print to windows, like
http://www.idevelopment.info/data/U...tLinuxSMB.shtml
http://www.redhat.com/docs/manuals/...mb-printer.html
as well as many stuff from google search But there is no way I can solve my problem. I follow the instructions but still I can't print
I also tried cups
$ rpm -q cups
cups-1.1.17-13
But there too I faced the same proble.
Can someone help me out here because I need that printer. I attach my smb.conf file. Any other information I will be standing by to submit.
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options (perhaps too
# many!) most of which are not shown in this example
# Any line which starts with a ; (semi-colon) or a # (hash)
# is a comment and is ignored. In this example we will use a #
# for commentry and a ; for parts of the config file that you
# may wish to enable
# NOTE: Whenever you modify this file you should run the command "testparm"
# to check that you have not made any basic syntactic errors.
#======================= Global Settings =====================================
[global]
# workgroup = NT-Domain-Name or Workgroup-Name
workgroup = mshome
# server string is the equivalent of the NT Description field
server string = samba server
# This option is important for security. It allows you to restrict
# connections to machines which are on your local network. The
# following example restricts access to two C class networks and
# the "loopback" interface. For more examples of the syntax see
# the smb.conf man page
; hosts allow = 192.168.1. 192.168.2. 127.
# if you want to automatically load your printer list rather
# than setting them up individually then you'll need this
printcap name = /etc/printcap
load printers = yes
# It should not be necessary to spell out the print system type unless
# yours is non-standard. Currently supported print systems include:
# bsd, sysv, plp, lprng, aix, hpux, qnx, cups
printing = cups
# Uncomment this if you want a guest account, you must add this to /etc/passwd
# otherwise the user "nobody" is used
; guest account = pcguest
# this tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba/%m.log
# Put a capping on the size of the log files (in Kb).
max log size = 0
# Security mode. Most people will want user level security. See
# security_level.txt for details.
# Use password server option only with security = server
# The argument list may include:
# password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name]
# or to auto-locate the domain controller/s
# password server = *
; password server = <NT-Server-Name>
# Password Level allows matching of _n_ characters of the password for
# all combinations of upper and lower case.
; password level = 8
; username level = 8
# You may wish to use password encryption. Please read
# ENCRYPTION.txt, Win95.txt and WinNT.txt in the Samba documentation.
# Do not enable this option unless you have read those documents
encrypt passwords = yes
smb passwd file = /etc/samba/smbpasswd
# The following is needed to keep smbclient from spouting spurious errors
# when Samba is built with support for SSL.
; ssl CA certFile = /usr/share/ssl/certs/ca-bundle.crt
# The following are needed to allow password changing from Windows to
# update the Linux system password also.
# NOTE: Use these with 'encrypt passwords' and 'smb passwd file' above.
# NOTE2: You do NOT need these to allow workstations to change only
# the encrypted SMB passwords. They allow the Unix password
# to be kept in sync with the SMB password.
unix password sync = Yes
passwd program = /usr/bin/passwd %u
passwd chat = *New*password* %nn *Retype*new*password* %nn *passwd:*all*authentication*tokens*updated*successfully*
# You can use PAM's password change control flag for Samba. If
# enabled, then PAM will be used for password changes when requested
# by an SMB client instead of the program listed in passwd program.
# It should be possible to enable this without changing your passwd
# chat parameter for most setups.
pam password change = yes
# Unix users can map to different SMB User names
; username map = /etc/samba/smbusers
# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
; include = /etc/samba/smb.conf.%m
# This parameter will control whether or not Samba should obey PAM's
# account and session management directives. The default behavior is
# to use PAM for clear text authentication only and to ignore any
# account or session management. Note that Samba always ignores PAM
# for authentication in the case of encrypt passwords = yes
obey pam restrictions = yes
# Most people will find that this option gives better performance.
# See speed.txt and the manual pages for details
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
# Configure Samba to use multiple interfaces
# If you have multiple network interfaces then you must list them
# here. See the man page for details.
; interfaces = 192.168.12.2/24 192.168.13.2/24
# Configure remote browse list synchronisation here
# request announcement to, or browse list sync from:
# a specific host or from / to a whole subnet (see below)
; remote browse sync = 192.168.3.25 192.168.5.255
# Cause this host to announce itself to local subnets here
; remote announce = 192.168.1.255 192.168.2.44
# Browser Control Options:
# set local master to no if you don't want Samba to become a master
# browser on your network. Otherwise the normal election rules apply
; local master = no
# OS Level determines the precedence of this server in master browser
# elections. The default value should be reasonable
; os level = 33
# Domain Master specifies Samba to be the Domain Master Browser. This
# allows Samba to collate browse lists between subnets. Don't use this
# if you already have a Windows NT domain controller doing this job
; domain master = yes
# Preferred Master causes Samba to force a local browser election on startup
# and gives it a slightly higher chance of winning the election
; preferred master = yes
# Enable this if you want Samba to be a domain logon server for
# Windows95 workstations.
; domain logons = yes
# if you enable domain logons then you may want a per-machine or
# per user logon script
# run a specific logon batch file per workstation (machine)
; logon script = %m.bat
# run a specific logon batch file per username
; logon script = %U.bat
# Where to store roving profiles (only for Win95 and WinNT)
# %L substitutes for this servers netbios name, %U is username
# You must uncomment the [Profiles] share below
; logon path = \%LProfiles%U
# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable it's WINS Server
; wins support = yes
# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
; wins server = w.x.y.z
# WINS Proxy - Tells Samba to answer name resolution queries on
# behalf of a non WINS capable client, for this to work there must be
# at least one WINS Server on the network. The default is NO.
; wins proxy = yes
# DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
# via DNS nslookups. The built-in default for versions 1.9.17 is yes,
# this has been changed in version 1.9.18 to no.
username map = /etc/samba/smbusers
guest ok = yes
guest account = axelman
dns proxy = no
# Case Preservation can be handy - system default is _no_
# NOTE: These can be set on a per share basis
; preserve case = no
; short preserve case = no
# Default case is normally upper case for all DOS files
; default case = lower
# Be very careful with case sensitivity - it can break things!
; case sensitive = no
#============================ Share Definitions ==============================
[homes]
comment = Home Directories
browseable = no
writeable = yes
valid users = %S
create mode = 0664
directory mode = 0775
# If you want users samba doesn't recognize to be mapped to a guest user
; map to guest = bad user
# Un-comment the following and create the netlogon directory for Domain Logons
; [netlogon]
; comment = Network Logon Service
; path = /usr/local/samba/lib/netlogon
; guest ok = yes
; writable = no
; share modes = no
# Un-comment the following to provide a specific roving profile share
# the default is to use the user's home directory
;[Profiles]
; path = /usr/local/samba/profiles
; browseable = no
; guest ok = yes
# NOTE: If you have a BSD-style print system there is no need to
# specifically define each individual printer
[printers]
comment = All Printers
path = /var/spool/samba
browseable = no
# Set public = yes to allow user 'guest account' to print
printable = yes
# This one is useful for people to share files
;[tmp]
; comment = Temporary file space
; path = /tmp/samba
; read only = no
; public = yes
# A publicly accessible directory, but read only, except for people in
# the "staff" group
;[public]
; comment = Public Stuff
; path = /home/samba
; public = yes
; writable = yes
; printable = no
; write list = @staff
# Other examples.
# A private printer, usable only by fred. Spool data will be placed in fred's
# home directory. Note that fred must have write access to the spool directory,
# wherever it is.
;[fredsprn]
; comment = Fred's Printer
; valid users = fred
; path = /home/fred
; printer = freds_printer
; public = no
; writable = no
; printable = yes
# A private directory, usable only by fred. Note that fred requires write
# access to the directory.
;[fredsdir]
; comment = Fred's Service
; path = /usr/somewhere/private
; valid users = fred
; public = no
; writable = yes
; printable = no
# a service which has a different directory for each machine that connects
# this allows you to tailor configurations to incoming machines. You could
# also use the %U option to tailor it by user name.
# The %m gets replaced with the machine name that is connecting.
;[pchome]
; comment = PC Directories
; path = /usr/local/pc/%m
; public = no
; writable = yes
# A publicly accessible directory, read/write to all users. Note that all files
# created in the directory by users will be owned by the default user, so
# any user with access can delete any other user's files. Obviously this
# directory must be writable by the default user. Another user could of course
# be specified, in which case all files would be owned by that user instead.
;[public]
; path = /usr/somewhere/else/public
; public = yes
; only guest = yes
; writable = yes
; printable = no
# The following two entries demonstrate how to share a directory so that two
# users can place files there that will be owned by the specific users. In this
# setup, the directory should be writable by both users and should have the
# sticky bit set on it to prevent abuse. Obviously this could be extended to
# as many users as required.
;[myshare]
; comment = Mary's and Fred's stuff
; path = /usr/somewhere/shared
; valid users = mary fred
; public = no
; writable = yes
; printable = no
; create mask = 0765
[axelman]
path = /home/axelman
writeable = yes
guest ok = yes
thanx to all
axelmang

This easy to follow procedure (5 web pages with screen shots) worked for MacBook Pro 10.6.8 via Wireless-N to Windows 7 Home Premium SP1 x64 using USB Cable to HP Officejet 7210 All-in-One. This configuration had worked with Windows XP.
http://macs.about.com/od/printersharing/ss/Printer-Sharing-Share-Your-Windows-7- Printer-With-Your-Mac.htm
Error messages encountered prior to using the above procedure:
authorization required
Backend returned status 2 (authentication required)
Cannot find server
Communication Failure: The computer is no longer able to communicate with your printer
cupsdAuthorize: pam_authenticate() returned 9
getaddrinfo: <windows printserver> nodename nor servname provided, or not known
Job held for authentication
On Hold (Authorization required)
pam_authenticate() returned 9 (authentication error)!
Printer Paused
Printer stopped due to backend errors
Session setup failed: NT_STATUS_INVALID_PARAMETER
snmpInk: Unknown host (<windows printserver>)
This computer seems to have a working Internet connection. but we cannot find "<windows printserver>" You may have typed the address incorrectly.
Tree connect failed (NT_STATUS_ACCESS_DENIED)
Unable to locate printer
Unable to locate printer Unknown host
Unknown host

Connect a Professional CRT monitor to iMac

Is there any way to connect a Professional CRT monitor to an iMac? I need to color correct my short film. If a regular monitor won't work what kinds will for accurate color grading?

I'm not sure what a professional CRT is compare to other CRT displays, but if it uses a VGA connection, all you need is a mini-DVI to VGA adapter.
http://store.apple.com/us/product/M9320G/A
I have a 21-inch flat screen CRT attached to my iMac at 1600x1200 resolution. It can go to 1792x1344, but that's a bit too small with the text, and the refresh rate drops to 60 Hz instead of 75 Hz at 1600x1200. You can, of course, choose all the standard resolutions down to 640x480.

Connecting a 15" MBP to an arcade cabinet CRT

Hello all,
I'm interested in hooking up my 15" MBP to an arcade cabinet's CRT display. The CRT takes VGA input and requires a 15 KHz horizontal refresh rate. I'll be using the Apple DVI -> VGA adapter that came with my MBP.
I am somewhat worried about damaging the CRT by outputting an incompatible signal. Thus, my questions:
1. Is my MBP capable of outputting a 15 KHz horizontal refresh rate?
2. If yes, what is the best procedure (step-by-step) for attaching and configuring an external monitor of this nature?
Thanks!
2.33 MBP 15" | 2 GB RAM | 256 MB VRAM Mac OS X (10.4.9)

As I recall the old TV standard was 15.750 kHz. I'm sure a MBP can output this because that is what it would send to a conventional TV when using the DVI to Video adapter.
Modern Macs and displays use a plug-and-play architecture based on a standard called DDC. This relies on data being embedded in a ROM inside the display that gets read by the Mac. I doubt the monitor in the arcade cabinet will have this embedded data, so that is something that will need to be overcome. The Mac may not even detect that an external display has been attached to the DVI port without this data.
You could try plugging it into the Mac's DVI port but leaving the power off to the arcade. See if the Mac detects it in a powered off state. If it does, then hopefully the timing you need (640 x 480 NTSC) will be an option available under Display Preferences. If it is, you can pre-select it before applying power to the arcade monitor.
If the arcade monitor is detected in a powered off state but the required timing is not available in the list of available timings, then you could use a third-party utility like SwitchRes X which will have a more extensive list of pre-installed standard timings.
If the arcade monitor isn't properly sensed by the Mac in all cases or at all, there is a danger that it might output a timing other than the one the monitor is intended to run from. That could cause an unsafe condition for the monitor's high voltage circuits. If you are really serious about getting this to work, you could invest in a Gefen DVI Detective that was factory configured with the custom EDID the arcade monitor requires. This would help ensure the right timing is always present on the port.
http://www.gefen.com/kvm/product.jsp?prod_id=1378
It's not all that easy, is it. You need to really want to do it to go through the trouble.

G4 iMac thinks an external VGA monitor is attached.

My first Mac is the 17 inch G4 iMac. I'm fairly sentimental about this machine.
The iMac running 10.4.11 thinks that there is an external VGA monitor attached to it. The iMac also assigns this "ghost VGA monitor" as the main screen. Every few minutes the screen will flicker from blue, to black and to white before resetting itself. This flickering will continue at random intervals thereafter. Under the Display settings there is no option to turn off mirroring or to arrange the screens.
Years ago I used to use one of those honking CRT Studio Displays. That thing died a long time ago though. Is there some old preferences file that could be screwing with my iMac?
I have also attempted to zap the NVRAM + PRAM. It did not solve the issue.
Any suggestions would be greatly appreciated. Thanks!

I don't think there is a way to undo the firmware update, until the installer from the developer has an uninstall option, or there was an uninstall program included with the install program. You can download it again and see.
However, now that you have it working partially (it's acting like you have another display attached), try resetting the PRAM again. You did that as a byproduct of resetting the PMU, but things were not working +almost correctly+ at that time. This is the reset PRAM procedure.
http://support.apple.com/kb/HT1379
That might help, because some display settings are stored in PRAM, so the one that indicates a second display could be corrupted.
Also, when I changed display settings on my Mac (such as resolution or arrangement), these are the files I saw getting updated.
<home folder>/Library/Preferences/ByHost/com.apple.windowserver...plist
<home folder>/Library/Preferences/ByHost/com.apple.preference.displays...plist
<volume root>/Library/Preferences/com.apple.windowserver.plist
(There is a random-looking alphanumeric string where I put the dots - probably different for each system.)
So you might try dragging those preference files to the Desktop to let the system create new ones. Then restart. Note: The above files are for Leopard; could be different if you are using Tiger.

IMac crt dark

The screen of my G3 400mhz iMac DV SE is now very dark, all settings are at their brightest in sys pref. It is viewable for text on white background and for most applications, it is unviewable for photos and dark background websites with low contrast text. It has been like this for sometime and once or twice after a restart it has been fully bright. I upgraded to the latest OSX in 12/05 but I don't remember if the problem started then or was prior to it. I have been upgrading since I got the machine and my firmware should be good. Other than this the computer works great. As peripherals I have a fire wire external hard drive,cd burner and voip modem and cable modem attached. My question, is this how crt's burnout or could it be a software/video card issue?
Appreciate any suggestions!

Hmm,
After some searching all I can find is this document. You've already done all the steps apart from taking it in to Apple.
I'd be tempted to hit the reset button on the side of the iMac.
I can only find this image right now - it's the "Bouton de réinitialisation".
Given the thousands of volts involved with CRTs I would not advise cracking open the iMac; unless you feel very confident.
kind regards
mrtotes

Sending plain request to web service using receiver sender adapter and PI and expecting as attachment as response

Hi
In my scenario,we are sending plain request to web service using receiver sender adapter and PI will receive response as excel attachment. What are standard module required to achieve this and sequence? or checking Keep attachment box will help us to achieve this?
is it possible to receive excel sheet as attachment from receiver soap adapter ?
Thanks in Advance

Hi,
This issue might be due to the invalid .pem certificate file.
Make sure to include the beginning and end tags on each certificate.
The result should look like this:
-----BEGIN CERTIFICATE-----
(Your Primary SSL certificate: your_domain_name.crt)
-----END CERTIFICATE-----
-----BEGIN CERTIFICATE-----
(Your Intermediate certificate: DigiCertCA.crt)
-----END CERTIFICATE-----
For more detailed information, you could refer to:
https://www.digicert.com/ssl-support/pem-ssl-creation.htm
Regards

LCD monitor recognized by X as CRT

I'm buy new LCD monitor and connect it to D-SUB on my GeForce4 MX 440.
But X and Nvidia drivers recognize the monitor as CRT.
I don't have DVI input on my video card. And only one monitor connected to computer.
I'm try to define in xorg.conf
Section "Device"
Identifier "Card0"
Driver "nvidia"
VendorName "nVidia Corporation"
BoardName "NV18 [GeForce4 MX 440 AGP 8x]"
BusID "PCI:1:0:0"
Option "ConnectedMonitor" "DFP"
EndSection
But after that I see in the /var/log/Xorg.0.log
(II) NVIDIA(0): Using ConnectedMonitor string "DFP-0"
(WW) NVIDIA(0): Inappropriate ConnectedMonitor string.
(II) NVIDIA(0): Connected display device(s): CRT-0
(--) NVIDIA(0): CRT-0: maximum pixel clock: 350 MHz
How can I force LCD monitor detection?

Mythoz wrote:
/usr/share/doc/NVIDIA_GLX-1.0/README.txt:
Option "ConnectedMonitor" "string"
NOTE: anything attached to a 15 pin VGA connector is regarded by the
driver as a CRT. "DFP" should only be used to refer to flatpanels
connected via a DVI port.
Thenk you.
I have no way to right recognize LCD monitor connected via D-SUB.

Attaching a CRT

Similar Messages

Maybe you are looking for