Firewire 800 crashes win 7 on bootcamp

I am using a late 2011 15" MBP (8, 2) with an upgrade to 8gb of ram.
I am running Windows 7 Ultimate on Bootcamp to use Adobe Software products (as Windows has advantageous features that are not supported by OSX).
The problem begins and ends when I plug in my Lacie Quadra 2tb external HDD to edit/grade videos in Premiere Pro (CS6), Speedgrade (CS6), and when transferring files (so just about any action that uses firewire): the computer crashes/freezes. There is absolutely no response in inputs or outputs, and the only way to get out of it is to force-shutdown the system.
This is just a terrific situation since Apple decided to get rid of the Expresscard slot from MBP's so that I can't use USB 3.0. I just don't know why the computer keeps crashing when using firewire 800, because everything goes over smoothly while using USB 2.0 (it's just too **** slow for my purposes).
I am very desperate for a solution for this FW800 problem... Can anyone out there help me, please?

It works. No more lock-ups for me with the legacy driver.
Here are the instructions (taken from the link above):
Windows 7's built-in FireWire (called IEEE 1394) drivers do not work properly. External devices connected via FireWire will either fail to be recognized properly, or lock up when initiating file transfers of any appreciable size. Luckily there is a relatively simple fix for this issue. Windows 7 includes the older Vista drivers, which work just fine. You simply need to roll back the drivers on your 1394 host adapter by doing the following: Open Device Manager, expand your IEEE 1394 Host Bus Controllers and right-click on your 1394 device, then choose "Update Driver Software". In the new window, click on "Browse my computer for driver software", then choose "Let me pick from a list of device drivers on my computer", then select the driver with the word "legacy" in brackets.
Don't forget to restart after you do this.

