Possible Driver Problem in ODPNET9202102

Hi,
got following problem with above ODP Driver:
In out Application we open a connection to the Oracle database, read data into a ado.net dataset, close connection. Before storing data back, again connection is open, data saved an connection again closed.
We get the following strange behaviour:
Reading the dataset and adding a new datarow to the table (dataset conatins only one table). Storing the dataset. reading it back again in the application and changing an exiting record. The next save (actually the Update of the Dataadapter on the modified Row in the dataset) comes up with the following (I translated the message from german to english) message:
Generation of dynamic SQL not successful. No Information on Keys found.
After that, ending the application results in NullReferenceException.
Same code works on other driver (for example OLEDB on Access).
What wrong?
Thanks for your help.

The reason I asked for a test case was to verify the fix in 9204000. Since you have verified the fix yourself, you don't need to send the test case.

Similar Messages

  • AT-MIO-16E-10 Read encoders problem (a possible driver problem ?)

    Hi there! I have AT-MIO-16E-10 board and i have a problem with reading the "values" from an incremental encoder.Here it's the description of the problem : I have the encoder conected via a mechanism formed by a belt and a pulley (the pulley it is connected directly to the encoder shaft) and this mechanism it is moved by a dc motor which it's also conected to the belt by an identical pulley mounted on the dc motor shaft.The motor drives a cart (by this mechanism formed by pulley-belt) on a track which has 1200 mm length.Now here comes the problem : The resolution of the encoder i use to measure the position it's 10000 ppr. The diameter of the puley it's 30.56 mm. Now the pulses given by the encoder during the full track (the total counts measured within the total length of the track i.e 1200mm) are measured with an universal counter (a hardware device) and with an aplication program (which it is attached bellow).The number of pulses for the total lenght of the track it's around 125000 (plus minus maxium 10 pulses) for the universal counter device (the hardware device) and around 128000 for the aplication program (plus minus 100 pulses).Now if we do a simple mathematical calculation we shall observe the following : if the puley has the diameter of 30.56 mm that gives us a linear length (the length of the circle) of PI*diameter i.e around 96.00424 mm (3.1415*30.56).If the total length of the track it's 1200mm that means the puley makes 1200/96.00424 rotations i.e. around 12.499 rotations and if the encoder give us 10000 ppr that means 124990 pulses for the total length of the track (for 1200mm) which it's extremely closed to the value of 125000 pulses provided by the universal counter (the hardware device) and quite far from 128000 pulses provided by the aplications program attached bellow.If we supose that the corect number of pulses it's 128000 that means the pulley should turn 12.8 times comparing with 12.5 times on the total length of the track which it's not true! (i could see with my own eyes that the pulley rotates under 12.5 rotations during the total length of the track). So after my opinion there is something wrong with the software (the program it is downloaded from zone.ni.com).I'm using AT-MIO-16E-10 hardware device,with LV6.1 (and real-time version),NI-DAQ 6.9.3 driver on XP1600+ processor,with Windows XP operating system.If any of NI aplication engineers see this please reply as quick as possible.Thank you very much for reading this and i'll be waiting for your answers as quick as possible.Best regards,Michael.
    Attachments:
    Quad._Encoder_with_E-series_(STC).VI ‏50 KB

    >by Michael Antonios
    The number of pulses for the total lenght of the track it's around 125000 (plus minus maxium 10 pulses) for the universal counter device (the hardware device) and around 128000 for the aplication program (plus minus 100 pulses).
    >mross
    IF the signal from the encoder is correct (proper voltages High and Low, and noise free), THEN the count will be correct.
    This is gauranteed.
    You probably have a noise problem ( I speak from experience). The counter is expecting TTL logic. In my experience, if the low of the encoder signal has noise exceeding 0.8V, the counter will falsely count the noise.
    The simplest solution could be to trigger on the falling edges of the encoder signal. There is more "headroom" coming dow
    n with TTL. If your high signal is running 5V, the undefined range starts at 2.4V (which is pretty much when the counter will start counting). This gives you the ability to reject 2.6V of noise. On the rising edge, you may have a 0.3V low and only 0.5V of noise rejection.
    The other option is to clean up the noise. Get an osilloscope and start looking. Fix any bad grounding and wiring practices. Turn off any noisy equipment. There are ways to buffer the counter input so that the encoder signal is a differential signal. Optocouplers and schmitt triggers can clean up the encoder signals. Sometimes the encoder needs to drive some current to be less noisy. A fast Line Receiver can clean up rounded off encoder pulses (see US Digital - $16).
    Good luck,
    mike

  • A205-S5000 won't boot. Says possible hard drive problem

    Laptop won't boot and says possible hard drive problem. Need to recover
    personal reports and data, so thinking of removing the drive and using an enclosure
    so the data, if still good, can be extracted from the drive by another computer. Question
    is, will I be able to create the restore cd's from the hard drive if the hard drive is not the
    boot drive ie; attached to a 2nd computer via usb and enclosure. 
    If it's not possible, I can try to create cd's from a different model laptop (toshiba), same vista os but
    what about the product key?  I will try to reinstall the bad drive and try a reboot to recovery mode but
    I doubt that is going to work or complete. Idea was to get a new drive and try to install recovery disks.

    Satellite A205-S5000
    Recovery discs must be from an identical model. If you can't burn them from that computer, best to order them
       Order Toshiba Recovery Media 
    The restored Windows is pre-activated.
    -Jerry

  • Yoga 13 Graphics driver problem -BSOD

    I am having a problem getting this frequent "graphic driver stopped responding..." message and a "video_scheduler.." BSOD after that. Something like this:
    Steps I did:
    Did OKR. Clean driver. Lenovo driver. Windows update intel Driver. Latest Intel HD 4000 from their site. The BIOS version is upto date but I reinstalled again.NO luck. .I tried both Win 8 and 8.1 here. .. I tried all these possibilities.. 
    Did clean windows install from a non-lenovo windows 8 image. Wiped SSD. Windows was fresh, clean and no bloatware. No Luck.  Updatet to 8.1 .. did all possibilities again.. no luck. 
    I called Lenovo Tech. They remote to the laptop and what he did is uninstall all graphics driver and use windows generic driver. He stopped auto windows update (since windows updates the driver). There's no error, but the laptop performance is horribly slow. Scrolling long PDF and websites is wavy and the HDMI port is useless.
    Lenovos solution is unacceptable. The laptop is bassically useless. 
    Are you guys experiencing the same thing too? Do you guys know a solution. I really like the laptop but it is unusable.
    BTW, I bought this laptop ~3 weeks as scratch and dent at their lenovo website. I wonder if there is a hardware problem for this.
    Also, the wifi sucks.. sigh

    Here's the analysis:
    System Information (local)
    computer name: JCXLENOVO
    windows version: Windows 8.1 , 6.2, build: 9200
    windows dir: C:\WINDOWS
    Hardware: 20175, LENOVO, INVALID
    CPU: GenuineIntel Intel(R) Core(TM) i5-3337U CPU @ 1.80GHz Intel586, level: 6
    4 logical processors, active mask: 15
    RAM: 4171603968 total
    VM: 2147352576, free: 1873526784
    Crash Dump Analysis
    Crash dump directory: C:\WINDOWS\Minidump
    Crash dumps are enabled on your computer.
    On Thu 3/20/2014 4:55:37 AM GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\031914-6000-01.dmp
    This was probably caused by the following module: watchdog.sys (watchdog+0x39CA)
    Bugcheck code: 0x119 (0x1, 0x0, 0xA60, 0xFFFFE000023D7010)
    Error: VIDEO_SCHEDULER_INTERNAL_ERROR
    file path: C:\WINDOWS\system32\drivers\watchdog.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Watchdog Driver
    Bug check description: This indicates that the video scheduler has detected a fatal violation.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
    On Thu 3/20/2014 4:55:37 AM GMT your computer crashed
    crash dump file: C:\WINDOWS\memory.dmp
    This was probably caused by the following module: igdkmd64.sys (igdkmd64!hybDriverEntry+0xB861A)
    Bugcheck code: 0x119 (0x1, 0x0, 0xA60, 0xFFFFE000023D7010)
    Error: VIDEO_SCHEDULER_INTERNAL_ERROR
    file path: C:\WINDOWS\system32\drivers\igdkmd64.sys
    product: Intel HD Graphics Drivers for Windows 8(R)
    company: Intel Corporation
    description: Intel Graphics Kernel Mode Driver
    Bug check description: This indicates that the video scheduler has detected a fatal violation.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: igdkmd64.sys (Intel Graphics Kernel Mode Driver, Intel Corporation).
    Google query: Intel Corporation VIDEO_SCHEDULER_INTERNAL_ERROR
    On Thu 3/20/2014 4:51:59 AM GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\031914-5593-01.dmp
    This was probably caused by the following module: watchdog.sys (watchdog+0x39CA)
    Bugcheck code: 0x119 (0x1, 0x0, 0x45F5, 0xFFFFE000023043C0)
    Error: VIDEO_SCHEDULER_INTERNAL_ERROR
    file path: C:\WINDOWS\system32\drivers\watchdog.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Watchdog Driver
    Bug check description: This indicates that the video scheduler has detected a fatal violation.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
    On Wed 3/19/2014 4:46:45 AM GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\031814-3859-01.dmp
    This was probably caused by the following module: watchdog.sys (watchdog+0x39CA)
    Bugcheck code: 0x119 (0x1, 0x0, 0x1A4F, 0xFFFFE00000225010)
    Error: VIDEO_SCHEDULER_INTERNAL_ERROR
    file path: C:\WINDOWS\system32\drivers\watchdog.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Watchdog Driver
    Bug check description: This indicates that the video scheduler has detected a fatal violation.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
    On Wed 3/19/2014 4:36:24 AM GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\031814-4218-01.dmp
    This was probably caused by the following module: watchdog.sys (watchdog+0x39CA)
    Bugcheck code: 0x119 (0x1, 0x0, 0x2BCA, 0xFFFFE000023F5010)
    Error: VIDEO_SCHEDULER_INTERNAL_ERROR
    file path: C:\WINDOWS\system32\drivers\watchdog.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Watchdog Driver
    Bug check description: This indicates that the video scheduler has detected a fatal violation.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
    On Wed 3/19/2014 4:28:45 AM GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\031814-3921-01.dmp
    This was probably caused by the following module: watchdog.sys (watchdog+0x39CA)
    Bugcheck code: 0x119 (0x1, 0x0, 0x1D35, 0xFFFFE00002255540)
    Error: VIDEO_SCHEDULER_INTERNAL_ERROR
    file path: C:\WINDOWS\system32\drivers\watchdog.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Watchdog Driver
    Bug check description: This indicates that the video scheduler has detected a fatal violation.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
    On Wed 3/19/2014 3:25:52 AM GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\031814-4234-01.dmp
    This was probably caused by the following module: watchdog.sys (watchdog+0x39CA)
    Bugcheck code: 0x119 (0x1, 0x0, 0x1A96, 0xFFFFE00002380010)
    Error: VIDEO_SCHEDULER_INTERNAL_ERROR
    file path: C:\WINDOWS\system32\drivers\watchdog.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Watchdog Driver
    Bug check description: This indicates that the video scheduler has detected a fatal violation.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
    On Tue 3/18/2014 7:00:40 PM GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\031814-4046-01.dmp
    This was probably caused by the following module: watchdog.sys (watchdog+0x39CA)
    Bugcheck code: 0x119 (0x1, 0x2E17, 0x29E, 0xFFFFE00000255010)
    Error: VIDEO_SCHEDULER_INTERNAL_ERROR
    file path: C:\WINDOWS\system32\drivers\watchdog.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Watchdog Driver
    Bug check description: This indicates that the video scheduler has detected a fatal violation.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
    On Thu 3/6/2014 9:07:27 AM GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\030614-3906-01.dmp
    This was probably caused by the following module: watchdog.sys (watchdog+0x39CA)
    Bugcheck code: 0x119 (0x1, 0x0, 0x2B6B, 0xFFFFE00001C90010)
    Error: VIDEO_SCHEDULER_INTERNAL_ERROR
    file path: C:\WINDOWS\system32\drivers\watchdog.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Watchdog Driver
    Bug check description: This indicates that the video scheduler has detected a fatal violation.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
    On Thu 3/6/2014 7:21:39 AM GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\030514-8468-01.dmp
    This was probably caused by the following module: Unknown (0xFFFFF8001F9D9CA0)
    Bugcheck code: 0x119 (0x1, 0x0, 0x448, 0xFFFFE00001C2D2A0)
    Error: VIDEO_SCHEDULER_INTERNAL_ERROR
    Bug check description: This indicates that the video scheduler has detected a fatal violation.
    A third party driver was identified as the probable root cause of this system error.
    Google query: VIDEO_SCHEDULER_INTERNAL_ERROR
    Conclusion
    16 crash dumps have been found and analyzed. Only 10 are included in this report. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
    igdkmd64.sys (Intel Graphics Kernel Mode Driver, Intel Corporation)
    If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.

  • Windows 7 - HP Laserjet 8500 print driver problem

    I have tried everything imaginable to correct this HP 8500n print driver problem with no success, please help!
    I cannot correct or get rid of a reoccurring “Incompatible Print Settings” error dialog box message that repeatedly states that “There are one or more conflicting settings. One of the settings is: Output Bin: Mailbox 1, Accessory Output Bin: Not Installed”. The radio button options are “Restore my previous settings or Keep this setting, and I will change it later”. This same dialog message repeats 13 times for all the other various conflicts each time you click on printer properties to change to 2 sided printing or any other printer settings. This printer does not have any of these features attached or set into it.
    I am a volunteer that manages a number of computers on our small church LAN, 2 computers operating on MS XP-SP3, 2 on MS Windows 7 Home Premium and my 2 problem computers that came pre-installed with Vista Home Premium of which I have performed an HP OEM upgrade to Window 7.
    I have isolated this print driver problem to the Vista operating system and even when computers are upgraded to Windows 7 does not correct this driver error. I have also tried every possible print driver variant of the HP 8500, HP8550, PCL, PS to include the Microsoft versus HP versions with no success. In each case I get this error yet neither of the XP computers or the computers that had Windows 7 as a original operating system have no problems with their print drivers for this printer.
    Yes, I have repeatedly searched and upgraded the operating system and print drivers. In desperation I have even tried to find the correctly behaving Windows 7 print driver and transfer it to these Vista upgraded to Windows 7 machines. However I could not isolate the driver location.
    The only thing I can conclude is that this errant HP print driver was resident within Vista and remains resident even after a HP OEM Windows 7 upgrade. Additionally, all of these computers are configured to access this printer via its static IP address on the network.  The XP computers are 32 bit, all of the Vista upgraded to Win 7 and OEM Win 7 computers are 64 bit machines all with respective OS. 
    Can anyone please help me correct this problem?

    Hi, 
    Unfortunately I can't see your uploaded image yet as it is awaiting approval from HP.
    From what I can see you are correct that HP does supply drivers for this printer and that the drivers for your printer are already included with Windows 7.  On the machines affected, try the procedure below to see if it helps at all
    Next download revo uninstaller on the link below and install it.
    http://www.revouninstaller.com/download-freeware-version.php
    Disconnect the printer from the PC.
    Run Revo and see if it finds any  HP Printer Software installed.  If it does, right click the software icon and select uninstall.  During the process you may be asked to delete registry entries.  If you are, just select all and click delete.  Do the same for any left over files and folders.  Once completed, reboot the PC.
    Re-connect your printer to the PC and follow the guide below.
    http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?&objectID=c02536257
    If this helps you will need to repeat the process on each of the affected machines.
    Best wishes,
    DP-K
    ****Click the White thumb to say thanks****
    ****Please mark Accept As Solution if it solves your problem****
    ****I don't work for HP****
    Microsoft MVP - Windows Experience

  • Premiere Pro 2.0 and Windows 7 - Direct Sound Input soundcard driver problem

    My XP machine crashed, I reinstalled Premiere Pro 2.0 with Windows 7, and I got the following error: 'The Currently installed soundcard driver does not support Direct Sound Input. Recording audio is not possible.' The soundcard drivers are updated. Any ideas? Here's what I have: AMD Phenom II X4 965 Processor  3.40 GHz 8 GB, 64 bit. Thank you for looking.

    Thanks! Though I upgraded to solve the problem, this is good to know.
    Bob
    Date: Wed, 9 Nov 2011 04:45:42 -0700
    From: [email protected]
    To: [email protected]
    Subject: Premiere Pro 2.0 and Windows 7 - Direct Sound Input soundcard driver problem
    Re: Premiere Pro 2.0 and Windows 7 - Direct Sound Input soundcard driver problem created by Steve-Italy in Premiere Pro CS4 & Earlier - View the full discussion
    VERY VERY VERY EASY (now, when I solved the problem, not before...!!!)
    Insert Micropone or any jack in Micropone Input or Aux Input, on your sound card or motherboard !
    AND NOW YOU CAN USE PREMIERE PRO 2.0
    Enjoy
    Steve - Italy
    Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/4015730#4015730
    To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/4015730#4015730. In the Actions box on the right, click the Stop Email Notifications link.
    Start a new discussion in Premiere Pro CS4 & Earlier by email or at Adobe Forums
    For more information about maintaining your forum email notifications please go to http://forums.adobe.com/message/2936746#2936746.

  • Yosemite won't install due to a "S.M.A.R.T. drive problem that can't be repaired."

    After downloading Yosemite successfully, it won't install due to a "S.M.A.R.T. drive problem that can't be repaired."  It says to back up as much as possible and replace the drive.  Everything works flawlessly with Mavericks.  What gives??

    If you are getting a S.M.A.R.T. error then you should be more worried about losing everything on your drive then about upgrading your Mac OS.  Regardless of if you are running Mac OS, Linux, or Windows, you should never just disregard such a drive error.  S.M.A.R.T. is designed to give you a warning that your drive is statistically having far more errors than normal and should be backed up immediately and typically replaced.
    In your case, it's likely a coincidence that your drive is failing at the time you are attempting to upgrade to Yosemite.  You should stop what you are doing, backup your drive (if you don't already have the backups that you should prior to any OS upgrade), and replace the hard drive prior to moving forward.
    To make it clear, your hard drive is likely going to fail soon and you may lose everything on it at any moment.  This failure has nothing to do with Yosemite or any Mac OS.  All hard drives fail at some point.  Hopefully this S.M.A.R.T. notice has given you the opportunity to solve a major problem before it gets worse.

  • Macbook air flash drive problem

    my air mid 2012 has flash drive problem cant update and theres written apple would replace it free of charge but theres no official service center in my country what to do?Is it possible that they could send me flash drive or smthing like that

    Apple Authorized Service Providers
    https://locate.apple.com/country
    Best.

  • PhotoSmart Premium C309a driver problem in Win10 at double side printing

    My problem is as follows: I created a catalog in MS Publisher 2013 for A4 paper format with 2 page per paper. I selected booklet side-fold type and double side printing. MS Publisher prepared all pages in correct way. I even created PDF versuions of such pages. But each time when I print pages, the printer keeps make them smaller (I think it scale them for Letter format) despuite the fact I changes in printer preferences A4as default paper source, all documents are in A4 format etc. As result, the printed pages are shifter from the center page on the left side, which is ok for one side printing but cannot work for doyuble side printing as shift is in different directions for result paper. Additionally, I cannot any more print on DVD or CD surfaces as the driver doesn't support sauch a feature. Please let me know how I can replace the native Windows 10 driver with the one for Windows 8.1? Or is there any other solutions except using another OS? Thx, Vlad.

    Hi , Welcome to the HP Forums! I noticed that your HP PhotoSmart Premium C309a is having a driver problem in Windows 10 when printing double sided. I am happy to help!  According to this guide, How to Use the 2-Sided Feature, it looks to me as if the double sided printing feature is only available to use with regular plain white paper. (Letter sized), which could be why the printer is scaling the size to letter.  You could possibly try using an alternate driver, by going to this post, How to Assign Alternate Print Drivers in Different Versions of Windows, by , and follow the steps for Windows 8, as they will work on Windows 10. Then you could attempt a custom size print. But as mentioned previously, I am positive that the 2-sided feature for this printer is for Letter sized paper only, and cannot guarantee this will work.  Hope this answers your question, and thank you for posting!  “Please click the Thumbs up icon below to thank me for responding.”

  • Combo drive problem on Pismo

    My Pismo has a Sony CRX820E combo drive, and quite often, while the computer is up and running, the drive decides not to open and won't work until I restart the machine. This can be a pain if I get something done and want to burn it to disc - to put the disc in and get the drive to respond I need to restart.
    Of course, I can `open' the drawer with a paperclip, but the drive won't work until I restart. When it works, it's all fine!
    Is it just a matter of resetting something?
    I've checked for possible drive driver updates but I think everything is in order there.

    Alex,
    Welcome to the Discussions.
    If this behavior is intermittent, I would think it is a hardware problem.
    Can you return functionality to the drive by removing the optical drive, then reinserting it while the 'book is running? These media bay devices are hot-swappable.
    Or can you return functionality by sleeping the 'book, then waking?
    I cannot recall if the 820E needs the "solder-fix" for full functionality. Will the drive boot a CD by pressing the 'c' key? Does the powerbook freeze when waking from sleep? These are two symptoms of an optical drive that is set to slave or cable-select.

  • Hard drive problem...... Please Help

    Hard drive problems
    I am sure it is due to my error or mistake but I received a new Maxtor III touch as a replacement for my failed drive yesterday after connecting it I went to Maxtor one touch manager software that came with it and the drive did not appear in the window so then I opened disk utilities and copied my notebook hard drive over to the Maxtor ran permissions on each drive and then closed down my system ! today when I opened my Powerbook with the Maxtor on it gave me the grey screen 2x so I disconnected the Maxtor ran permissions again and everything was fine until i power up the Maxtor and Grey screen again! Help How do I fix this?????

    Maxtor one touch III firewire 800 its connected to my Titanium G$ Powerbook I am beginning to think its just another drive failure

  • Computer is balky random freezes across apps. Two hard drive cleans later (their scan reveals no hard drive problems) photo shop won't work at all, magic touch mouse inoperable and their diagnoses is corrupted data? Anybody heard of this?

    Computer is balky random freezes across apps. Two hard drive cleans later (their scan reveals no hard drive problems) photo shop won't work at all, magic touch mouse inoperable and their diagnoses is corrupted data? Anybody heard of this?

    Well, yes, data does get corrupted sometimes.
    The trick is finding what data.
    By 'cleaned' are you therefor meaning that the drive has been erased and the system re-installed?
    Because that's the quickest way to deal with such a situation.
    Back up the system first of course,
    Add back 3rd party apps one at a time in case one of them is causing the problem.

  • Lenovo T400 screen goes dark issue, some video driver problem

    Lenovo:
    Motherboard:
    CPU Type: Mobile DualCore Intel Core 2 Duo P8600, 2400 MHz (9 x 267)
    Motherboard Chipset:  Intel Cantiga GM45
    System Memory: 1992 MB (DDR3 SDRAM)
    BIOS Type: Phoenix (08/19/08)
    Display:
    Video Adapter: Mobile Intel(R) 4 Series Express Chipset Family 
    Video Adapter: Mobile Intel(R) 4 Series Express Chipset Family 
    3D Accelerator: ATI Mobility Radeon HD 3470 
    Problem/Issue:
    Driver problem appeard after upgrading from XP to Windows 7.
    From the Device Manager I saw that ATI Mobility Radeon HD 3470 was not working properly and
    a) I did the "update driver software." After restart the screen light was darker than usual. (This was usual if I was working from battery but I was plugged in this time. ) 
    As I'm not the best with computers I thought my drivers might be in conflict and to prevent serious damages, I just
    b) disabled ATI Mobility Radeon HD 3470 from device manager. 
    This actually resolved the dark screen problem.
    c) then I went to Lenovo support site: http://support.lenovo.com/en_US/research/hints-or-tips/detail.page?&LegacyDocID=MIGR-72858
    downloaded newest drivers for ATI Mobility Radeon HD 3400 (Switchable Graphics Driver)
    and Intel 4500MHD (Intel GM45 Express Chip)
    For some reason while installine the: Intel GM45 Display Driver (version 8.15.10.2302) gives me error:
    "This Computer Does not meet the minimum requirements for installing the software"
    Also some problem appeard when installing the new downloaded version:
    ThinkPad Switchable Graphics Driver  (version 8.792.5-110424b-119200C)
    d) so I went back to device manager and made an update to ATI Mobility Radeon  from there. 
    Well, I got it working, but the screen went dark again. When I disable the driver it goes back to normal
    brightness and when I enable it again, it stays normal.
    I'll try to restart and see what happens

    We had the excat same issue.
    I could get the picuture back pressing the power button until it went to sleep and then wake it up again.
    After the I went to device manager to delete all display drivers both Intel and ATI and then reboot.
    doing the reboot windows found some drivers it could use.
    I then installed the switchable driver from lenovo.
    Now windows device manger report two display drivers:
    1)
    ATI Mobility Radeon HD 3400 Series, Version 8.792.5.2000, Driver manufacturer ATI Technologies Inc
    2)
    Mobile Intel(R) 4 Series Express Chipset Family, Version, Version 8.792.5.2000, Driver manufacturer ATI Technologies Inc
    So it seams the switchable ATI driver take over the Intel card and the Intel driver is not needed.
    At least the problem is solved for us.
    Regards Anders

  • I was trying to sync my 120GB iPod Classic earlier and it said it couldn't sync as the iPod disk could not be "read" or "written to". I now can't get anything onto my iPod, and I was wondering if it is a hard drive problem? Any help appreciated. Thanks.

    I was trying to sync my 120GB iPod Classic earlier, and it said it couldn't sync as the iPod disk could not be "read" or "written to." I now can't get anything onto my iPod, and I was wondering if it is a hard drive problem? Any help appreciated. Thanks.

    Did you go into iTunes to change the location of your media files? if not you will need to go into iTunes and click on preference and select the advance tab then click the iTunes Media folder location.  Select the location of your on external hard drive. 

  • HP Color LaserJet 5550 and Tiger (10.4.11) Driver Problem

    I have recently acquired a Color LaserJet 5550hdn. I have updated all drivers and firmware available from the HP Website (Printer Driver, 5550 firmware and Jetdirect 610n firmware). The printer has been factory reset/cold reset etc. to purge any previous custom settings. I am using a PowerMac G4 Quicksilver (933mhz) and Mac OS X Tiger (10.4.11). I have made some test prints from both Preview and iPhoto and all have been dark and muddy with respect to colors. I have printed the same images from my wife's PC with HP's PCL 6 Driver for Windows XP and achieve satisfactory results with respect to color (that is to say, without fooling with any color settings in the driver, the image is at least within 10% of the color gamut compared to the screen image). Setting up the printer with the HP Postscript Driver for XP yields similar results as the Mac, dark and muddy colors. So is this a problem with the HP Postscript Driver? Is this a Mac OS X Tiger problem? Do users have color problems with the printer running the Leopard driver? 
    I previously owned a HP Color LaserJet 8550 (utilizing the same HP Driver for Mac OS X that the 5550 uses) and had default images (no fooling with any color settings in the driver) that were acceptable, again within 10% or less of the screen image color gamut.
    I have also downloaded HP's ICC color profiles (CMYK and sRGB) and put them in library/printers/hp/profiles.
    With respect to the driver itself, there are two areas in the print dialogue box which seem to have a bearing on color. One is Colorsync and the other is Color Options. Colorsync has two choices ('Standard' and 'In Printer') and I chose 'In Printer' to I assume bypass any Colorsync Conversion. When 'Standard' is chosen the print summary shows the HP Color LaserJet CMYK profile being used. There seems to be no way of changing the default setting in the Colorsync Utility to HP Color LaserJet sRGB. Not sure if it matters as the output for both 'Standard' and 'In Printer' seem to yield the same results. The options under 'Color Options" in the driver under the 'Show Advanced Options' have choices (Basic, Text, Graphics, Photographs, Advanced) and I have played with these to some extent. Although they seem to have some effect on the image, the print is still dark and muddy with respect to colors.
    On a final note I have tried a 'GutenPrint' driver to see if it would yield different results.....there was not one for the 5550 so I used a driver for the Color LaserJet 5500......it would only print in grayscale....the resulting image did not look very promising even if it had printed in color.
    Insights on any of the above from the community here would be most helpful!
    Thanks,
    -Ray 

    This is an update to my own post above. I downloaded the Mac OS 9 driver (yes OS 9!, but the QuickSilver is Dual Boot) for the Color LaerJet 5550 and printed (no changes to any of the driver settings) the same image (photo) as I used in Mac OS X. The image was still dark but not as poor from Mac OS X 10.4.11 (Tiger). Although I prefer not to use color management, I used the Colorsync tab in the driver and chose to match to Colorsync with a generic sRGB output profile (no other settings were changed in the HP color options tab). The resulting image was +/- 5% within the color gamut of the screen image (yeah!!!) In Tiger the options under the Colorsync tab in the driver are 'Standard' or 'In Device' and regardless of the choice, the print result is the same, very dark and muted colors. There is no option for sRGB and if set to 'Standard' the print summary always shows a CMYK profile being utilized. Given that the HP Color LaserJet 5550 is an sRGB printer as per HP, perhaps that is a problem? I would assume the 'In Device' option would bypass Colorsync (since there seems to be no other way to turn it off) and use sRGB, but that does not seem to make a difference in the image being printed.
    My good success with an OS 9 driver leads me to believe I have a driver problem in Tiger. However, I have no problems with other printers (HP All in One, DesignJet Color Plotter and wide format Epson inkjet....all of which are older) with respect to poor color output. Given this is a current model in the HP line-up and I believe in service during Mac OS X Tiger, it seems hard to fathom other users do/did not experience a problem.
    Again, do Leopard users have a problem with color issues on this printer with default driver settings? Does anyone have driver settings/other insights they could share with respect to Tiger to at least get the print image somewaht close to the screen image? As it stands now, regardless of settings, the printed image is dark with muted colors.
    Thnaks to anyone who can respond, even if it is to say they have no problems in Leopard/Snow Leopard as I am upgrading to a new Mac soon.
    -Ray

Maybe you are looking for