Twin Terminals- almost
Hi
I wonder if any of you can help me with this issue i created, I moved Terminal into Applications Folder some days before doing an Archive & install and now I have two terminals but they are different v. only package difference seems to be the info string. Here is the plist info, in get info i get the same versions a described below
<key>CFBundleShortVersionString</key>
<string>1.4.6</string>( ORIGINAL moved in applications folder before archive)
<key>CFBundleShortVersionString</key>
<string>1.4.1</string> ( NEW After Archive in Utilities after archive and install ) and Combo Update 10.3.9 update.
I was think along with others that i should delete the one that is not updated,
thought about do the Combo update but then I would still have two, i am betting only two heads are better at this point, not me with 2 of these. Any advice would be so very appreciated.
Thank you for your time.
Eme:~O
p.s. I not too learned, as you have probably surmise !!
Power PC G4 (3.3) iMac ♥ Flat Panel 10.3.9 & 15 Alum.PowerBook Tiger Mac OS X (10.4.5)
I had moved it before about a week before I did an A & I , did not think to move it back ( it was moved in response to the leap- A alarm. )
The fact though is that the newer one is in Applications 1.4.6 where I moved it to, not the one that you would presume would be newer in App/Utilities.
Does that indicate a problem. Do you think it could be an indication of a continued corruption in the os ?
I have done the security Updates as presented in Software updater presuming it knows the needs of the system. Perhaps there is an Sec-Update it still needs This is the Software Update Log as follows w/ out Airport Updates:
2006-02-27 01:52:36 -0500: Installed "Mac OS X Update Combined" (10.3.9)
2006-02-27 02:12:07 -0500: Installed "Apple Remote Desktop Client" (1.2.4)
2006-02-27 02:18:31 -0500: "Java 1.4.2 Update 2" (1.4.2 Update 2)
2006-02-27 02:18:41 -0500: "Java Security Update" (4.0)
2006-02-27 02:23:31 -0500: "Java Update for Mac OS X v10.3.9" (1.0)
2006-02-27 02:24:26 -0500: "Security Update 2004-10-27" (1.0)
2006-02-27 02:26:17 -0500: "Security Update 2005-008" (1.0)
2006-02-27 02:37:46 -0500: "Security Update 2005-009" (1.0)
2006-02-28 17:31:35 -0500: "iSync" (1.5)
2006-02-28 17:33:29 -0500: "Security Update 2005-004" (1.0)
I remember doing 2005-005- and 2005-007last year, I do not see them I do not know if they are part of the new Combo 10.3.9, I have not yet done the latest Sec. Update 2005-001
What do you think I should do, should I move the ORIGINAL from Applications back into Apps/Utilities and trash the one Non -Updated that's in App/Utilities.?
Thank you for your patience and help, I appreciate it. Eme
Power PC G4 (3.3) iMac ♥ Flat Panel 10.3.9 & 15 Alum.PowerBook Tiger Mac OS X (10.4.5)
Similar Messages
-
Design Flaw in Twin Frozr fans
So, I'm finally creating a thread about this.
There's been reports over the last few years about fans making rattling noises, grinding noises, high pitched whines, whether on cold boot, idle, high RPM, or constantly, and quite frankly I'm tired of MSI ignoring the issue.
There is a design flaw with the Twin Frozr fans.
MSI needs to publicly acknowledge this.
Currently, the only way to get a replacement fan is to send your ENTIRE card in for repair. Other more reputable companies will send you out an entirely new fansink attachment at no cost. As one poster said it; "That would be like sending my car to Nissan every time I blow a tire"
My personal experience with Twin Frozr started with Twin Frozr 2 on my GTX 460 Hawks. The Talon Attack edition started to make a bad grinding noise on cold boot or if it actually got cold enough during idle operation. When the card warmed up, the noise stopped. Speeding up the fan to 100% sometimes also caused it to get rid of the noise, but that was only temporary unless the card stayed warm.
My non-hawk exhibited rattling as well, but to a lesser extent. No grinding noise on cold boot, just a low rattling.
My next card was a GTX 670 PE with Twin Frozr 4. Surely they fixed the issue by now right? Wrong! Within 30 days I started having fan issues. This fan doesn't rattle, but there is a high pitched whine when the fan is in operation. The faster the RPM, the louder the whine. Most people don't even know they have this issue because of the subtle tone of the whine and it being muffled by the fan's air sound at higher RPMs.
That's 3 separate graphics cards all exhibiting an issue with their fans.
There's one thing in common with these issues; it's only caused by the fan closest to the I/O. This boggles my mind. Surely if there was a problem with the fan design itself it would affect both fans, right? I just don't understand it. This leads me to believe it's a design flaw with the Twin Frozr design.
Some people seem to have an issue with the other fan, but it appears to be rare and not the same type of problem the majority of people are reporting.
Seeing as they want you to lose your card (and $10+ to ship it) for weeks at a time to 'fix' an issue which will no doubt happen again, something needs to be done about this. Their 'warranty' policy for this issue is completely unacceptable, as is the fact that the fans start acting up within a month of ownership.
If you want to see more threads, just do a search. Here is some of them:
https://forum-en.msi.com/index.php?topic=151578.0
https://forum-en.msi.com/index.php?topic=157567.0
https://forum-en.msi.com/index.php?topic=156284.0
https://forum-en.msi.com/index.php?topic=161914.0
https://forum-en.msi.com/index.php?topic=153463.0
https://forum-en.msi.com/index.php?topic=154030.0
Googling brings more results. I've posted about it in this thread, and others have mentioned it as well: http://www.overclock.net/t/1265574/msi-gtx-670-power-edition-twin-frozr-4-cooler/0_30Quote from: Noway77 on 28-May-14, 05:39:49
I don't think we have a MSI office in Portugal, most brands don't.
Some stores are not reliable they buy from EU retailers some even from Asia retailers and usually they don't give proper support. In Lisbon you have stores like Globaldata, Nanochip, Chiptek and AquaPC they are in business for years, have good customer support and have also good prices.
I'm probably not going to buy any MSI product from now on , for obvious reasons.
Trying to contact a support shoudn't be this hard from a client , at this point I assume anyone that's doesn't want to lose time will just give up.
As a consumer I was forced to RUN and TRY to find msi support , MSI support mail doesn't event exist , since I made this thread it still hasn't been changed.
I really liked MSI ( I still have my 875P MSI neo here with my p4 and the NX6800 working ) it's like saying goodbye to an old friend that has been by my side since P4 times.
I'll buy msi products in US , or in another country maybe , but never MORE in portugal.
This is not cause of the shops , I recommend everyone to buy in the shops listed !!
In fact most of the portuguese shops tried to help me find msi support ( even though they weren't the stored that sold me the card ).
I really don't want ppl to get this mixed up, the problem here is MSI not acknowledging a problem that is simple to fix, having a non-existant email on their webpage as support for over 4 months and the fact that as a consumer I was forced to jump trough loops to actually contact MSI itself !
Every portuguese shop I contacted was super nice and really helpful pointing me to the new msi email
And actually the fix ( hot needle fix forum post link ) came from a shop reply.
US support was always super nice and helpful !
I was forced to fix my fan with the help of users.
If right now my MSI gpu is working is thanks to guru3d and hardwareoc and simillar forums ( thanks to everyone that posted Twin Frozn fixes , this may not mean much , but really .. thanks for helping me out ! )
MSI didn't help or even try to help me , I had to go out of my way to get help , and I never did.
I know some of those stores , they have great prices , but if I buy anything in portugal I'll buy other brands for obvious reasons. ( it was actually one of those shops that helped me pinpoint the "real" msi email )
I am a customer , I should be treated as such , I was joked and pushed around emails , found emails that don't even exist , I was ignored and left looking at a card going dead.
Maybe for some of you it's easy , you just buy another one .... and maybe that's the custommer MSI wants. But that's not me.
Pointing me to places to buy MORE is almost insulting at this point. I wont buy more ... I would be stupid of I did.
I just hope some other person that has MSI and is having this problem with Twin Frozn fans ( that msi refuses to acknowledge as THEIR problem !! ) can fix them themselves or take some info from my posts and others to at least understand what is happening.
From my pov , the fan eventually has some sort of lubrication problem , and due to that it starts to wobble , after that the coils heat up to a point it wobbles even more.
Due to the high temps the fan either "looses" enough to dump all the lubing out.
At some point the fan will heat up so much the plastic IS REALLY hot to the touch and fells that it can be actually moldable ( so I assume this is really bad )
This leads to the start-stop problem , the fan tries to kick itself on , but just makes things worse.
This leads to a fan that fails in 2-3 years.
MSI should either had a way to put oil in the fan OR just start to be ready to replace them.
The fact that IS an ebay market for Twin Frzn fans is just flabbergasting .
I wish I had a better view on this , but seriously looking at this thread, and seeing all the steps I have done , to find there are others like me that have a failing fan and that the ones that aren't ignored like me have to RMA a card for a simple fan doesn't give me any sort of confidence in this brand.
MSI has one of the best gpu coolers , honestly it's so god that after all this mess I stand as a testimony for it being one of the BEST gpu coolers around ! All my MSI products so far have been great ... but this experience was just ... weird ..
I wish MSI would contact the ppl that are in my position and help them , it's just a fan , it's an easy fix and it's easy to replace.
There are lots of ppl right now with fans starting to fail , just take their card , replace the fan and send them back , and MSI will have happy customers , HAPPY cause the brand CARED !
I'm only 1 client , MSI hardly "fells" me leaving ... I really like MSI ... so I wish this won't ever happen again to no one !
I have been ignored in mailing for TDR problems , after that about the 12h+ card artifacting being fixed with cold boot ( I assume this was an nvidia problem )
After using certain drivers that didn't TDR my card ( I have enough PSU for it so ... it's not the PSU ) and having been 2 years finding my own "solutions" to problems ... being ignored and just struggling to get help from MSI for a stupid FAN a cheap part and being hard just to contact them to get no answer .... and getting help from other users while MSI ignores me ? ... I'm thinking on leaving the brand ...
The fans are now working 100% , I'll post info when and if they fail ( if I see my "fix" stopped working ) .
It has now been a long time since 2011 and my first reports , and its been almost 6 months since I contacted msi about the portuguese email listed not existing.
The email is still there , that non-existent email is STILL listen in MSI website RIGHT NOW after me being emailing them about it for 4+ months ,as a customer, I can only assume they either ignore people , or they have a terrible communications internally .
Again after all this mess , I would be kinda stupid to support or try to buy another product from this brand , MSI support was always great and was the main reason I bought msi products, all this posts are from a person that was truly SHOCKED in everything that is happening and the feeling that no one cared. -
Re:560GTX Twin frozr II-What does MSI mean when they say 20% cooler?
Surely it can't mean that literally? I'm currently running FEAR3 at 80c with this card, does this mean i'm really at 100c if i use another 560GTX that's not twin frozr II? or if i'm running Black Ops at 64c now, does this really mean its 80c? Pls explain the parameters of this feature bec. when i saw my temps in FEAR3 i suddenly wondered what that claim was all about. My old GTX275 had almost same temps so what's with the new twin frozr II? Pls don't suggest an RMA bec the card ain't broke. it idles at 37-38c that means the cooling mechanism works its when it loads heavy games that it acts up.
Quote from: Bernhard on 20-July-11, 14:45:52
Disconnect the front 120mm and the bottom 80mm. Only leave your extraction fans and the side fan on and retest.This way the extraction fans will pull in the air and you may have a more "smoothed" flow of air.
With an ambient temp of ~29C your load temps with the side panel open are actually excellent, as the temp increase is only about 30C.
It most certainly looks like an airflow shortage for the GPU with your side panel on.
I for one like the cases with fully meshed side panels for that reason. Good example http://www.aerocool.us/pgs/pgs-b/bx500.htm
Ok i did what you suggested and while the peak temp in the Witcher 2 was 75c it didn't stay there too long, it settled at around 67c-68c and note this is with the computer case closed. i didn't bother test it w/ an open case bec. i know the peak won't even touch 71c i'm sure. My conclusion therefore is even w/ a closed case, the temps are nothing to worry about, is this a safe assumption now that we've tested this card w/ 3 different top games, Witcher 2, Bad Company 2 and Black Ops? -
MSI N560GTX-Ti Twin Frozr II/OC: Graphical Glitches/Corruption
Hello, I bought and installed an MSI N560GTX-Ti Twin Frozr II/OC video card one week ago. For the last week, it has been running perfectly, but today when I started up a game the 3D graphics began glitching and showing random stretched triangles and distorted models. While the 3D graphics are running, the monitor randomly loses signal from the video card and occasionally the program will crash with a popup bubble stating that the NVIDIA driver has recovered from a problem.
After reading through some posts here, I downloaded the MSI Afterburner program, enabled voltage monitoring, and set everything to defaults.
The defaults are:
Core Voltage: 1000 mV
Core Clock : 880 MHz
Shader Clock : 1760 MHz
Memory Clock : 2100 MHz
When I click the button to run a Kombuster stability test, the 3D has the same graphical glitches that I saw in my games. Here is a screenshot:
http://i733.photobucket.com/albums/ww333/MP64x2/corrupted_880.jpg
I tried lowering the Core Clock speed and retrying the test. It appears that the level of corruption is proportional to the clock speed. At the minimum clock speed of 440 MHz, the graphics are almost perfect, however a glitch or two will still occasionally show up.
Here is the test at Core Clock = 705 MHz: http://i733.photobucket.com/albums/ww333/MP64x2/corrupted_705.jpg
and at 440 MHz: http://i733.photobucket.com/albums/ww333/MP64x2/corrupted_440.jpg
- I've tried bumping up the Core Voltage a little to around 1020 mV, but it doesn't seem to have any effect.
- Lowering the Memory Clock also reduces glitches, but they never go away completely.
- Even at the absolute minimum clock settings, my games still glitch and crash.
- I do not have access to another system that I can try the video card in.
System Info
CPU: Intel Core 2 Quad Q9450 2.66GHz
MoBo: Abit IP35 Pro - LGA775, Intel P35, FSB1333
RAM: G.Skill 4x2GB DDR2 800 (PC2 6400) Dual Channel (Total: 8GB)
Video Card: MSI N560GTX-Ti Twin Frozr II/OC
Video S/N: 602-V238-130B1103126135
Video BIOS: 70.24.11.00.00
NVIDIA Driver: 266.66
Hard Disks: 2x 640GB Western Digital WD6401AALS
OS: Windows 7 Ultimate 64-bit
Power Supply:
OCZ GameXStream OCZ700GXSSLI 700W
+3.3@36A,+5V@30A,+12V1@18A,+12V2@18A,+12V3@18A,+12V4@18A,[email protected],[email protected]
As I type this I'm starting to get corruption right on my desktop too, with random pixels changing color and black rectangles appearing on applications.
From what I've read in other threads, it seems like my power supply may not be sufficient since it has multiple 12V rails, but before I spend ~$100 on a new one I thought I'd see if anyone had any other thoughts.Quote from: MP64 on 22-April-11, 03:46:20
I have an interesting update on my original problem.
A week after I reseated the card, the graphical glitches returned. I turned the computer off, reseated the card again, turned it on, and it began working fine.
Another week goes by with no problems, and then a couple days ago the glitches came back. Thinking it strange that the card could somehow take approximately the same amount of time to cause the same kind of bad connection, I wondered if there was something else that was causing the glitches to temporarily disappear.
I tried rebooting my computer, but the glitches remained.
I then completely turned off my computer and pulled out the power cord and left it for a couple minutes. I didn't open the case at all and made sure not to do anything that would bump any components. I turned the computer back on - glitches are gone once again.
So, it would seem that it may in fact have something to do with the power supply and not any bad connections with the card itself - at least, that's the best guess I have at the moment. I leave my computer on 24/7 so it seems like it doesn't like being left on for an entire week with this new video card installed.
Does this sound sensible? Is it possible for a power supply to slowly fail over several days, only to start working again after being powered down for a couple minutes?
Did you ever figure your issue out? I have the exact same issue. My system runs fine for almost a week...and then my desktop starts artifacting. The only way it goes away is to unplug my pc (or flip the switch on PSU). Then it runs again perfectly for nearly a week again and I start getting artifacts and the message stating that the graphics driver has stopped working and then recovered.
I also run my pc 24/7 and this problem is getting very annoying! My PSU shouldn't be a problem as I have the PC & Cooling 750W...
Oh...almost forgot. I've seen the same issue on 2 video cards now. RMA'd the first one and the second one does the exact same thing... -
Return code = 00000057 using a gem pc twin reader with OCF
Hello, i really need help.
I'm having the famous return code = 00000057 when i try to send an APDU command, I'm using a applet proxy, so it send an select APDU inside the OCF framework, and the result is success, so i'm able to send an select Applet, but when i try to send the following apdu:
allocateCardChannel();
// Set up the command APDU and send it to the card.
getBalanceAPDU.setLength(0);
getBalanceAPDU.append(MyAPPLET_CLA); // Class
getBalanceAPDU.append(VERIFY_INS); // Instr'n
getBalanceAPDU.append((byte) 0x00); // P1
getBalanceAPDU.append((byte) 0x00); // P2
getBalanceAPDU.append((byte) 0x00); // Lc
getBalanceAPDU.append((byte) 0x05); // Le
// Send command APDU and check the response.
ResponseAPDU response;
//response = new ResponseAPDU(07);
response = sendCommandAPDU(getCardChannel(), MY_CARD_AID,
getBalanceAPDU);
i got that error. I pasted, all the debug message below. I already updated the pcsc-wrapper-2.0.jar file, but i'm still having this error, as i said i'm using an gem pc twin cardreader with gemxpresso card. My opencard.properties file:
# Card service configuration #
OpenCard.services = com.ibm.opencard.factory.MFCCardServiceFactory \
opencard.opt.util.PassThruCardServiceFactory \
br.com.neac.petrobras.medidorgas.process.NastekCardProxyFactory
#OpenCard.services = br.com.neac.petrobras.medidorgas.process.NastekCardProxyFactory
# Card terminal configuration #
#OpenCard.terminals = GemplusCardTerminalFactory
OpenCard.terminals = com.ibm.opencard.terminal.pcsc10.Pcsc10CardTerminalFactory|Autodetect|*|SHARED
#OpenCard.terminals = com.ibm.opencard.terminal.pcsc10.Pcsc10CardTerminalFactory
#OpenCard.terminals=com.ibm.opencard.terminal.pcsc10.Pcsc10CardTerminalFactory|myGEMPlus|GEM430PC|SHARED
# Trace configuration #
OpenCard.trace = opencard:9
----- the debug----
[DEBUG ] opencard.core.service.SmartCard.getRegistryEntry
--- message tag OpenCard.terminals = com.ibm.opencard.terminal.pcsc10.Pcsc10CardTerminalFactory|Autodetect|*|SHARED
--- thread Thread[AWT-EventQueue-0,6,main]
--- source class opencard.core.service.SmartCard
[DEBUG ] opencard.core.terminal.CardTerminal.<init>
--- message (Gemplus USB Smart Card Reader 0, PCSC10, )
--- thread Thread[AWT-EventQueue-0,6,main]
--- source class opencard.core.terminal.CardTerminal
[DEBUG ] opencard.core.event.EventGenerator.updateTerminals
--- message new pollable Terminal = com.ibm.opencard.terminal.pcsc10.Pcsc10CardTerminal@1e1df6e
+ name Gemplus USB Smart Card Reader 0
+ type PCSC10
+ addr
--- thread Thread[AWT-EventQueue-0,6,main]
--- source class opencard.core.event.EventGenerator
[DEBUG ] com.ibm.opencard.terminal.pcsc10.Pcsc10CardTerminal.cardInserted
--- message slotID 0, )
--- thread Thread[AWT-EventQueue-0,6,main]
--- source com.ibm.opencard.terminal.pcsc10.Pcsc10CardTerminal@1e1df6e
+ name Gemplus USB Smart Card Reader 0
+ type PCSC10
+ addr
[DEBUG ] opencard.core.event.EventGenerator.updateCards
--- message card inserted slotID = 0
--- thread Thread[AWT-EventQueue-0,6,main]
--- source class opencard.core.event.EventGenerator
[DEBUG ] opencard.core.service.SmartCard.getRegistryEntry
--- message tag OpenCard.services = com.ibm.opencard.factory.MFCCardServiceFactory opencard.opt.util.PassThruCardServiceFactory br.com.neac.petrobras.medidorgas.process.NastekCardProxyFactory
--- thread Thread[AWT-EventQueue-0,6,main]
--- source class opencard.core.service.SmartCard
[DEBUG ] opencard.core.service.CardServiceFactory.<init>
--- message instantiating
--- thread Thread[AWT-EventQueue-0,6,main]
--- source class opencard.core.service.CardServiceFactory
[DEBUG ] opencard.core.service.CardServiceRegistry.add
--- message com.ibm.opencard.factory.MFCCardServiceFactory@103368e
--- thread Thread[AWT-EventQueue-0,6,main]
--- source opencard.core.service.CardServiceRegistry@1f2ae62++ registered factory [email protected]c68b6f
[DEBUG ] opencard.core.service.CardServiceFactory.<init>
--- message instantiating
--- thread Thread[AWT-EventQueue-0,6,main]
--- source class opencard.core.service.CardServiceFactory
[DEBUG ] opencard.opt.service.OCF11CardServiceFactory.<init>
--- message instantiating
--- thread Thread[AWT-EventQueue-0,6,main]
--- source class opencard.opt.service.OCF11CardServiceFactory
[DEBUG ] opencard.core.service.CardServiceRegistry.add
--- message opencard.opt.util.PassThruCardServiceFactory@94cc7
--- thread Thread[AWT-EventQueue-0,6,main]
--- source opencard.core.service.CardServiceRegistry@1f2ae62++ registered factory [email protected]c68b6f
++ registered factory com.ibm.opencard.factory.MFCCardServiceFactory@103368e
[DEBUG ] opencard.core.service.CardServiceFactory.<init>
--- message instantiating
--- thread Thread[AWT-EventQueue-0,6,main]
--- source class opencard.core.service.CardServiceFactory
[DEBUG ] opencard.core.service.CardServiceRegistry.add
--- message [email protected]fa0f0
--- thread Thread[AWT-EventQueue-0,6,main]
--- source opencard.core.service.CardServiceRegistry@1f2ae62++ registered factory [email protected]c68b6f
++ registered factory com.ibm.opencard.factory.MFCCardServiceFactory@103368e
++ registered factory opencard.opt.util.PassThruCardServiceFactory@94cc7
[DEBUG ] opencard.core.service.SmartCard.<start>
--- message finished
--- thread Thread[AWT-EventQueue-0,6,main]
--- source class opencard.core.service.SmartCard
[DEBUG ] opencard.core.service.CardServiceRegistry.getSmartCard
--- message CTEvent opencard.core.event.CardTerminalEvent[source=com.ibm.opencard.terminal.pcsc10.Pcsc10CardTerminal@1e1df6e
+ name Gemplus USB Smart Card Reader 0
+ type PCSC10
+ addr ]
---source com.ibm.opencard.terminal.pcsc10.Pcsc10CardTerminal@1e1df6e
+ name Gemplus USB Smart Card Reader 0
+ type PCSC10
+ addr
---id 1
card inserted in slot 0
terminal com.ibm.opencard.terminal.pcsc10.Pcsc10CardTerminal@1e1df6e
+ name Gemplus USB Smart Card Reader 0
+ type PCSC10
+ addr
--- thread Thread[AWT-EventQueue-0,6,main]
--- source opencard.core.service.CardServiceRegistry@1f2ae62++ registered factory [email protected]c68b6f
++ registered factory com.ibm.opencard.factory.MFCCardServiceFactory@103368e
++ registered factory opencard.opt.util.PassThruCardServiceFactory@94cc7
++ registered factory [email protected]fa0f0
[DEBUG ] com.ibm.opencard.terminal.pcsc10.Pcsc10CardTerminal.openSlotChannel
--- message for slot #0
--- thread Thread[AWT-EventQueue-0,6,main]
--- source com.ibm.opencard.terminal.pcsc10.Pcsc10CardTerminal@1e1df6e
+ name Gemplus USB Smart Card Reader 0
+ type PCSC10
+ addr
[DEBUG ] com.ibm.opencard.terminal.pcsc10.Pcsc10CardTerminal.openSlotChannel
--- message new SlotChannel is opencard.core.terminal.SlotChannel@182815a
+ state open
--- thread Thread[AWT-EventQueue-0,6,main]
--- source com.ibm.opencard.terminal.pcsc10.Pcsc10CardTerminal@1e1df6e
+ name Gemplus USB Smart Card Reader 0
+ type PCSC10
+ addr
[DEBUG ] opencard.core.service.CardServiceRegistry.allocateCardServiceScheduler
--- message instantiating CardServiceScheduler
--- thread Thread[AWT-EventQueue-0,6,main]
--- source opencard.core.service.CardServiceRegistry@1f2ae62++ registered factory [email protected]c68b6f
++ registered factory com.ibm.opencard.factory.MFCCardServiceFactory@103368e
++ registered factory opencard.opt.util.PassThruCardServiceFactory@94cc7
++ registered factory [email protected]fa0f0
[DEBUG ] opencard.core.service.CardServiceScheduler.<init>
--- message slotChannel opencard.core.terminal.SlotChannel@182815a
+ state open
--- thread Thread[AWT-EventQueue-0,6,main]
--- source class opencard.core.service.CardServiceScheduler
[DEBUG ] opencard.core.service.CardChannel.<init>
--- message (opencard.core.terminal.SlotChannel@182815a
+ state open)
--- thread Thread[AWT-EventQueue-0,6,main]
--- source class opencard.core.service.CardChannel
[DEBUG ] opencard.core.service.CardServiceRegistry.getSmartCard
--- message using CardServiceScheduler opencard.core.service.CardServiceScheduler@4ab8b9, is alive
--- thread Thread[AWT-EventQueue-0,6,main]
--- source opencard.core.service.CardServiceRegistry@1f2ae62++ registered factory [email protected]c68b6f
++ registered factory com.ibm.opencard.factory.MFCCardServiceFactory@103368e
++ registered factory opencard.opt.util.PassThruCardServiceFactory@94cc7
++ registered factory [email protected]fa0f0
[DEBUG ] opencard.core.service.CardServiceScheduler.createSmartCard
--- message creating SmartCard
--- thread Thread[AWT-EventQueue-0,6,main]
--- source opencard.core.service.CardServiceScheduler@4ab8b9, is alive
[DEBUG ] opencard.core.service.SmartCard.<init>
--- message scheduler opencard.core.service.CardServiceScheduler@4ab8b9, is alive, cid opencard.core.terminal.CardID@1a5ba75 ATR: 3B 7D 94 00 00 80 31 80 65 B0 83 01 02 90 83 00
90 00
--- thread Thread[AWT-EventQueue-0,6,main]
--- source class opencard.core.service.SmartCard
[DEBUG ] opencard.core.service.SmartCard.getCardService
--- message (class br.com.neac.petrobras.medidorgas.process.NastekCardProxy)
--- thread Thread[AWT-EventQueue-0,6,main]
--- source opencard.core.service.SmartCard@fb7efa
[DEBUG ] opencard.core.service.CardServiceRegistry.getCardServiceInstance
--- message for class br.com.neac.petrobras.medidorgas.process.NastekCardProxy from opencard.core.service.SmartCard@fb7efa
--- thread Thread[AWT-EventQueue-0,6,main]
--- source opencard.core.service.CardServiceRegistry@1f2ae62++ registered factory [email protected]c68b6f
++ registered factory com.ibm.opencard.factory.MFCCardServiceFactory@103368e
++ registered factory opencard.opt.util.PassThruCardServiceFactory@94cc7
++ registered factory [email protected]fa0f0
[DEBUG ] opencard.core.service.CardServiceRegistry.getCardServiceInstance
--- message checking [email protected]c68b6f
--- thread Thread[AWT-EventQueue-0,6,main]
--- source opencard.core.service.CardServiceRegistry@1f2ae62++ registered factory [email protected]c68b6f
++ registered factory com.ibm.opencard.factory.MFCCardServiceFactory@103368e
++ registered factory opencard.opt.util.PassThruCardServiceFactory@94cc7
++ registered factory [email protected]fa0f0
[DEBUG ] opencard.core.service.CardService.<init>
--- message default constructor of br.com.neac.petrobras.medidorgas.process.NastekCardProxy@8f57a
--- thread Thread[AWT-EventQueue-0,6,main]
--- source class opencard.core.service.CardService
[DEBUG ] opencard.opt.applet.AppletProxy.<init>
--- message (A0 00 00 00 62 03 01 0C 02,opencard.core.service.CardServiceScheduler@4ab8b9, is alive,opencard.core.service.SmartCard@fb7efa,true)
--- thread Thread[AWT-EventQueue-0,6,main]
--- source class opencard.opt.applet.AppletProxy
[DEBUG ] br.com.neac.petrobras.medidorgas.process.NastekCardProxy.initialize
--- message (opencard.core.service.CardServiceScheduler@4ab8b9, is alive,opencard.core.service.SmartCard@fb7efa)
--- thread Thread[AWT-EventQueue-0,6,main]
--- source br.com.neac.petrobras.medidorgas.process.NastekCardProxy@8f57a
[DEBUG ] opencard.opt.applet.BasicAppletCardService.<init>
--- message (opencard.core.service.CardServiceScheduler@4ab8b9, is alive,opencard.core.service.SmartCard@fb7efa,true)
--- thread Thread[AWT-EventQueue-0,6,main]
--- source class opencard.opt.applet.BasicAppletCardService
[DEBUG ] br.com.neac.petrobras.medidorgas.process.NastekCardProxy.allocateCardChannel
--- message allocating
--- thread Thread[AWT-EventQueue-0,6,main]
--- source br.com.neac.petrobras.medidorgas.process.NastekCardProxy@8f57a
[DEBUG ] opencard.core.service.CardServiceScheduler.allocateCardChannel
--- message applicant br.com.neac.petrobras.medidorgas.process.NastekCardProxy@8f57a
--- thread Thread[AWT-EventQueue-0,6,main]
--- source opencard.core.service.CardServiceScheduler@4ab8b9, is alive
[DEBUG ] opencard.core.service.CardChannel.open
--- message opening CardChannel
--- thread Thread[AWT-EventQueue-0,6,main]
--- source opencard.core.service.CardChannel@9bb457, not open, not jammed
BasicAppletCardService - allocated CardChannel()
[DEBUG ] br.com.neac.petrobras.medidorgas.process.NastekCardProxy.releaseCardChannel
--- message releasing
--- thread Thread[AWT-EventQueue-0,6,main]
--- source br.com.neac.petrobras.medidorgas.process.NastekCardProxy@8f57a
[DEBUG ] opencard.core.service.CardServiceScheduler.releaseCardChannel
--- message releasing opencard.core.service.CardChannel@9bb457, is open, not jammed
--- thread Thread[AWT-EventQueue-0,6,main]
--- source opencard.core.service.CardServiceScheduler@4ab8b9, is alive
++ channel is allocated
[DEBUG ] opencard.core.service.CardChannel.close
--- message CardChannel closed
--- thread Thread[AWT-EventQueue-0,6,main]
--- source opencard.core.service.CardChannel@9bb457, not open, not jammed
[DEBUG ] br.com.neac.petrobras.medidorgas.process.NastekCardProxy.allocateCardChannel
--- message allocating
--- thread Thread[AWT-EventQueue-0,6,main]
--- source br.com.neac.petrobras.medidorgas.process.NastekCardProxy@8f57a
[DEBUG ] opencard.core.service.CardServiceScheduler.allocateCardChannel
--- message applicant br.com.neac.petrobras.medidorgas.process.NastekCardProxy@8f57a
--- thread Thread[AWT-EventQueue-0,6,main]
--- source opencard.core.service.CardServiceScheduler@4ab8b9, is alive
[DEBUG ] opencard.core.service.CardChannel.open
--- message opening CardChannel
--- thread Thread[AWT-EventQueue-0,6,main]
--- source opencard.core.service.CardChannel@9bb457, not open, not jammed
[DEBUG ] br.com.neac.petrobras.medidorgas.process.NastekCardProxy.releaseCardChannel
--- message releasing
--- thread Thread[AWT-EventQueue-0,6,main]
--- source br.com.neac.petrobras.medidorgas.process.NastekCardProxy@8f57a
[DEBUG ] opencard.core.service.CardServiceScheduler.releaseCardChannel
--- message releasing opencard.core.service.CardChannel@9bb457, is open, not jammed
--- thread Thread[AWT-EventQueue-0,6,main]
--- source opencard.core.service.CardServiceScheduler@4ab8b9, is alive
++ channel is allocated
[DEBUG ] opencard.core.service.CardChannel.close
--- message CardChannel closed
--- thread Thread[AWT-EventQueue-0,6,main]
--- source opencard.core.service.CardChannel@9bb457, not open, not jammed
[DEBUG ] opencard.core.service.CardServiceRegistry.getCardServiceInstance
--- message factory [email protected]c68b6f produced br.com.neac.petrobras.medidorgas.process.NastekCardProxy@8f57a
--- thread Thread[AWT-EventQueue-0,6,main]
--- source opencard.core.service.CardServiceRegistry@1f2ae62++ registered factory [email protected]c68b6f
++ registered factory com.ibm.opencard.factory.MFCCardServiceFactory@103368e
++ registered factory opencard.opt.util.PassThruCardServiceFactory@94cc7
++ registered factory [email protected]fa0f0
[DEBUG ] br.com.neac.petrobras.medidorgas.process.NastekCardProxy.allocateCardChannel
--- message allocating
--- thread Thread[AWT-EventQueue-0,6,main]
--- source br.com.neac.petrobras.medidorgas.process.NastekCardProxy@8f57a
[DEBUG ] opencard.core.service.CardServiceScheduler.allocateCardChannel
--- message applicant br.com.neac.petrobras.medidorgas.process.NastekCardProxy@8f57a
--- thread Thread[AWT-EventQueue-0,6,main]
--- source opencard.core.service.CardServiceScheduler@4ab8b9, is alive
[DEBUG ] opencard.core.service.CardChannel.open
--- message opening CardChannel
--- thread Thread[AWT-EventQueue-0,6,main]
--- source opencard.core.service.CardChannel@9bb457, not open, not jammed
[DEBUG ] opencard.opt.applet.BasicAppletCardService.sendCommandAPDU(channel,...)
--- message sending opencard.core.terminal.CommandAPDU@1d92803
0000: 00 20 00 00 00 05 . ....
to <A0 00 00 00 62 03 01 0C 02>
--- thread Thread[AWT-EventQueue-0,6,main]
--- source class opencard.opt.applet.BasicAppletCardService
[DEBUG ] opencard.opt.applet.BasicAppletCardService.selectApplet
--- message selecting A0 00 00 00 62 03 01 0C 02
--- thread Thread[AWT-EventQueue-0,6,main]
--- source class opencard.opt.applet.BasicAppletCardService
[DEBUG ] opencard.opt.applet.ISOAppletSelector.selectApplet
--- message selecting A0 00 00 00 62 03 01 0C 02
--- thread Thread[AWT-EventQueue-0,6,main]
--- source class opencard.opt.applet.ISOAppletSelector
[DEBUG ] opencard.core.service.CardChannel.sendCommandAPDU
--- message opencard.core.terminal.CommandAPDU@1d206f0
0000: 00 A4 04 00 09 A0 00 00 00 62 03 01 0C 02 00 .........b.....
--- thread Thread[AWT-EventQueue-0,6,main]
--- source opencard.core.service.CardChannel@9bb457, is open, not jammed
[DEBUG ] opencard.core.service.CardChannel.response:
--- message opencard.core.terminal.ResponseAPDU@1f23f8b
0000: 90 00 ..
--- thread Thread[AWT-EventQueue-0,6,main]
--- source opencard.core.service.CardChannel@9bb457, is open, not jammed
[DEBUG ] opencard.opt.applet.ISOAppletSelector.selectApplet
--- message Selection response sw = 0x9000
--- thread Thread[AWT-EventQueue-0,6,main]
--- source class opencard.opt.applet.ISOAppletSelector
[DEBUG ] opencard.core.service.CardChannel.sendCommandAPDU
--- message opencard.core.terminal.CommandAPDU@1d92803
0000: 00 20 00 00 00 05 . ....
--- thread Thread[AWT-EventQueue-0,6,main]
--- source opencard.core.service.CardChannel@9bb457, is open, not jammed
[DEBUG ] br.com.neac.petrobras.medidorgas.process.NastekCardProxy.releaseCardChannel
--- message releasing
--- thread Thread[AWT-EventQueue-0,6,main]
--- source br.com.neac.petrobras.medidorgas.process.NastekCardProxy@8f57a
[DEBUG ] opencard.core.service.CardServiceScheduler.releaseCardChannel
--- message releasing opencard.core.service.CardChannel@9bb457, is open, not jammed
--- thread Thread[AWT-EventQueue-0,6,main]
--- source opencard.core.service.CardServiceScheduler@4ab8b9, is alive
++ channel is allocated
[DEBUG ] opencard.core.service.CardChannel.close
--- message CardChannel closed
--- thread Thread[AWT-EventQueue-0,6,main]
--- source opencard.core.service.CardChannel@9bb457, not open, not jammed
opencard.core.terminal.CardTerminalException: Pcsc10CardTerminal: PCSC Exception in method SCardTransmit: error occurred with SCardTransmit
return code = 00000057
at com.ibm.opencard.terminal.pcsc10.Pcsc10CardTerminal.translatePcscException(Pcsc10CardTerminal.java:502)Hello, i really need help.
I'm having the famous return code = 00000057 when i try to send an APDU command, I'm using a applet proxy, so it send an select APDU inside the OCF framework, and the result is success, so i'm able to send an select Applet, but when i try to send the following apdu:
allocateCardChannel();
// Set up the command APDU and send it to the card.
getBalanceAPDU.setLength(0);
getBalanceAPDU.append(MyAPPLET_CLA); // Class
getBalanceAPDU.append(VERIFY_INS); // Instr'n
getBalanceAPDU.append((byte) 0x00); // P1
getBalanceAPDU.append((byte) 0x00); // P2
getBalanceAPDU.append((byte) 0x00); // Lc
getBalanceAPDU.append((byte) 0x05); // Le
// Send command APDU and check the response.
ResponseAPDU response;
//response = new ResponseAPDU(07);
response = sendCommandAPDU(getCardChannel(), MY_CARD_AID,
getBalanceAPDU);
i got that error. I pasted, all the debug message below. I already updated the pcsc-wrapper-2.0.jar file, but i'm still having this error, as i said i'm using an gem pc twin cardreader with gemxpresso card. My opencard.properties file:
# Card service configuration #
OpenCard.services = com.ibm.opencard.factory.MFCCardServiceFactory \
opencard.opt.util.PassThruCardServiceFactory \
br.com.neac.petrobras.medidorgas.process.NastekCardProxyFactory
#OpenCard.services = br.com.neac.petrobras.medidorgas.process.NastekCardProxyFactory
# Card terminal configuration #
#OpenCard.terminals = GemplusCardTerminalFactory
OpenCard.terminals = com.ibm.opencard.terminal.pcsc10.Pcsc10CardTerminalFactory|Autodetect|*|SHARED
#OpenCard.terminals = com.ibm.opencard.terminal.pcsc10.Pcsc10CardTerminalFactory
#OpenCard.terminals=com.ibm.opencard.terminal.pcsc10.Pcsc10CardTerminalFactory|myGEMPlus|GEM430PC|SHARED
# Trace configuration #
OpenCard.trace = opencard:9
----- the debug----
[DEBUG ] opencard.core.service.SmartCard.getRegistryEntry
--- message tag OpenCard.terminals = com.ibm.opencard.terminal.pcsc10.Pcsc10CardTerminalFactory|Autodetect|*|SHARED
--- thread Thread[AWT-EventQueue-0,6,main]
--- source class opencard.core.service.SmartCard
[DEBUG ] opencard.core.terminal.CardTerminal.<init>
--- message (Gemplus USB Smart Card Reader 0, PCSC10, )
--- thread Thread[AWT-EventQueue-0,6,main]
--- source class opencard.core.terminal.CardTerminal
[DEBUG ] opencard.core.event.EventGenerator.updateTerminals
--- message new pollable Terminal = com.ibm.opencard.terminal.pcsc10.Pcsc10CardTerminal@1e1df6e
+ name Gemplus USB Smart Card Reader 0
+ type PCSC10
+ addr
--- thread Thread[AWT-EventQueue-0,6,main]
--- source class opencard.core.event.EventGenerator
[DEBUG ] com.ibm.opencard.terminal.pcsc10.Pcsc10CardTerminal.cardInserted
--- message slotID 0, )
--- thread Thread[AWT-EventQueue-0,6,main]
--- source com.ibm.opencard.terminal.pcsc10.Pcsc10CardTerminal@1e1df6e
+ name Gemplus USB Smart Card Reader 0
+ type PCSC10
+ addr
[DEBUG ] opencard.core.event.EventGenerator.updateCards
--- message card inserted slotID = 0
--- thread Thread[AWT-EventQueue-0,6,main]
--- source class opencard.core.event.EventGenerator
[DEBUG ] opencard.core.service.SmartCard.getRegistryEntry
--- message tag OpenCard.services = com.ibm.opencard.factory.MFCCardServiceFactory opencard.opt.util.PassThruCardServiceFactory br.com.neac.petrobras.medidorgas.process.NastekCardProxyFactory
--- thread Thread[AWT-EventQueue-0,6,main]
--- source class opencard.core.service.SmartCard
[DEBUG ] opencard.core.service.CardServiceFactory.<init>
--- message instantiating
--- thread Thread[AWT-EventQueue-0,6,main]
--- source class opencard.core.service.CardServiceFactory
[DEBUG ] opencard.core.service.CardServiceRegistry.add
--- message com.ibm.opencard.factory.MFCCardServiceFactory@103368e
--- thread Thread[AWT-EventQueue-0,6,main]
--- source opencard.core.service.CardServiceRegistry@1f2ae62++ registered factory [email protected]c68b6f
[DEBUG ] opencard.core.service.CardServiceFactory.<init>
--- message instantiating
--- thread Thread[AWT-EventQueue-0,6,main]
--- source class opencard.core.service.CardServiceFactory
[DEBUG ] opencard.opt.service.OCF11CardServiceFactory.<init>
--- message instantiating
--- thread Thread[AWT-EventQueue-0,6,main]
--- source class opencard.opt.service.OCF11CardServiceFactory
[DEBUG ] opencard.core.service.CardServiceRegistry.add
--- message opencard.opt.util.PassThruCardServiceFactory@94cc7
--- thread Thread[AWT-EventQueue-0,6,main]
--- source opencard.core.service.CardServiceRegistry@1f2ae62++ registered factory [email protected]c68b6f
++ registered factory com.ibm.opencard.factory.MFCCardServiceFactory@103368e
[DEBUG ] opencard.core.service.CardServiceFactory.<init>
--- message instantiating
--- thread Thread[AWT-EventQueue-0,6,main]
--- source class opencard.core.service.CardServiceFactory
[DEBUG ] opencard.core.service.CardServiceRegistry.add
--- message [email protected]fa0f0
--- thread Thread[AWT-EventQueue-0,6,main]
--- source opencard.core.service.CardServiceRegistry@1f2ae62++ registered factory [email protected]c68b6f
++ registered factory com.ibm.opencard.factory.MFCCardServiceFactory@103368e
++ registered factory opencard.opt.util.PassThruCardServiceFactory@94cc7
[DEBUG ] opencard.core.service.SmartCard.<start>
--- message finished
--- thread Thread[AWT-EventQueue-0,6,main]
--- source class opencard.core.service.SmartCard
[DEBUG ] opencard.core.service.CardServiceRegistry.getSmartCard
--- message CTEvent opencard.core.event.CardTerminalEvent[source=com.ibm.opencard.terminal.pcsc10.Pcsc10CardTerminal@1e1df6e
+ name Gemplus USB Smart Card Reader 0
+ type PCSC10
+ addr ]
---source com.ibm.opencard.terminal.pcsc10.Pcsc10CardTerminal@1e1df6e
+ name Gemplus USB Smart Card Reader 0
+ type PCSC10
+ addr
---id 1
card inserted in slot 0
terminal com.ibm.opencard.terminal.pcsc10.Pcsc10CardTerminal@1e1df6e
+ name Gemplus USB Smart Card Reader 0
+ type PCSC10
+ addr
--- thread Thread[AWT-EventQueue-0,6,main]
--- source opencard.core.service.CardServiceRegistry@1f2ae62++ registered factory [email protected]c68b6f
++ registered factory com.ibm.opencard.factory.MFCCardServiceFactory@103368e
++ registered factory opencard.opt.util.PassThruCardServiceFactory@94cc7
++ registered factory [email protected]fa0f0
[DEBUG ] com.ibm.opencard.terminal.pcsc10.Pcsc10CardTerminal.openSlotChannel
--- message for slot #0
--- thread Thread[AWT-EventQueue-0,6,main]
--- source com.ibm.opencard.terminal.pcsc10.Pcsc10CardTerminal@1e1df6e
+ name Gemplus USB Smart Card Reader 0
+ type PCSC10
+ addr
[DEBUG ] com.ibm.opencard.terminal.pcsc10.Pcsc10CardTerminal.openSlotChannel
--- message new SlotChannel is opencard.core.terminal.SlotChannel@182815a
+ state open
--- thread Thread[AWT-EventQueue-0,6,main]
--- source com.ibm.opencard.terminal.pcsc10.Pcsc10CardTerminal@1e1df6e
+ name Gemplus USB Smart Card Reader 0
+ type PCSC10
+ addr
[DEBUG ] opencard.core.service.CardServiceRegistry.allocateCardServiceScheduler
--- message instantiating CardServiceScheduler
--- thread Thread[AWT-EventQueue-0,6,main]
--- source opencard.core.service.CardServiceRegistry@1f2ae62++ registered factory [email protected]c68b6f
++ registered factory com.ibm.opencard.factory.MFCCardServiceFactory@103368e
++ registered factory opencard.opt.util.PassThruCardServiceFactory@94cc7
++ registered factory [email protected]fa0f0
[DEBUG ] opencard.core.service.CardServiceScheduler.<init>
--- message slotChannel opencard.core.terminal.SlotChannel@182815a
+ state open
--- thread Thread[AWT-EventQueue-0,6,main]
--- source class opencard.core.service.CardServiceScheduler
[DEBUG ] opencard.core.service.CardChannel.<init>
--- message (opencard.core.terminal.SlotChannel@182815a
+ state open)
--- thread Thread[AWT-EventQueue-0,6,main]
--- source class opencard.core.service.CardChannel
[DEBUG ] opencard.core.service.CardServiceRegistry.getSmartCard
--- message using CardServiceScheduler opencard.core.service.CardServiceScheduler@4ab8b9, is alive
--- thread Thread[AWT-EventQueue-0,6,main]
--- source opencard.core.service.CardServiceRegistry@1f2ae62++ registered factory [email protected]c68b6f
++ registered factory com.ibm.opencard.factory.MFCCardServiceFactory@103368e
++ registered factory opencard.opt.util.PassThruCardServiceFactory@94cc7
++ registered factory [email protected]fa0f0
[DEBUG ] opencard.core.service.CardServiceScheduler.createSmartCard
--- message creating SmartCard
--- thread Thread[AWT-EventQueue-0,6,main]
--- source opencard.core.service.CardServiceScheduler@4ab8b9, is alive
[DEBUG ] opencard.core.service.SmartCard.<init>
--- message scheduler opencard.core.service.CardServiceScheduler@4ab8b9, is alive, cid opencard.core.terminal.CardID@1a5ba75 ATR: 3B 7D 94 00 00 80 31 80 65 B0 83 01 02 90 83 00
90 00
--- thread Thread[AWT-EventQueue-0,6,main]
--- source class opencard.core.service.SmartCard
[DEBUG ] opencard.core.service.SmartCard.getCardService
--- message (class br.com.neac.petrobras.medidorgas.process.NastekCardProxy)
--- thread Thread[AWT-EventQueue-0,6,main]
--- source opencard.core.service.SmartCard@fb7efa
[DEBUG ] opencard.core.service.CardServiceRegistry.getCardServiceInstance
--- message for class br.com.neac.petrobras.medidorgas.process.NastekCardProxy from opencard.core.service.SmartCard@fb7efa
--- thread Thread[AWT-EventQueue-0,6,main]
--- source opencard.core.service.CardServiceRegistry@1f2ae62++ registered factory [email protected]c68b6f
++ registered factory com.ibm.opencard.factory.MFCCardServiceFactory@103368e
++ registered factory opencard.opt.util.PassThruCardServiceFactory@94cc7
++ registered factory [email protected]fa0f0
[DEBUG ] opencard.core.service.CardServiceRegistry.getCardServiceInstance
--- message checking [email protected]c68b6f
--- thread Thread[AWT-EventQueue-0,6,main]
--- source opencard.core.service.CardServiceRegistry@1f2ae62++ registered factory [email protected]c68b6f
++ registered factory com.ibm.opencard.factory.MFCCardServiceFactory@103368e
++ registered factory opencard.opt.util.PassThruCardServiceFactory@94cc7
++ registered factory [email protected]fa0f0
[DEBUG ] opencard.core.service.CardService.<init>
--- message default constructor of br.com.neac.petrobras.medidorgas.process.NastekCardProxy@8f57a
--- thread Thread[AWT-EventQueue-0,6,main]
--- source class opencard.core.service.CardService
[DEBUG ] opencard.opt.applet.AppletProxy.<init>
--- message (A0 00 00 00 62 03 01 0C 02,opencard.core.service.CardServiceScheduler@4ab8b9, is alive,opencard.core.service.SmartCard@fb7efa,true)
--- thread Thread[AWT-EventQueue-0,6,main]
--- source class opencard.opt.applet.AppletProxy
[DEBUG ] br.com.neac.petrobras.medidorgas.process.NastekCardProxy.initialize
--- message (opencard.core.service.CardServiceScheduler@4ab8b9, is alive,opencard.core.service.SmartCard@fb7efa)
--- thread Thread[AWT-EventQueue-0,6,main]
--- source br.com.neac.petrobras.medidorgas.process.NastekCardProxy@8f57a
[DEBUG ] opencard.opt.applet.BasicAppletCardService.<init>
--- message (opencard.core.service.CardServiceScheduler@4ab8b9, is alive,opencard.core.service.SmartCard@fb7efa,true)
--- thread Thread[AWT-EventQueue-0,6,main]
--- source class opencard.opt.applet.BasicAppletCardService
[DEBUG ] br.com.neac.petrobras.medidorgas.process.NastekCardProxy.allocateCardChannel
--- message allocating
--- thread Thread[AWT-EventQueue-0,6,main]
--- source br.com.neac.petrobras.medidorgas.process.NastekCardProxy@8f57a
[DEBUG ] opencard.core.service.CardServiceScheduler.allocateCardChannel
--- message applicant br.com.neac.petrobras.medidorgas.process.NastekCardProxy@8f57a
--- thread Thread[AWT-EventQueue-0,6,main]
--- source opencard.core.service.CardServiceScheduler@4ab8b9, is alive
[DEBUG ] opencard.core.service.CardChannel.open
--- message opening CardChannel
--- thread Thread[AWT-EventQueue-0,6,main]
--- source opencard.core.service.CardChannel@9bb457, not open, not jammed
BasicAppletCardService - allocated CardChannel()
[DEBUG ] br.com.neac.petrobras.medidorgas.process.NastekCardProxy.releaseCardChannel
--- message releasing
--- thread Thread[AWT-EventQueue-0,6,main]
--- source br.com.neac.petrobras.medidorgas.process.NastekCardProxy@8f57a
[DEBUG ] opencard.core.service.CardServiceScheduler.releaseCardChannel
--- message releasing opencard.core.service.CardChannel@9bb457, is open, not jammed
--- thread Thread[AWT-EventQueue-0,6,main]
--- source opencard.core.service.CardServiceScheduler@4ab8b9, is alive
++ channel is allocated
[DEBUG ] opencard.core.service.CardChannel.close
--- message CardChannel closed
--- thread Thread[AWT-EventQueue-0,6,main]
--- source opencard.core.service.CardChannel@9bb457, not open, not jammed
[DEBUG ] br.com.neac.petrobras.medidorgas.process.NastekCardProxy.allocateCardChannel
--- message allocating
--- thread Thread[AWT-EventQueue-0,6,main]
--- source br.com.neac.petrobras.medidorgas.process.NastekCardProxy@8f57a
[DEBUG ] opencard.core.service.CardServiceScheduler.allocateCardChannel
--- message applicant br.com.neac.petrobras.medidorgas.process.NastekCardProxy@8f57a
--- thread Thread[AWT-EventQueue-0,6,main]
--- source opencard.core.service.CardServiceScheduler@4ab8b9, is alive
[DEBUG ] opencard.core.service.CardChannel.open
--- message opening CardChannel
--- thread Thread[AWT-EventQueue-0,6,main]
--- source opencard.core.service.CardChannel@9bb457, not open, not jammed
[DEBUG ] br.com.neac.petrobras.medidorgas.process.NastekCardProxy.releaseCardChannel
--- message releasing
--- thread Thread[AWT-EventQueue-0,6,main]
--- source br.com.neac.petrobras.medidorgas.process.NastekCardProxy@8f57a
[DEBUG ] opencard.core.service.CardServiceScheduler.releaseCardChannel
--- message releasing opencard.core.service.CardChannel@9bb457, is open, not jammed
--- thread Thread[AWT-EventQueue-0,6,main]
--- source opencard.core.service.CardServiceScheduler@4ab8b9, is alive
++ channel is allocated
[DEBUG ] opencard.core.service.CardChannel.close
--- message CardChannel closed
--- thread Thread[AWT-EventQueue-0,6,main]
--- source opencard.core.service.CardChannel@9bb457, not open, not jammed
[DEBUG ] opencard.core.service.CardServiceRegistry.getCardServiceInstance
--- message factory [email protected]c68b6f produced br.com.neac.petrobras.medidorgas.process.NastekCardProxy@8f57a
--- thread Thread[AWT-EventQueue-0,6,main]
--- source opencard.core.service.CardServiceRegistry@1f2ae62++ registered factory [email protected]c68b6f
++ registered factory com.ibm.opencard.factory.MFCCardServiceFactory@103368e
++ registered factory opencard.opt.util.PassThruCardServiceFactory@94cc7
++ registered factory [email protected]fa0f0
[DEBUG ] br.com.neac.petrobras.medidorgas.process.NastekCardProxy.allocateCardChannel
--- message allocating
--- thread Thread[AWT-EventQueue-0,6,main]
--- source br.com.neac.petrobras.medidorgas.process.NastekCardProxy@8f57a
[DEBUG ] opencard.core.service.CardServiceScheduler.allocateCardChannel
--- message applicant br.com.neac.petrobras.medidorgas.process.NastekCardProxy@8f57a
--- thread Thread[AWT-EventQueue-0,6,main]
--- source opencard.core.service.CardServiceScheduler@4ab8b9, is alive
[DEBUG ] opencard.core.service.CardChannel.open
--- message opening CardChannel
--- thread Thread[AWT-EventQueue-0,6,main]
--- source opencard.core.service.CardChannel@9bb457, not open, not jammed
[DEBUG ] opencard.opt.applet.BasicAppletCardService.sendCommandAPDU(channel,...)
--- message sending opencard.core.terminal.CommandAPDU@1d92803
0000: 00 20 00 00 00 05 . ....
to <A0 00 00 00 62 03 01 0C 02>
--- thread Thread[AWT-EventQueue-0,6,main]
--- source class opencard.opt.applet.BasicAppletCardService
[DEBUG ] opencard.opt.applet.BasicAppletCardService.selectApplet
--- message selecting A0 00 00 00 62 03 01 0C 02
--- thread Thread[AWT-EventQueue-0,6,main]
--- source class opencard.opt.applet.BasicAppletCardService
[DEBUG ] opencard.opt.applet.ISOAppletSelector.selectApplet
--- message selecting A0 00 00 00 62 03 01 0C 02
--- thread Thread[AWT-EventQueue-0,6,main]
--- source class opencard.opt.applet.ISOAppletSelector
[DEBUG ] opencard.core.service.CardChannel.sendCommandAPDU
--- message opencard.core.terminal.CommandAPDU@1d206f0
0000: 00 A4 04 00 09 A0 00 00 00 62 03 01 0C 02 00 .........b.....
--- thread Thread[AWT-EventQueue-0,6,main]
--- source opencard.core.service.CardChannel@9bb457, is open, not jammed
[DEBUG ] opencard.core.service.CardChannel.response:
--- message opencard.core.terminal.ResponseAPDU@1f23f8b
0000: 90 00 ..
--- thread Thread[AWT-EventQueue-0,6,main]
--- source opencard.core.service.CardChannel@9bb457, is open, not jammed
[DEBUG ] opencard.opt.applet.ISOAppletSelector.selectApplet
--- message Selection response sw = 0x9000
--- thread Thread[AWT-EventQueue-0,6,main]
--- source class opencard.opt.applet.ISOAppletSelector
[DEBUG ] opencard.core.service.CardChannel.sendCommandAPDU
--- message opencard.core.terminal.CommandAPDU@1d92803
0000: 00 20 00 00 00 05 . ....
--- thread Thread[AWT-EventQueue-0,6,main]
--- source opencard.core.service.CardChannel@9bb457, is open, not jammed
[DEBUG ] br.com.neac.petrobras.medidorgas.process.NastekCardProxy.releaseCardChannel
--- message releasing
--- thread Thread[AWT-EventQueue-0,6,main]
--- source br.com.neac.petrobras.medidorgas.process.NastekCardProxy@8f57a
[DEBUG ] opencard.core.service.CardServiceScheduler.releaseCardChannel
--- message releasing opencard.core.service.CardChannel@9bb457, is open, not jammed
--- thread Thread[AWT-EventQueue-0,6,main]
--- source opencard.core.service.CardServiceScheduler@4ab8b9, is alive
++ channel is allocated
[DEBUG ] opencard.core.service.CardChannel.close
--- message CardChannel closed
--- thread Thread[AWT-EventQueue-0,6,main]
--- source opencard.core.service.CardChannel@9bb457, not open, not jammed
opencard.core.terminal.CardTerminalException: Pcsc10CardTerminal: PCSC Exception in method SCardTransmit: error occurred with SCardTransmit
return code = 00000057
at com.ibm.opencard.terminal.pcsc10.Pcsc10CardTerminal.translatePcscException(Pcsc10CardTerminal.java:502) -
Help with some strange artifacts - N580GTX Twin Frozr II/OC
hi and firstly thanks for any assistance on my issue
I bought a new N580GTX Twin Frozr II/OC card about a month ago and I have recently noticed some strange artifacts showing up.
Basically, I get light, almost pastel coloured blue and red 'ghosting' in 3d games (eg TF2, RO2), noticeable where the background is dark. They are only noticeble when I move in the environment, but they leave short-lived (perhaps 500ms), thin outlines of the edge of the image on the screen. The image might be the edge of a person graphic or the side of a wall for instance. These artifacts don't show up in 2d screens and the machine I have is perfectly stable.
I've got the latest official nvidia driver (280), don't overclock the unit and have a corsair hx 750 ps. I have read the faq and it suggests upgrading the bios, but considering it's only a few weeks old is there any other thing I should try first?
cheers!Quote from: barkmann on 08-October-11, 06:18:31
Thanks for your assistance Svet.
http://www.mediafire.com/?ecwm7bwfyfow3iv
cheers
BIOS appear to be already latest version. It use different one.
Try to apply VGA reference clocks with Afterburner,
then retest -
"Edit Find" coercion dots, Recommended terminals, empty Description, etc
Are there ways to use LV's automated Find capability to look for any of the following items?
Coercion dots
Connector terminals for which connection is "Recomended"
Controls or VIs for which the Description or Tip is blank
Wires that go behind objects
Wires that graphically are shown touching a terminal but that are not logically connected to it
Objects that logically are inside structures like loops and case statements but that graphically are out of view (beyond the graphical edge of the structure)
Dataflow running right to left on a wire
Variables that are written to in zero places or in more than one place
Controls and nodes whose only output terminal is unwired
Unwired Error Out terminals
I'd like to be able to search through a VI and everything inside its heirarchy for the above things - going through and noticing all their occurances could be good for a project. Some of these are pretty clearly programming errors. Some of them are bad practice, or at least the preference to avoid can be a useful strategy or check. Some of these things are perfectly legitimate to use frequently, but glancing at all the occurances of them gives an opportunity to notice otherwise hard to spot errors. AFAIK LabVIEW doesn't allow searching for them, though it would be able to recognize them.
For any of these, is there a way to Find them?I think that almost all of the items you listed are coverd by the VI Analyzer. It will find and list all of the offenses, let you browse to each case, and produce reports if you would like.
[Set PunMode = True]
It can be customized in the event you think the "out-of-the-box" configuration warrents it being renamed "VI-ANALyzer".
[Set PunMode = Flase]
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction -
MSI GTX 560Ti TWIN FROZR II 1GB GDDR5
Currently I'm experiencing a problem where no matter what I'm doing, whether it is gaming or browsing, green/orange chequered squares appear exactly as in the picture below:
The problem lasts for a matter of seconds and then windows informs me that the drivers have recovered from a failure. This is very remininsant, but not identical, to when I had a 9800GT that died. This issue has only started within the last month and the card is over 6 months old. Is this likely to be a GPU issue?
M4N72-E Windows 7 64 Bit Phenom II X4 950 3.0Ghz
Kingston Hyper-X 1066Mhz CL5 8GB @ 800Mhz CL4
MSI GTX 560Ti TWIN FROZR II 1GB GDDR5
Inno3D GT240 512MB GDDR5 iChill
Sony AD-7240S 24x DVD±RW DL & RAM SATA Optical Drive - OEM Black
Seagate ST3500418AS 500GB Hard Drive SATAII 7200rpm 16MB Cache - OEM
Thermaltake 500W PSUSadly I've no way of testing the card in another PC or a different PSU.
What is the likelihood that it is the PSU even though the card has been performing flawlessly for almost a year? Also I could understand if it was causing artifacts just when gaming due to power load, but it happened when I was merely surfing the net, where power draw doesn't even reach 300W.
Is a known solution to this issue an increase in Watts or is there a chance that it is a problem with the GPU? -
GTX 560 Ti (Twin Frozr II) Temperatures
Hello, I know that temperatures are a 'hot' topic always, especially for the 560 Ti as it is rated 20'C cooler than stock. At the moment I hit a threshold of 92-95'C when playing World of Tanks on 1680x1050, full settings except Anisotropic 8x. The custom fan settings are such that after 70'C the fans are at 100%.
I have only 1 VGA - GTX 560 Ti Twin Frozr II, in an NZXT Tempest 410 Elite case. It has 2x 140mm exhausts (top) 1x 120mm exhaust (back), 3x 120mm intake (2 front, 1 bottom). I can attach pictures if a visual of the setup is needed. I have an excellent wiring setup, there is very little blockage. I also run BOINC and hit high 70s and mid 80s. Most games run in the high 80s.
I've tried Furmark a few times but anything larger than 800x600 maxes temperatures almost immediately (within seconds) and the fans cannot catch up and I stop it before it can set fire to itself. It also makes a loud ringing noise during those tests, so that's not good either.
Is anyone familiar with such high temperatures on a card that is not OC, other than how it came in the box, in a case with lots of airflow, playing games that really shouldn't be hitting that temperature? Also, I've tried testing with the removed side panel, it changes by perhaps +/- 1-2'C.
All help is greatly appreciated, I'd like to know if I have to RMA for faulty thermal paste or just stop worrying about the glowing red boiler in my computer.
Thank you,
KyattoQuote from: Henry on 29-February-12, 07:03:38
Have you re-seated the cooler on it yet with fresh TIM? Some people have done that and got a reduction in temperature and therefore fan speed and noise as well. If that doesn't do any good then RMA the card as it should not get to max temp like that.
I don't have any issues like that on my 560 Ti GE TF ll and currently it's running f@h 66% fan speed, 73C at 99% GPU load, 23C room temp. This is in CM 330 Elite case with 1 front intake, 1 rear exhaust fans both 120mm + PSU fan exhaust. Nothing fancy there and I've never had temperature issues with any MSI (6 in all the past few years & all but 2 with TF ll coolers)
I certainly don't see how replacing all of his case fans would help with his VGA temperature problem.
This is one scenario I feel I can speak with authority on and I bet 100 internet points it doesn't address the issue but there is no harm in doing it.
AS LONG AS YOU ARE GENTLE PULLING THE HEATSINK OFF
You can't just lever it off, you'll need to giggle/spin/twist back and forth a bit. This is because you'll find an ungodly amount of gloop under the heatsink and it provides very strong surface tension.
The reason i ask about the adapter is I got a strange one with the 1st card I got that had to be RMA'd because of the same high temp issue you are having. (it was about 8cm long, and grey)
Initially I thought maybe it was a batch of cards that shipped with that one that were the hot ones, a duff batch.
Ironically I cant use both DVI sockets and the mini hdmi port because the card is not wide enough. The weird grey adapter would sort that issue out so I'm trying to find one. -
MSI GTX 580 Twin Frozr 2/OC Problems
Hey guys, I just build my second new(er) computer (specs below, system 2), with this MSI GTX 580 Twin Frozr 2/OC, and I am having several problems. The first problem I noticed was was in Starcraft 2, I was having major texture stretching (looked like units were stretched across the map, exc.), so I tried a new driver to no avail. I delt with that problem and played for several hours to find that the screen turned black, then recovered (happened several times), which I was able to continue playing after. I went ahead and tried Battlefield Bad Company 2, and noticed the same texture stretching, but with big black shapes (almost looked like large artifacts), so I checked the temps, 74c, so that was not the problem. I continued playing for about 5 minutes before the screen went black, turned white, and the game became unresponsive. Thinking it was a possible PSU problem, I moved the card to my first system (specs below, system 1), and produced the same results.
Does anyone have any ideas, or is it time to RMA the card. Sad thing is, I am seeing alot of people having problems with this card, I hope MSI didn't do me wrong here.... :(
P.s. I flashed the newest BIOS for the VGA and the MoBo.Quote from: doubleohseven on 12-September-11, 06:45:32
Unfortunately it has, and the artifacting only seems to get worse as time goes on (if the card/game doesn't crash right away that is...). I guess RMA'ing is my only option at this point, thanks for your help.
I'll chock it up to a defective card this time, but seeing all the problems with these similar cards from MSI is making me worried... I only hope MSI didn't do me dirty with this product.
No worries, call msi at +1.626.271.1004 within regular business days and they will take care of it -
Linux for single-purpose terminals
Here's a little Arch Linux success story that I feel I need to post somewhere:
I work at a place that oversees public internet access sites (government-funded, for disadvantaged people but anyone can use them), and we're often pressured into making the terminals run Windows "because that's what people are used to." I've about had it with trying to get Windows locked down enough so that people can't set porn wallpaper or change the homepage, but can still save PDF's to the desktop and print them. Securing windows is an adventure in clicking through hundreds of little checkboxes -- it starts with everything allowed, and you selectively turn things off one by one, and hope that Microsoft deigned to make checkboxes for everything.
And then, there's the problem of cloning the install once you've got it all set up just right -- even on identical hardware, you can't just copy the files over and expect it to work. Even after you run the repair CD and use that "fix boot sector" command, usually it still won't boot without a little more fighting, and most of the time a "repair install" is needed. When you've got different motherboards, especially if they're of a different generations (686 vs. one higher), almost nothing is portable.
When I'm not making Windows boxes for these sites, I have sysadmin duties that I often don't work enough hours per week to fulfill. And when an order for "make us some public terminals" comes in, they usually mean "right freaking now" and we don't have time to do anything but fulfill the request the only way we know how, so I don't get time to experiment then, either.
Then the other week, one of my contract clients from my other job (my own business, actually) said, "We need four very simple terminals that act as web browsers for this web-based app our volunteers will use. We want them as cheap as possible, so it'd be great if you could use junk hardware."
So, I finally had a legit excuse to do what I'd always wanted to -- build these things with Linux. I chose Arch because that's what I use at home, so I'm already familiar with it. It's also insanely fast to get it installed and running -- if you use the "quickinst" method, you don't even have to bother with package selection until later. I built the first workstation, then spent a few hours Googling for how to make X auto-login as the limit user, then how to make a custom UI out of FVWM so that all the users had were gigantic buttons called "WWW" "My documents" "Notepad" and "Citrix" and "Help". I found an XP-like theme for FVWM, so that users who've memorized "big red button means close window" will be happy, and learned enough FVWM scripting to have it customized within a couple hours. I found that opera-static (web browser) loads fast enough, even on a Celeron 466 and a really old hard drive.
Then came cloning -- I weeded out as many unnecessary files as I could, and made the root partition only use 780 MB uncompressed. I made tarballs of it and /boot , booted the next blank computer from CD (totally different hardware -- my initial machine was a P4, my clone was that Celeron 466; different hard drives, network cards, video, everything), partitioned it, untarred, changed the hostname and 2 or 3 other little settings, installed grub... and the thing booted perfectly on the second try (the first try was spent switching X drivers). I repeated the process to the other two machines, and had them all working by the end of the day. Oh, and the Linux version of the Citrix client is faster than the native Windows one :)
Four machines with vastly different hardware, running identical setups that (I hope) will be damn near impossible for users to screw up, in one working day. It took me and the staff at my day job months to learn all of the tricks for doing the same thing with Windows, with less adequate results. Now I'll be sharing my linux station tarballs with them, and we can make workstations in less than 10 minutes, rather than 3 or 4 hours, and best of all, no more getting into arguments about licensing (it's become more or less standard practice to use pirated Windows even though we have paid keys for every install, just because it saves us so much hassle -- no WGA, no activation, etc.).thetrivialstuff wrote:no more getting into arguments about licensing (it's become more or less standard practice to use pirated Windows even though we have paid keys for every install, just because it saves us so much hassle -- no WGA, no activation, etc.).
Don't you love it when they shoot themselves in the foot so readily?
Very nice post -
N560GTX-Ti Twin Frozr II/OC Bios request
Given the problems i had with recent nvidia drivers (TDR's, game crashes, pink artifacts etc...), i got stuck with the last 'trouble free' ones whitch are the 10 month old 275.33.
So, assuming that the low factory OC voltages are the culprit, is there a recent bios with higher voltages than the original ones ?
my card:
N560GTX-Ti Twin Frozr II/OC
SN: 602-V238-16SB1101157535
Current Bios: 70.24.0A.00.00 (P1040-0050) http://www.mediafire.com/download.php?bwdoc7r4re5kk7eI know how this is going to sound, but the truth is almost always unpleasant...
I'm not a teenager, i don't have time to test different drivers with all my games, flash video playback, TDR's scenarios etc.. with various voltages to the gpu and gpu ram to reach, by trial end error, a satisfying 'config' (which would also require a reset to MB bios default to eliminate any potential overclocking interference with the GPU (and yes, i do have the same problems with the GPU on MB bios defaults)). And all of this NOT to overclock it further but to bring it to a 'functioning' state on the factory frequences. If MSI software team couldn't get ir right in the first place, it's their job to do further testing and come up with the solution. I'm a newbie to gpu overclocking but i realize that just increasing the core voltage is not enough and oher things need to be taken into account. Damaging components due to overvolting, thus losing my warranty, is not desirable. And in the end, if they already fixed this with a new bios, why would i go to all the trouble myself ?!?
What do i mean by "Also, i wouldn't want to have to apply these voltages every time i start the pc." ? .., i mean that when i last tried it, checking the 'apply OC at startup' box, didn't actually apply OC at startup.. I had to create profiles and apply them myself. Also, i shouldn't have to run afterburner all the time just to ghet the card to work properly.
I appolagise for the long post and the 'tone' of the message. -
MSI GTX580 Twin Froxr III power edition problems.
Hello last night i kinda played around with afterburner and checking it with Kombustor, doing some testing in various benchmarks, at one point it said gpu throttling -3MHz
The card never exceeded 63 degrees C no artifacts at all, so now when i push reset on afterburner it goes to stock settings only kombustor shows throttling -3MHz but at 803-841 on core and 2005-20025 memory it shows no such thing but sometimes oc doesn't seem to get me all that better results, well the highest i got in heaven is 1377 stock 1260 something.
Can i have damaged the card even though it never was getting hot at all?
I am noob at OC but i know something about it and i know as long as i don't meddle with voltage i can+t really burn the card and also i use 70+% fan speed on the card when oc´d/gaming
have i really hurt the card?
since combustor/furmark shows797/800, GPU-Z 800 core afterburner shows 800MHz core 2004 memoryQuote from: flobelix on 03-August-12, 04:37:42
797 to 800, yes. As far as I can see MSI says 800Mhz and not 810Mhz (http://www.msi.com/product/vga/N580GTX-TWIN-FROZR-III-15D5-POWER-EDITION-OC.html)
Yep!
Oh yes, almost no game is currently more stressing than BF3.
so i see now that i looked at that link it shows 800 mybe i looked at another oc´d card adn got mixed up
i also wonder ewhen i raise the clock to say 846 adn memory to 2036 i sometimes get lower rsults on heaven for example than if i just oc it to tiny little 810mhz core and keep memory at 2004 how come it goes that way?
i also wonder there is a bios for my card on MSI website but i do not know if it is newer than the one on the card, it said something about stability
and thank you now i can sleep alot better knowing it is ok :D -
MSI R6950 Twin Frozr III Power Edition – Replacement Heat Sink?
Hello,
Does anyone know of a good 3rd party heat sink that will definitely fit this non reference card? We all know that manufactures such has Artic, Thermalright and Prolimatech make such heat sinks, but of course they are for reference cards. I'm sure you can understand that I don't want to make any expensive mistakes!
Thanks,
Krutish.Thanks for the reply flobelix.
My main concern was the amount of decibels this card produced when pushed, not its thermal properties. Under high stress the card would peak at 80-85c with a fan speed of anywhere around 80-100%. Normal gaming temps would be around 65c-75c depending on game, or gaming environment, with matching fan speeds. That is why I was looking for a replacement, the temps were within the manufactures tolerances, even if a little high, but the db's were well outside of mine!
However, the situation as changed somewhat. While messing around inside the case trying to improve airflow I accidentally touched the heat-sink assembly, and upon doing so the fan instantly roared to 100% and the temps started to shoot up. I wiggled the assembly again and the fan and temps dropped back! So it seemed like the heat-sink was lose! I removed the card and tightened the screws a little, this solved the problem in regards to the temp/fan shooting up, but the temps were still high!
The next step was to completely remove the heat-sink, give it a good clean and replace the thermal compound in the hope that this would solve the noise/heat problem. It was at this point that I spotted the problem! The GPU was absolutely caked in thermal compound, so much so that all of the resistors around the GPU were also covered in thermal grease, (Don't these guys know less is better?) good job they hadn't used a metal based thermal compound, that could have wrecked the card!
Anyway, I removed the mess and used TIM-clean to dissolve what was left and finished the clean up with isopropanol. I applied a small amount of compound, replaced the heat-sink and Bobs your uncle! Max loads so far, GPU 64c – Fan speed 55%... That I can live with!
So there you have it, this card as been noisy and running hot from the day I brought it, but I didn’t know any better, I've never seen or heard a MSI R6950 in action before, now I have!
Made In China. (Sad Face)
Krutish
Oh almost forgot... i heard off Artic, they recommend the Twin Turbo II, Xtreme II or the Xtreme III for this card! -
GTX 760 TWIN FROZR OC showing incorrect clocks?
I'm new here, hi .
Week ago I received a brand new 'GTX 760 TWIN FROZR OC 2 GIG' card.
I understand this card should have 1085 clock and 1150 boost.
The thing I can not understand is why my clocks in GPU-Z are showing different?
See screen shots.
Despite what the above says, boost clock does seem to work, Afterburner shows 1137 mhz in games, not quite the 1150 mhz advertised but almost.
Can someone tell me if this is normal? or have I been given an older revision? I'm sure when I checked the clocks the first day, the clocks were correct, but I could have been mistaken, not sure.
CheersYou have to check the specs of your card. It lists:
1085 (Boost Clock: 1150) (OC mode)
1020 (Boost Clock: 1085) (Gaming mode)
980 (Boost Clock: 1033) (Silent mode)
Quote from: http://www.msi.com/product/vga/N760_TF_2GD5OC.html#overview
Default (even when not using Gaming APP) and if using gaming mode the clockrates are 1020 (Boost Clock: 1085). With good cooling it might boost a bit higher like in your case. Silent and OC mode do require running the >>Gaming APP<< in silent or oc mode.
Alternatively you can manually oc the card.
Maybe you are looking for
-
How can i take the full page off and go back to the regular page
When I go to my to my web pages, I have a full screen. That means I can't see my toolbar.. I would like to see my toolbar at the top at all time.. Can you please help me... Also, I am having trouble with popups all the time.. I downloaded the Ad-bloc
-
Delivery Block Based on Payment Card validity.
Dear SAP Gurus, We are working on a scenario, where in we need to block the delivery based on the payment card validity date, which is given in sales order. The requirement here is, for eg. If a sales order is created during the payment card validity
-
Hi, I am trying to write Custom Code in SSRS for Age Calculation for two requirements in the same report,But report is giving error #Error in expression with my below code. whole logic is same for both but only two lines are different,Do i need creat
-
I've just installed nightly build 4.0.0.9417 and I am getting this error: VerifyError: Error #1053: Illegal override of AdvancedDataGridBaseEx in mx.controls.AdvancedDataGridBaseEx This is the first nightly build SDK I have tried to use so I am wonde
-
Vivado 2015.02 Download Link Not Working
The direct (no download manager) download link for Vivado doesn't work. It is a link to AR #64685