Similar Messages

  • Firewire 800 / Crashing / Windows XP Pro

    I have a brand new (bought 2 days ago) MacBook Pro 17. 10.5.6 with all updates applied. Using bootcamp assistant, I split the drive into 2 equal partitions and installed Windows XP, Service Pack 3, all current Windows updates applied (Partition formatted as NTFS). In setting up the back up, I'm having trouble with backup programs crashing while backing up to external hard drives (again, formatted as NTFS). The backups will be plugging along and then the system will just freeze completely, no keyboard, no mouse function and the only way to recover is to power off and restart. I've tried 2 different external drives (both LaCie), 2 different firewire 800 cables, 2 different backup programs (Norton Ghost 14 and SecondCopy). If I connect the same drives using USB cables, all works fine, albeit slower than firewire 800. I've even re-formatted both external drives as NTFS directly from Windows running in boot camp.
    The same Firewire 800 cables are used to connect to external Mac volumes while backing up the Mac partition via TimeMachine and they work fine
    Any ideas?
    Thanks!

    There are adapters. If you want drivers, I'd think Microsoft and Windows Update. Apple has a tech note about slow performance of FW800 (google is faster than Apple Search). But I thought 2008 ushered in somewhat better FW800 (for Mac Pro).
    Personally, I stay away from LaCie. Sometimes that are firwmare updates for LaCie (all FW drive cases have to use a bridge).

  • LaCie 500GB External Firewire 800 causes crash every time its plugged in???

    My LaCie 500GB Firewire External hard drive causes the computer to freeze every time I plug it in.
    I just switched back to Mac from Win XP, where the LaCie was used for almost a year without a single problem. Supposedly, since it is formatted for XP use, it can simply be plugged in to my G5 (dual 2.3, 4BG RAM) and work just fine.
    I've upgraded to 10.4.4 and still have issues. I've read this is a 'kernal panic' issue, etc.
    What is the solution? I can't even plug it in and reformat it - as soon as it's plugged in the Mac collapses; the screen goes 'grey tinted' and an error message appears telling me to hold down the restart button and restart the computer. If I leave the drive plugged in, as soon as I've signed in on the restart, it crashes/freezes/collapses again, same error (i.e. it's circular).
    There seems to be no solution. Any help MUCH appreciated!
    Thanks,
    Sarge

    Welcome to Apple Discussions!
    First find out if this is a Firewire 800 or 400 problem. Try connecting a Firewire 400 cable to the drive if it supports it. If it only has Firewire 800 ports, you may want to get a Firewire 400 drive to experiment to see if that's all the problem is.
    After a forced reboot, it is also always wise to repair the directory if you are backed up:
    http://docs.info.apple.com/article.html?artnum=106214
    If it detects issues on your source drive that it can't repair, and you are backed up, then I would use Alsoft Disk Warrior.
    If it detects no issues, then the problem probably resides in either the cable or the drive you are connecting to. Try a little process of elimination.

  • Time Machine won't mount Firewire 800 drive after restart / Finder crashes

    I've been having problems with Finder crashes. I first suspected Spotlight might be the problem because sometimes when I started typing a search, it would display the first 3 characters and then lock up. I could force quit the Finder, but it wouldn't relaunch and required the computer to be shutdown and restarted with the power button. Once restarted, I had no keyboard and no mouse click (the mouse would move across the screen but I could not click on anything). After waiting several minutes (3-5) the mouse and keyboard worked properly.
    After some research suggested the Spotlight index might be corrupt, I forced Spotlight to rebuild the index (add the drive to the exclude list under "Privacy" and then remove it from the list) and then repaired disk permissions. After that Spotlight was noticeably snappier and I thought my Finder crashes had been solved until........
    Part 2: I have been using Time Machine (connected to a Fantom GreenDrive via Firewire 800) for several months now and ever since the beginning, I have noticed that the drive will NOT mount after a restart. I must turn the drive off and back on again to get it to mount. After that Time Machine picks it up and seems to work fine.....well, that is until this Finder crashing thing started several weeks ago. Anyway, I inadvertently set up an experiment last weekend when I installed some software update and forgot to remount the Time Machine drive after the restart. That was last Sunday night. The computer did not crash all week long. I thought my Spotlight fix had finally solved my problems, but now it seems I was wrong. This morning (Saturday, six days later), I noticed my Time Machine drive was not mounted. I mounted it, told Time Machine to "Back Up Now" and went away for a few hours. When I came back the Finder was locked up.
    So guess my question is this: Are there any know problems with using Firewire 800 with Time Machine? and What can I do to fix this? In the meantime I'm trying another experiment - I've disconnect the Firewire 800 connection and replaced it with USB.

    shaneeudy wrote:
    So guess my question is this: Are there any know problems with using Firewire 800 with Time Machine?
    Hi, and welcome to the forums.
    Not in general. Some drives don't always wake or "spin up" fast enough; often that's seen when the system wakes from sleep, though, not so much after a system Restart. Many Western Digitals do that; I don't recall seeing any posts here about yours, but you might want to search the forums for Fantom
    In the meantime I'm trying another experiment - I've disconnect the Firewire 800 connection and replaced it with USB.
    Good plan - that may provide a clue.
    Also, check with the maker -- there may be a firmware or driver update.
    And try verifying your internal HD, and repairing your backups, per #A5 of Time Machine - Troubleshooting (or use the link in *User Tips* at the top of this forum). Either might cause that.

  • PowerMac G4 FireWire 800 freezes/crashes-post modification 300GB drive

    wondering if anyone one had any insight into this problem:
    I recently installed a 300GB internal drive into my G4, running on the same carrier as the one that came with the computer, both on the ATA/100 bus, the rear carrier.
    The system software and apps are still on the original 80GB drive and I'm using the new drive for storage.
    Occasionally the computer crashes/freezes, mostly when I'm trying to shut down the computer, forceing me to force a shut down.
    Wondering if moving one of the drives to the front carrier, ATA/66 bus might solve the problem? I would appreciate any help/insight anyone could give me.
    -Steve Hastings
    PowerMac G4 (FireWire 800)   Mac OS X (10.3.9)  

    Apple Hardware Test is not Disk utility. its a separate ROOT type test that checks everything with your computer. normally some version of AHT came with your system discs.
    Diskwarrior just checks the drive index, its like a "roadmap" program, when your run DW it checks this roadmap and will allow you rebuild the map which tells the Drive where to look for stuff. sometimes those directions get fuddled. instead of actually moving the "roads" or building new ones, DW changes the map to reflect how the data on the drive appears. DW DOES NOT physically alter your HD.
    if you are having other system stability concerns you might download YASU 2.0 from versiontracker or macupdate. its donationware app that allows you to clear all sort of system caches and logs and safari junk, and run various CRON scripts from a simple GUI.

  • When I plug in my Lacie Firewire 800 drive it causes certain apps to crash. Chrome will immediately crash when I open it, so will DVD player. It's only when I plug in my Firewire 800 drive, USB does not cause issues. What's the deal?

    When I plug in my Lacie Firewire 800 drive into my Mid-2009 Macbook Pro running Mountain Lion - 10.8.2,  it causes certain apps to crash. Chrome will immediately crash when I open it, so will DVD player. It's only when I plug in my Firewire 800 drive, USB does not cause issues. What's the deal?
    I've restarted, verfied the disk, repaired permissions, smc reset.. don't know what else to do..

    Contact Lacie since it's their product you are having issues with. 

  • Computer crash with iTunes - Using external firewire 800 drive

    I am using an external firewire 800 drive (2TB Lacie) to store all my music for iTunes... At random times this crashes the computer, the music "skips" and the computer has a grey notice telling me to shutdown immediately. I am not sure why this is happening, but think this must be some sort of conflict issue... but no clue how to resolve... Any advice would be great!! Thanks!

    Oh no, sounds like kernel panics. Time to head directly to The X Lab to read the FAQs and get started with maintenance and troubleshooting. Unfortunately, this problem goes way beyond iTunes, so for additional support, you should post in the appropriate OS X forum.

  • Full screen games crash at launch on Bootcamp Win XP with Apple Cinema Disp

    Hello,
    strange issue to me. Everything goes flawlessly on Win XP on Bootcamp on my 2010 MBP 13", and games launch full screen with no problem. But as soon as I use my external 20" Apple Cinema Display, they crash immediately after launch. I wouldn't know on Windows how to get console logs etcetera.
    This is an issue with all games launched at full screen. No issue in applications.
    How to fix this?

    Anyone, please.
    This now only happens with Unreal Engine games since I chose "use this screen only" on my Nvidia preferences. I think it has to do with the Win XP drivers for this Nvidia integrated chip (Geforce 320M), which aren't much updated in Win XP. I think I could fix it by updating to Windows 7 and using newer drivers which aren't available in XP. Hope so.

  • Recording to external hard drives - Firewire 800 problems

    Ok so i did post a similar thread on this in the "mac mini" part of the website so im very sorry for double posting but I thought since this problems pertains mostly to recording and specifically recording on garageband, that I would try posting here as well. Heres my deal:
    I am a musician working with garageband and I have always been recording to my internal drive until recently. I was unaware until I read some posts here from the good people like you guys, that that is not a good idea to record to your internal drive. So, I got an external firewire 800 drive (http://www.amazon.com/gp/product/B001DGZ05A) and this cable (http://www.amazon.com/2M-Firewire-800-9PIN-Cable/dp/B000XQILWK/ref=pdbxgy_e_imgb). When I received it, I first used disk utility and reformatted it for Mac OS Extended Journaled. Then I proceeded to move a couple sample libraries and my entire "Garageband" folder (with my saved songs in it) to the external. I instantly knew something was wrong. The files were taking forever to get written over. It took about 15 mins for a 5GB folder to be moved over. I was already discouraged. Anyway, I plugged in the USB cable that came with the external (the drive has hook ups for both USB 2 and firewire 400/800) and tried moving the same files and it was MUCH faster. The same 5GB file was moved over in a matter of minutes.
    I then tried recording to the drive (using firewire again) and it would hardly even PLAY the song without stopping every couple seconds (too many effects error, and yes ALL the tracks were locked). Tried to record as well and i'd get even less time before garageband would stop the song with the same error. So I disconnected firewire and went USB. Thru USB the song didnt stop once, not on playback OR recording. Then I moved the songs back to my internal and played them (and recorded) with no problem either.
    I ran a couple tests on the drive using AJA system test and came back with these results:
    Basic test of read/write speed using firewire 800:
    write - 14/mb sec
    read - 21/mb sec
    then, using usb 2.0
    write - 18/mb sec
    read - 37/mb sec
    both these connections seemed to be running slower then they should ..but at least the USB connection would actually let me play a song and record to it without stopping
    I manually copied over a 2.04GB file and via firewire 800 connection it took 2 mins and 20 secs. Via the USB 2 connection it was 55 seconds! ..also, while i transfered the files i noticed that the USB transfer was nice and steady with tiny increments of the file being transferred. Firewire, however, was speedy then slow, speedy then slow. Very inconsistant transfer speed throughout the process. kind of choppy
    So what gives? I cant figure out if I'm doing something wrong, or if my external HD is bad? Or the cable is bad? Or maybe the firewire port on my mac mini is bad (i've never used it before for anything other than this external drive). Or i'm thinking maybe my processor isnt strong/fast enough to record to the external firewire drive? Im working with a mac mini 120GB internal HD and the 2ghz intel core 2 duo with only 2GB ram (i know thats not ideal for recording and im planning to upgrade at some point, but i have been recording to the internal just fine with the RAM i have now and never had a problem until trying to record to the firewire drive). I was going to go out today and get a new cable and see if that was the cause of it. Anyway sorry for the book-length post! But PLEASE SOMEBODY help me here! ..as i said, im not very computer literate and only just started producing music using computers so please use dummy terms lol ..thanks in advance

    Strictly my opinion, and more than happy to be educated with facts and convinced otherwise... but, there are no dangers.
    Bottom line is this... does your specific computer setup encounter ANY problems during recording or editing with your chosen software and current workflow? If not, then there is nothing wrong. Simple as that. Further, if you are having problems, then its more than likely dealt with by upgrading RAM amount and internal HDD speed and size. If you have a slightly older machine that is pre FW800, you will find by bench marking your HDD's that an upgraded internal system HDD will significantly outperform any external HDD read/write spec's. Even with FW800, comparing apples with apples, your system HDD will more than likely have better spec's. Please however, do not take my word for this, but try it out for yourself. Make sure you have facts about your own system rather than believing my claims or anyone else's claims. I used Intech's Quickbench http://www.speedtools.com/QuickBench.html to get some facts about my machine.
    There will be an argument made that you will be putting strain on your hard drive by recording to the system drive because it not only has to deal with this function but also with other functions related to your audio programs and OS. Apparently you may be working it on the 'hard' side and shorten its life span. Probably technically correct but practically speaking you will more than likely never even notice any such strain. If you are worried about a system HDD crash or death because you are working it too hard then the answer to this is a well planned back up regime. You should have one anyway, regardless of setup.

  • Can I use my firewire 800 wd hd in my windows boot camp?

    I have a my passport studio 1tb hd with usb and firewire 800, i just installed windows 7 via bootcamp on my computer. I partitioned a portion of it to exFat which I plan on converting to NTFS or something. Can I use it with the firewire cable any way? I don't have the usb with me at the moment.

    I removed the exfat partition because windows didn't recognize it. I left about 200 gb of free space though. I looked in computer management, under disk management and windows shows my ext hd as being unallocated, even though it is hfs+ and contains about a gigabyte of info. My question is: if I try to make a partition using windows, will it erase the information on my hfs+ portion?

  • FireWire 800 Daisy Chain Problem

    Hello everyone, I have three firewire drives. Two 2TB 3.5" drives and one 2.5" 1TB drive. All three are connected to my MacBook Pro 13" via the one firewire port in a daisy chain. I usually always have the 3.5" disk connected. When I add the portable drive to the daisy chain, it crashes the desktop drive, and I get the "do not disconnect drives without ejecting" message. Is this normal? I am thinking of purchasing the Thunderbolt to Firewire 800 adapter, only to avoid the crashes of the other drives in the Daisy chain.
    My Mac is an early 2011 13" MacBook Pro i5 2.3GHz with 16GB RAM.
    Thank you for your help in advance

    Sorry for my late answer.
    The disc has 2 FW800 and 1 USB2.
    If you buy a TB to FW800 you should give to the disc more power from the TB port.
    If you connect the disc with USB you could use a special cable with 2 plugs on one side and one smal USB plug on the other.  This cable is designed to give to one disc the pover grom 2 USB ports but one of the 2 can also be connected to an USB power supply, so ytou will give to the disc more power....   of copurse with USB you have a lower speed.
    If you have Thunderbolt you should try to use TB discs. I know they are expensive but there is a trick which I like to use... have a look here  http://www.youtube.com/watch?v=1Aa3BXmQVpc 

  • NitroAV FireWire 800/1394b Express Card (34)

    After some foot dragging by FireWire direct, today I finally received the NitroAV FireWire 800/1394b Express Card ordered almost a month ago.
    First Impressions: Unimpressive at best.
    According to the FireWire direct rep, it is supposed to work using the Mac OS built in drivers and require no additional driver....
    Upon first insertion, my MacBook Pro promptly went into a kernel panic.
    NOT a good introductory performance!
    Upon restart, I did get the thing to work, "sort of".
    First, it requires AC power even with a 2.5" external drive meant for bus power. Bummer, but so be it. However, less acceptable: it is VERY fussy about sequence, reminding me of evil SCSI voodoo rituals from the past century. Seems it only likes to work once- if I remove the card, it requires a reboot to recognize anything attached to it subsequently.
    Functionality is intermittent. Sometimes I can mount and unmount a drive several times in a row, sometimes just once before it fails to recognize the drive and requires another reboot. One drive it took a long time to recognize but eventually it did- only to freeze up rock solid soon thereafter requiring an uncomfortable long push on the power button to shut down- nothing else worked. That drive was a known to be working Lacie, the first a known to be working WiebeTech and both are totally reliable on my G5 and previously completely reliable on the MacBook Pro using the integrated FireWire 400 port.
    Unscientific results so far show a modest speed increase transferring a few large files, nothing like double the FireWire 800 speed hoped for. In any case if it ain't reliable it ain't gettin' used. Hoping for a driver solution in 10.4.7? (Wishful thinking)
    No one likes a fussy device, much less one doomed to corrupting directories with that kind of behavior. I'm disappointed with Apple for omitting the FireWire 800 port on the 15 inch model and leaving us with this cheesy "solution".
    I am not a big fan of dongles, or things like Express cards which are just asking for trouble by introducing intermediary third party connectivity issues exactly like these...
    Oh yeh, and the little metal door on the Express Card slot tends to hang open and not snap closed- just to add insult to the whole process.

    Well, after two days of use I have a bit of data regarding the NitroAV (and Apple's implementation of ExpressCard/34).
    First some general observations: like bigwheel, there are a few too many rough edges to be fully pleased. After inserting the card, a menu bar icon appears next to the Airport icon. On mouse over, the drop down shows "Unknown Vendor" and "Firewire Controller" are greyed out, while the 3rd "Power off Card" is selectable but does NOT power down the card. Looks like I have to shut down the MBP, then eject the Nitro card.
    I also can confirm intermittent unmounting and remounting. My latest experiment is to leave the drive mounted and then have it wake up after sleep. So far it's worked once, but will post if it continues to find my FW 800 drive over time.
    One major design flaw of the ExpressCard implementation - to engage the card you push in until it clicks, while to disengage the card you merely push in a second time. But how are you supposed to ATTACH FW800 cables?? I find I have to try to hold the ExpressCard firmly so it doesn't go in while fumbling with the FW800 connector. WAY too fussy...
    OK, here's some actual test data, involving transfers of 1,000 MB of files (147 Canon RAW files, approx 7 MB each).
    I used three hard drives for various transfers -
    1. Internal stock 100 GB - 5400 rpm (TOSHIBA MK1032GSX)
    2. FW 800 / 400 500 GB - 7200 rpm (Seagate 3500841A in OWC Mercury Elite case)
    3. FW 800 / 400 250 GB - La Cie 7200 rpm drive
    All test are transfer of 1 GB of files from HD to HD-
    Test 1: Internal to FW 400 - 68 seconds
    Test 2: Internal to FW 800 - 65 seconds
    Test 3: MBP built in FW 400 daisy-chained - 54 seconds
    Test 4: Nitro FW 800 daisy chained - 43 seconds
    Test 5: Nitro FW 800 port A to Nitro FW 800 port B - 43 seconds
    Test 6: MBP built in FW 400 to Nitro FW 800 - 35 seconds
    So it looks like there is some speed increase, but I was surprised that mixing the FW 400 and FW 800 ports gave the fastest transfer speeds! The Nitro card is dependent on Apple's implementation of buses, and this seems to be the winning combo. Not that intuitive that shifting one of the FW 800 devices down to FW 400 will speed things up, but that's what my simple test seemed to imply.
    I didn't test read times only, but it would seem that these should speed up (and hopefully speed up my primary application of Aperture).
    MBP 2.0, 2GB   Mac OS X (10.4.6)  

  • M-Audio 1814 and FireWire 800

    I am working on a MBP and Logic 8, using the Vienna Symphonic Library on external hard drives, one 250 GB LaCie, the second a 500 GB Maxtor. When I use the external hard drives with FireWire 800 first the Audio Interface starts clicking, using Logic 8 the system crashes seriously. If I use the FireWire Hub on the back of my Cinema Display, the 1814 is not recognized.
    For the use of the VI-Library I need fast hard drives, the CPU seems not to be the problem. Why I cannot use FireWire 400 (Audio Interface) and Firewire 800 hard drives?

    Thank you Chris, I just wonder why Bee Jay can use the HD FW800 with the M-Audio Firewire interface without problems.
    I use the ext HD for backup too, but sometimes I need to find something in my backups and I have to turn off the audio interface and copy the files on my internal HD ... then turn off the drive again and turn on the M-Audio ... it's very annoying.
    In some forum I read that the problem can be the firewire chipset, but my iMac has the Lucent and the MacBook Pro has the TI (reccomended by M-Audio) ... same problem on both machines.
    I did some test:
    1) If I use the FW800 external HD and the FW400 with iMovie and my Video Camcorder I have no problem at all. I tried to use the HD at maximum (during a time machine backup I was copying other files and saving the HDV files in the same external HD) and everything works perfectly without loosing a single frame.
    2) If I connect the HDV camcorder to the M-Audio interface I cannot even start the capture ... I have to turn off the external FW800 HD.
    It looks that the problem is definitely in the M-Audio Firewire driver but unfortunatley the M-Audio e-mail support is only for US customers ... and I'm Italian.
    Is there any US customer that has this problem and can insist with the M-Audio support?
    Maybe they can solve it in the next release ...
    Thank you in advance.

  • Bus powered Firewire devices crashes

    I have a Macbook Pro (June 2009) and a Western Digital Passport hard disk with a Firewire 800 connection, bus powered. It has an optional USB 2.0 connection
    It keeps crashing the system with firewire, not with USB.
    Especially when I move large files or Time Machine backups or migrations with Migration Assistant, the process stops at some point, eventually forcing me to shut the computer down.
    My bet is that it's something related with the power, because this problem does'nt occur with the USB connection.
    I also have an USB keyboard connected. Could this be the problem? Is the USB keyboard sucking so much power out of the mac?
    Please help.

    Welcome to Apple Discussions!
    I wonder if there might be a problem with the firewire bridge in the WD? The most reliable Firewire chipset that I know of is the Oxford 924+, but not everybody uses these. You might be able to find out what is actually used on the WD web site.
    Since the USB connection works, the WD drive itself is probably fine.
    Does your FireWire 800 work properly with other devices? If not, or if you don't know, you could try a SMC reset, which may help if the problem is with the FireWire port on the MBP:
    http://support.apple.com/kb/HT1411?viewlocale=en_US
    Otherwise, you could try the drive in a different enclosure, like the Mercury on the Go from OWC, which has the Oxford 934 chipset. I have WD drives in 3 of these enclosures, and have never had a problem with any of them.
    Good luck!

  • OSX 10.7.5 Finder unresponsive when using firewire 800 devices

    My system was running well until recently when my finder in OSX 10.7.5 has beccome intermittently unresponsive. Many apps, especially Mail are not very responsive either.
    I have multiple external hard drives (both 400 and 800) hooked into a Nitro AV firewire 800 hub repeater. When I pull the firewire 800 cable from the port on my Intel iMac, the system and finder seem to work properly. When using a single device plugged into the iMac's FW 800 port, the system and finder also appear to run fine.
    Other symptoms include drive icons not ejecting and freezing on the desktop, system crashing often, very slow startup, apps running slowly at times and becoming unresponsive during use, slow opening of folders and slow launching of apps.
    If anyone has had similar problems or has any experience with these issues, I would be grateful for your help.
    Thanks!!

    I read another thread about the same problem and it is checked under Finder>Preferences.  All boxes except Macbook Pro are checked.

Maybe you are looking for

  • HP 4540s will not activate windows 8 from HP recovery dvds, please help

    Hi, I'm trying to migrate my HP from the harddrive to a new ssd I bought. As far as I know windows 8 is supposed to activate based on the code burned into the machines bios, so I bought some hp recovery dvds online as HP recovery manager no longer se

  • Applet failed to load in Internet Explorer when using JRE 1.5 update 5

    I have downloaded JRE 1.5 Update 5 and checked the relevant checkbox in Internet Explorer Advanced tab to use JRE 1.5 for applets. Did the same in Java Control Panel. However none of the applets seem to load. For example I went to this site: http://j

  • Issues with hooking up an older kodak aio3 printer to a new hp windows 8 computer

    I have a new HP p2-1343wb setup that came with a monitor. It is running Windows 8. I have an older Kodak aio3 printer that i used to use on both a Windows Vista and a  Windows XP computer. When I tried to intall the software and drivers for the print

  • Parent account key name/description in report

    Hi Experts! So here is the code where i am retrieving postings detail (invoice rows, BP, system amount, doc number, distribution rule and project) Declare @FromDate Datetime Declare @ToDate Datetime Set @FromDate = (Select min(T0.[TaxDate]) from OPCH

  • Retest Date Calculate from manufacturing Date

    Dear all, If we are doing Goods Receipt  for Finished Goods, Semi Finished Goods or Raw Material the  Retest date is calculated from Posting Date (GRN) as per SAP Standard. But our client required it should be the retest date is calculate from Manufa