Z68A-GD80 (G3) and Port 7/esata port

Hallo everyone, please give me a little help here, I have a Z68A-GD80 (G3) MB and I connected a hard drive er 2 or 5 how and sata port 1 -> 6 is running 100% ok but port 7 doesn't show and I have a drive connected also if I connect a external drive to the Esata port it doesn't show. I installed the marvell 88SE9128 drivers bit no sata controller shows. I have the intel side set to raid mode because I have striped volume with ssd enhanced acceleration option on it does this make a difference to the marvell side ? how do I get the marvell port 7 and esata to show and work ?

Sometimes the Drive Letter for the device your trying to plug in is trying to use the same letter of another drive currently in use for example D: drive or F: drive etc if you goto the drive management see if your drive shows up there and if it shows an error you can right click the drive letter or Volume and allocate(change) the letter to one that is not in use. maybe this will work i had similar issue with an previous computer, and as Always if you do not know what you are doing then dont do it , i am not responsible for any mistakes that you may cause. Hope this helps if your comfortable doing so!
02/01/12 3:22 P.M. Edit: btw this may not fix your issue worth the look into!
1. Click the Windows Start Orb and then Right-Click Computer and Click Manage from the context menu.
access the device manager from windows 7 start menu
2. Click Storage > Disk Management from the left panel. Next Right-Click the drive letter that you would like to change and Click Change Drive Letter and Paths…
use the disk management feature to enter the change drive letter dialog in windows 7
3. Select the drive letter you would like to change then Click Change. In the pop-up dialog use the drop-down box to Select a new drive letter. Click OK to save and exit both windows.
assign a new drive letter to your windows 7 hard disk
Now your drive should have the new letter you just assigned to it.

Similar Messages

MSI Z68A-GD80-G3 sata port 7 marvell controlled not showing in BIOS

My spec is..Antec 1200 case. MSI Z68A-GD80-G3 board . i7 -2700K @4.1 GHZ. GTX 580 OC twin FrozR II 1536 Mb Graphics.Corsair Vengeance 16 GB PC3-12800C9 1600MHz RAM. Cooler Master Hyper 212+ CPU cooler. Crucial SSD M4 128 GB SATA 6Gb/s main Hard drive.Crucial SSD M4 128GB hard drive. 500 GB HDD. Crucial SSD M4 60GB.1200W PSU.
My 3rd 60 GB SSD drive had to be plugged in sata 7..I reformatted It in windows and it is working. It does still not show up on BIOS.
I could not find my install disc. I couldnt find any marvell drivers in the download section for my board?
Has windows found them? why no show in BIOS?

I may have found correct drivers now SATA 7 drive is showing up. seems to be running . my ssds running off SATA 1 and 2 are getting a AS SSD bench mark score of 710 and 780. The SATA 7 one is scoring at 340 so it is not working like the first x2 SDD's.

Problematic Motherboard MSI Z68a GD80 (B3) and bad customer service

I opened a support ticket at MSI's support site (http://support.msi.com/index.php?mod=questions&dop=reply_list&question_no=102573) and still waiting for a response since last week. Not only that, but there is no way you can talk to customer support and you can only submit tickets online. What if your PC is not working because of the MSI motherboard? How is then the customer able to talk to customer support?! eh!!!?!?!???
To describe the issues I experience I will copy-paste some of the info from my existing support ticket....
Recently I noticed that my new PC's performance degraded considerably, without me having made any changes to its settings, software or hardware. After extensive testing I realised that the RAM was faulty so I replaced it with new DIMMs which I tested again and work correctly. However after replacing with new RAM (memeory is in the "approved" list of the motherboard) the PC's performance is still very slow, especially when it comes to hard disk access. So I tested all, memory, hard disks (checkdisk, defrag, and also used WesternDigital utilities to check all disks) and all tests came back fine. I also checked all BIOS settings and re-installed all Motherboard drivers to ensure that the issue was not due to a damaged driver file. But none made a difference. So given that everything appears to be working correctly and all tests for individual components come back as normal, I uspect that it's the motherboard to blame.
In addition to the above the PC has now started behaving strange too: when rebooting pc restarts..and then turns off and then on again and off again. ...or it restarts but then does not boot at all. Just now i turned it off and then on again and the pc behaves as if it boots up but nothing is showing on the screen. not even the bios.
Once, when i turned on the PC and when logged into windows I got a popup saying "you have booted from your second BIOS rom. Please update your BIOS using Live Update". I then went to live update and it said i am running the latest BIOS.
The issues exist also outside the OS. I also tried to boot from Norton Ghost DVD and take a backup from there and see the backup speed (which normally takes an hour). It took 2-7 times more, depending on the PC's "mood". I also tried booting from a DVD into Windows PE (pre-installation environment) and tried to take a disk backup from there too. Same issue everywhere.
I did various tests with Western Digital to eliminate the hard disk, and all come out fine. I even formatted the hard drive (low level format) and reinstalled a fresh OS. The problem was still there and the mouse pointed would stutter when the disk was active.
Another thing I noticed which might help: sometimes disk to pc/disk-over-network file copying works at a reasonable speed. But local-disk to local-disk copying is very slow and affects the mouse pointer and overall pc performance.
I use this PC for business so it's critical that this is fixed asap or that I am sent a replacement motherboard promptly before I send this one back so that I am not left without a working PC.
Any suggestions?
My spec:
   * CPU brand, model and speed: Intel i7 i2600K 2.5 GHz
   * Motherboard model: MSI Z68a GD80 (B3)
   * Memory brand, type/speed, size, number of sticks: Kingston KHX1333C9D3B1K2/4G (2 sticks x 2 Gb each. total of 4gb)
   * Video card brand, chipset type, memory size: XFX 7600GT 256MB
   * Hard drive(s) brand, size, type, speed: Westerd Digital Velociraptor 600Gb
   * Operating system and version (including if 32 or 64bit!): Windows XP SP3 32bit
   * Power Supply Unit brand and output in watts and DC output (amps) - OCZ 650W

Quote
Well on the MSI UK website that is the only support which is listed for motherboards! Global or not, that's the one listed there.
Yes, I know. But there is an E-Mail Contact listed for RMA procedures. When you go to the Global support site:
http://ocss.msi.com.tw/
... you'll find the same E-Mail contact address listed under the heading
Quote
If you live in the following country and have any request about RMA, please go to Online RMA Request:
Quote
Ok, I will contact both the reseller and send an email to the email address you mentioned and see what happens.
Quote
In fact the reseller has an online system specifically for returns and as per UK distant selling regulations their system does not accept any returns and won't allow you to make a returns request after 28 days from the date of purchase. ..and given that I've been dealing with these issues for 10-14 days weeks now I am not sure they will allow a returns request. But I will contact them and see what they will say.
Yes, contact them.
Quote
But have a look at the returns policy anyway: http://www.ebuyer.com/help/returns#1
Look:
Quote
Items Faulty in Warranty Period
If any of your purchases develop a fault, and it's more than 28 calendar days since receipt, then provided your item is within its warranty period, you are entitled to a warranty repair.
... more:
http://static.ebuyer.com/customer/help/index.html?action=c2hvd190ZXJtcw==&type=personal
Quote
9. Our refunds policy
9.1 When you return a Product to us:
   9.1.2 for any other reason (for instance, because you have notified us in accordance with clause 21 that you do not agree to any change in these terms and conditions or in any of our policies, or because you claim that the Product is defective), we will examine the returned Product and if you are entitled, we will notify you of your options to either repair, replace or refund via e-mail within a reasonable period of time. We will usually process your elected repair, replacement or refund as soon as possible and, in any case, within 30 days of the day you confirm whether you opt for repair, replacement or refund for the defective Product. If you elect a refund of a Product returned by you because of a defect it will be refunded as per our refunds policy, including a refund of the part of the delivery charge which related to that defective Product for sending the item to you and the cost incurred by returning the defective Product to us. If you elect a repair or replacement of a defective Product we will not charge you for redelivery of the repaired or replaced Product.
   9.1.3 If you elect to return the defective Product to us using your own method of delivery, we will refund up to £4.00 of the costs incurred by you. This will only be refunded upon the receipt of proof of the carriage costs.
Just for your record:
Quote
and still waiting for a response since last week.
MSI Technical Support has responded to you giving you the following advice:
Quote
Dear sir/madam
Thanks for contacting MSI technical support.
Regarding your concern,if the issue appears when loading windows,we suggest you reinstall your os for a try.If it appears when post,we have to suggest you contact your reseller (The place you bought this MB from) and have them test the MB completely for you to check if this MB is faulty or not, then ask for some help.
If the reseller for some reason cannot help, we have to ask you to contact MSI distributor or MSI office near your place to seek further help.
Thanks for your cooperation in advance!
Best Regards,
MSI Technical Support Team
... and as I said before, this is precisely the next logical step in your situation.

MSI Z68A-GD80 (B3) and (G3) intel vt-d support?

Hello guys,
I would like some information....
the MSI motherboard Z68A-GD80 (G3) or (B3) in both its variants supports Intel VT-d?
I am thinking of buying a 2600 I7....
Thanks in advance!

It shows in CPU Features submenu on the Z68A-GD80(B3), so would expect it to be included in the (G3) as well. Download the pdf manual from the Global Website for the (G3) & have a look.

MSI Z68A-GD80(G3) and Corsair's New RAM

Yeah, ok, it all looks great, but how do they work together outside of a test laboratory in a real world home built pc?
That question was answered very quickly, without any special fiddling about required beyond normal setting changes.
When the Corsair kit was installed, the usual 'Memory Has Changed' screen popped up. No big deal, a simple check in the UEFI/BIOS looked like everything defaulted to ensure a successful post and bootup. Yup, that's exactly what took place. Corsair took the right approach IMO to set the profile to default to DDR3 1333. At the next restart, it was a simple matter to set the manufacturer's recommended rated speed of 2133, CR 1, 9 11 10 27, tRFC 171 on Auto DRAM V. Posted and booted right up.
Yeah, ok, how about if 8GB isn't enough RAM for me?
Figured that might be a question asked. Here is the finding. To make it more real, often pc builders buy components at different times. This can be problematic, but that is best discussed on a case by case basis. Back to the answer. Purchased on purpose a kit from a different batch, even the serial numbers were way apart. After they were installed, the usual 'Mem. Change' screen again, but at F10 - Enter, it posted and booted right up! No increase of DRAM V. was required. In fact, with it set to Auto, the 'Read Only' actually shows the voltage to be 1.472v's (by meter, it was just below 1.50v's).
Note that CPU-Z X.M.P. for this RAM shows wrong. In the UEFI/BIOS, Memory-Z, it shows correctly.
Conclusion? I would say MSI mainboards and this RAM are going to work out just fine together.

Quote from: Bernhard on 14-September-12, 11:14:44
That formula may be a good rule of thumb, or may have worked with DDR and DDR2, but looking at JEDEC standard 1333, that would already be out. 9.9.9.24 is the standard. that would mean the 24 should be 20, which it's not. Maybe for OC'ing it may be an indicator of how far you can tighten them
These are all tweaks that probably cannot be realised anywhere else but in benchmarks and tests as performed here.
But its nice to compare similar or the same memory on similar platforms and see how close the performance figures are, yet highlight also how they differ, even at the same settings. Good to see for newbie OC'ers that even at the same settings, no two rigs will ever be the same.
That makes sense, since I tried to look the article up again (from Mushkin actually), and the article appears to be so old, they took it down.
It is quite surprising how close our bench results really are! It is also interesting how different systems with the same memory react to timings. Learned some good things in this thread, and once again, glad I made the purchase!
Quote from: Froggy Gremlin on 14-September-12, 11:52:12
Wanted to thank all for contributing to this thread. I have most definately learned some things.

Experiences about Z68A-GD80 (G3) and firewire?

Hi,
have someone tried to connect an external firewire audio production interface using the integrated VIA VT6308P? is it good or there are latency, disconnections or other issues.
I'm a bit worried about the PCI to PCIe bridge that is used to internal connect the VT6308P and the PCI slots to the motherboard.
Maybe even if you haven't used a music firewire interface can you share your experiences using an internal audio PCI (not PCIe) card (again have you tried it at lower latencies using some music production software).PCI slots are also connected using the same PCI to PCIe bridge so them could also give an idea if this bridge is good or not.
many thanks to all

Sometimes the Drive Letter for the device your trying to plug in is trying to use the same letter of another drive currently in use for example D: drive or F: drive etc if you goto the drive management see if your drive shows up there and if it shows an error you can right click the drive letter or Volume and allocate(change) the letter to one that is not in use. maybe this will work i had similar issue with an previous computer, and as Always if you do not know what you are doing then dont do it , i am not responsible for any mistakes that you may cause. Hope this helps if your comfortable doing so!
02/01/12 3:22 P.M. Edit: btw this may not fix your issue worth the look into!
1. Click the Windows Start Orb and then Right-Click Computer and Click Manage from the context menu.
access the device manager from windows 7 start menu
2. Click Storage > Disk Management from the left panel. Next Right-Click the drive letter that you would like to change and Click Change Drive Letter and Paths…
use the disk management feature to enter the change drive letter dialog in windows 7
3. Select the drive letter you would like to change then Click Change. In the pop-up dialog use the drop-down box to Select a new drive letter. Click OK to save and exit both windows.
assign a new drive letter to your windows 7 hard disk
Now your drive should have the new letter you just assigned to it.

Z68A-GD80 Memory Choices

I've got an MSI Z68A-GD80 board and an i7 2600k that I plan on running but I'd also like to run 16GB of RAM and I'm having trouble finding it in a kit. I did find this Corsair Vengeance Blu 16 GB PC3-12800 1600mHz DDR3 240-Pin SDRAM Dual Channel Memory Kit for Intel and AMD Platforms CMZ16GX3M4A1600C9B and was wondering if anyone has used this particular kit or is there another option?

Another update that's not so good. Everything was running fine until yesterday late in the afternoon. I had been messing around with an RC Flight training program for about an hour. Everything was still humming right along so I was scrounging around the web when I got the hated BSOD and it shut down my entire system. I figured okay no problem just power it back up and things would be fine. It didn't work that way, now it was trying to start but like many it just kept shutting down and coming back on, all it would do is just loop. Having limited use of my hands I had to wait until I could get someone to help me get into the case. I cleared the CMOS but that didn't work, still looping. I had my aide pull a couple pieces of the Corsair Vengeance out dropping it down to 8GB and tried starting it, well that worked it fired right up and went straight to the desktop. The RAM had dropped back to the default settings so I went back and enabled the XMP profile and with just the two 4GB sticks it started up without any trouble. I then went and added a third stick to see if it would boot and it did but I had stayed away from the dimm slot number 2. As soon as I placed the last stick in and hit the power it went right back to the looping without getting anything at all to show up on my display. So I pulled dimm 2 and dimm 4 out and it booted right up. Then I spent a couple of hours trying each stick in each dimm since I had help to change them. Everytime I put a stick into dimm 2 even by itself it would just go back to the looping. I ended up just using dimm 1 and dimm 3 and it is running now since I'm using it to post this. I have no idea which direction to turn now. I did manage to save the error message that Windows presented me with when I got it running the first time with just dimm 1 and 3 populated.
Here is what it was telling me:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional information about the problem:
BCCode: 50
BCP1: FFFFF900C6A965E8
BCP2: 0000000000000000
BCP3: FFFFF9600016325F
BCP4: 0000000000000002
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1
Files that help describe the problem:
C:\Windows\Minidump\071711-12292-01.dmp
C:\Users\Burnard\AppData\Local\Temp\WER-51651-0.sysdata.xml
I'm not sure what it all means and searching for the files wasn't much help. I did notice one thing, when there are just two sticks installed and the XMP enabled the voltage is running at 1.5 compared to the 1.64 it was at when all the dimms were populated and working normally. Now I'm left scratching my head, is the board bad, or my PSU an 850w Corsair unit not getting me enough juice, or my CPU an i7 2600k messed up in some way or bad memory.

Z68A-GD80 DVI Port Woes

I've been having problems (like many others) getting the on board DVI port to work. I've done some testing and here is what I've found.
My monitor is an ASUS VE247H.
A direct connection between the DVI port of the mainboard and my monitor results in no output. Monitor gives a "no signal" message. A single link or dual link DVI cable yields the same result. There is no difference between the two.
A DVI to HDMI adapter connected to the HDMI input of the monitor works.
A DVI to VGA adapter connected to the VGA input of the monitor works.
An HDMI to HDMI connection from mainboard to monitor also works.
Monitor worked with my previous PC connected via DVI. Monitor also works with Z68A-GD80 and a discrete card connected via DVI. That should rule out the monitor being the issue.
At this point I figured the DVI port was just faulty. I have already received a call from MSI, after discussing my DVI problems in a Newegg review, and was instructed to RMA the board back to Newegg for a replacement. Before taking everything apart, I decided to try the only other "monitor" available to me with a DVI input, my Samsung DLP TV (model#HLP4663WX/XAA). So I directly connected the mainboard to the TV (DVI to DVI), with a single link DVI cable and amazingly, that worked.
This leads me to believe there is definitely some issue with the way the BIOS handles communication to/from the monitor, and not just a faulty DVI socket.
Another observation I've made, the same monitor is detected differently depending on what interface is being used. For instance, when I connect via HDMI, the Intel Graphics and Media Control Panel shows my display as "Digital Television VE247".
If I connect with VGA, the display shows up as "Monitor VE247".
Hopefully this is of some use to MSI. We really need these port issues fixed.

Quote from: owcraftsman on 11-June-11, 00:40:06
Have you tried a HDMI connection with the Asus VE247H? The reason I ask is the DVI-D connection "D" meaning Dual with that monitor may not be compatible with the Single link out put of the motherboard. You would think it's backward compatible but maybe not. I hope this helps you avoid an RMA GL
Yes, I tried every connection I could to the monitor. Straight HDMI from board to display worked. Using the DVI port on the board and some adapters, DVI -> HDMI (worked), DVI -> VGA (worked), DVI -> DVI (doesn't work).
And FYI, in DVI-D, the "D" is for DIGITAL not dual. The mainboard has a DVI-I port, the "I" meaning integrated. It supports both digital (DVI) and analog (VGA) connections from the same port.
Quote from: HU16E on 11-June-11, 02:34:35
Not really sure if this may be a possible factor or not, our board HDMI port is compliant v1.4, maybe an issue with the backwards compatibility with v1.3 devices & cables? After everyone contacts & opens a ticket with MSI Tech Support, please be sure to post their response.
AFAIK, the monitor is HDMI v1.3 compliant, the cable I'm using definitely is. I have no problems with an HDMI connection though. Either straight HDMI from board to monitor, or DVI port on board -> DVI to HDMI adapter -> HDMI cable to monitor. I've contacted support with my results thus far and linked them to this thread as well. Their reply "Ok, thank you for the update. I will look further into this and update you as further information becomes available."
I've RMA'd the board back to newegg for a replacement and will repeat this process when I get it back (probably another week). I even went as far as to try one of the beta BIOSes before RMAing, no improvement there.

Visual Voicemail gone after upgrade to 2.0 (and porting number)

Anyone else experience this? I upgraded to 2.0 and at the same time I ported the old iPhone to another cell phone number on my account with ATT. The upgrade to 2.0 and porting appeared to go OK as everything else is working EXCEPT when on the phone application, I can not get the visual voicemail button to do anything. I press it and it acts like it is taking some time to open but it never brings up the visual voicemail screen. The phone part works as usual in all other ways.

I upgraded to the pre-release version of 2.0 and it worked fine. Then this morning i tried to update to the official 2.0 and it could not connect to iTunes, and that pinwheel kept spinning. So I pressed home button and power button until it (iPhone) rebooted. Then i connected it to iTunes and it asked me to restore.... So i pressed the option key (in mac, idk what it is in windows) and selected the prerelease version to downgrade to and now its fine. So...... good luck all

Coherence::net::messaging::ConnectionException: could not establish a connection to one of the following addresses: {10.242.152.242/10.242.152.242:8088}; make sure the "remote-addresses" configuration element contains an address and port of a running TcpA

Hi
I have installed coheI have installed coherence server "fmw_12.1.3.0.0_coherence_Disk1_1of1.zip" along with Examples on windows machine and C++ client coherence-cpp-12.1.3.0.0b51709-windows-x86-vs2012.zip on the same machine.
I have built the "contacts" C++ Example successfully and while I execute this "contacts" using run I am facing TcpAcceptor error.
On my coherence server the TcpAcceptor is listening on port 8088, so I have modified the extend-cache-config.xml file with values "ip address of my windows machine" and port as "8088".
All the time I am getting below error,
coherence::net::messaging::ConnectionException: could not establish a connection to one of the following addresses: {10.242.152.242/10.242.152.242:8088}; make sure the "remote-addresses" configuration element contains an address and port of a running TcpAcceptor
    at class coherence::lang::TypedHandle<class coherence::component::net::extend::PofConnection> __thiscall coherence::component::util::TcpInitiator::openConne
ction(void)(TcpInitiator.cpp:307)
    at coherence::component::util::TcpInitiator::openConnection
    at coherence::component::util::Initiator::ensureConnection
    at coherence::component::net::extend::RemoteCacheService::openChannel
    at coherence::component::net::extend::RemoteService::doStart
    at coherence::component::net::extend::RemoteService::start
    at coherence::component::util::SafeService::startService
    at coherence::component::util::SafeService::restartService
    at coherence::component::util::SafeService::ensureRunningServiceInternal
    at coherence::component::util::SafeService::start
    at coherence::net::DefaultConfigurableCacheFactory::configureService
    at coherence::net::DefaultConfigurableCacheFactory::ensureService
    at coherence::net::DefaultConfigurableCacheFactory::ensureRemoteCache
    at coherence::net::DefaultConfigurableCacheFactory::configureCache
    at coherence::net::DefaultConfigurableCacheFactory::ensureCache
    at coherence::net::CacheFactory::getCache
    at unsigned __int64 coherence::lang::class_spec<class coherence::lang::Managed<class ContactId>,class coherence::lang::extends<class coherence::lang::Object,class coherence::lang::Void<class coherence::lang::Object> >,class coherence::lang::implements<void,void,void,void,void,void,void,void,void,void,void,void,void,void,void,void> >::sizeOf(bool)
    at _onexit
    at class coherence::util::Hashtable * coherence::lang::factory<class coherence::util::Hashtable>::create(void)
    at class coherence::util::Hashtable * coherence::lang::factory<class coherence::util::Hashtable>::create(void)
    at BaseThreadInitThunk
    at RtlInitializeExceptionChain
    at RtlInitializeExceptionChain
    on thread "main"
Caused by: coherence::net::messaging::ConnectionException: coherence::component::util::TcpInitiator::TcpConnection@029EAD78{Id=NULL, Open=1, LocalAddress=NULL,
RemoteAddress=10.242.152.242/10.242.152.242:8088}: socket disconnect
    at class coherence::lang::TypedHandle<class coherence::net::messaging::Response> __thiscall coherence::component::net::extend::AbstractPofRequest::Status::g
etResponse(void)(AbstractPofRequest.cpp:203)
    at coherence::component::net::extend::AbstractPofRequest::Status::getResponse
    at coherence::component::net::extend::AbstractPofRequest::Status::waitForResponse
    at coherence::component::util::Initiator::openConnection
    at coherence::component::net::extend::PofConnection::open
    at coherence::component::util::TcpInitiator::openConnection
    at coherence::component::util::Initiator::ensureConnection
    at coherence::component::net::extend::RemoteCacheService::openChannel
    at coherence::component::net::extend::RemoteService::doStart
    at coherence::component::net::extend::RemoteService::start
    at coherence::component::util::SafeService::startService
    at coherence::component::util::SafeService::restartService
    at coherence::component::util::SafeService::ensureRunningServiceInternal
    at coherence::component::util::SafeService::start
    at coherence::net::DefaultConfigurableCacheFactory::configureService
    at coherence::net::DefaultConfigurableCacheFactory::ensureService
    at coherence::net::DefaultConfigurableCacheFactory::ensureRemoteCache
    at coherence::net::DefaultConfigurableCacheFactory::configureCache
    at coherence::net::DefaultConfigurableCacheFactory::ensureCache
    at coherence::net::CacheFactory::getCache
    at unsigned __int64 coherence::lang::class_spec<class coherence::lang::Managed<class ContactId>,class coherence::lang::extends<class coherence::lang::Object
,class coherence::lang::Void<class coherence::lang::Object> >,class coherence::lang::implements<void,void,void,void,void,void,void,void,void,void,void,void,void
,void,void,void> >::sizeOf(bool)
    at _onexit
    at class coherence::util::Hashtable * coherence::lang::factory<class coherence::util::Hashtable>::create(void)
    at class coherence::util::Hashtable * coherence::lang::factory<class coherence::util::Hashtable>::create(void)
    at BaseThreadInitThunk
    at RtlInitializeExceptionChain
    at RtlInitializeExceptionChain
    on thread "main"
Caused by: coherence::io::IOException: socket disconnect
    at unsigned int __thiscall coherence::net::Socket::readInternal(unsigned char *,unsigned int)(Socket.cpp:333)
    at coherence::net::Socket::readInternal
    at coherence::net::Socket::SocketInput::read
    at coherence::io::BufferedInputStream::fillBuffer
    at coherence::io::BufferedInputStream::read
    at coherence::component::util::TcpInitiator::readMessageLength
    at coherence::component::util::TcpInitiator::TcpConnection::TcpReader::onNotify
    at coherence::component::util::Daemon::run
    at coherence::lang::Thread::run
    on thread "ExtendTcpCacheService:coherence::component::util::TcpInitiator:coherence::component::util::TcpInitiator::TcpConnection::TcpReader"

We are facing same issue.    Could you please provide us any working .Net sample code for the version 12.1.2.0.
<ssl>
              <protocol>Tls</protocol>
              <local-certificates>
                <certificate>
                  <url>c:\Cert\</url>
                  <password>password</password>
                  <flags>DefaultKeySet</flags>
                </certificate>
              </local-certificates>
            </ssl>
thanks
Bala

How to determine which IP address and port is used to make DNS queries?

I am using JNDI/DNS API to query a Enum server (Tel URI resolution in VOIP world) what is a DNS server.
But I have many network interfaces, in a VLAN environment, and I must to specify from which interface (and port)
all the requests are sent.
When I read the code of JNDI/DNS API (in JDK 1.5) and specially the DNSClient class, I can see that the
DatagramSocket is created without parameters... : udpSocket = new DatagramSocket();
How can I specify the IP address and port to use for my client???
Thanks for your help.

I must to specify from which interface (and port) all the requests are sent. You don't have to specify the interface unless your static unicast routing tables are incorrect, and you never have to specify the port unless some lunatic is in control of your firewall.

FF keeps defaulting to the wrong HTTP proxy server and port. I have to change it every time I attempt to open Firefox? How do I change it for good?

The manual proxy settings keep defaulting to the wrong HTTP and port. This has caused me many hours of anguish. It works fine when I correct the settings but after you log off and then come back it has to be changed again. Is there anyway to fix it? Or can I go back to the previous version because 4 definitely has some issues (other than this one). I could live with it if I had to but I'm not the only one who uses this computer and they don't know how to make the changes. Thanks and I would definitely appreciate an answer.

See:
* http://kb.mozillazine.org/Preferences_not_saved
Start Firefox in <u>[[Safe Mode]]</u> to check if one of the extensions is causing the problem (switch to the DEFAULT theme: Firefox (Tools) > Add-ons > Appearance/Themes).
* Don't make any changes on the Safe mode start window.
* https://support.mozilla.com/kb/Safe+Mode
* https://support.mozilla.com/kb/Troubleshooting+extensions+and+themes

Web Service Proxy with Dynamic IP and Port

hi,
I am currently looking at the Web Service Proxy generation in JDev 11g. I can generate proxies fine, but the proxies are generated with static host and port. I want to substitute the host and port during runtime if required, for instance read the values from a database. I need to do this to avoid compiling the application for every deployment we make dev, test and production. Is there an easy way to set the generated proxy host and port? Are there any examples?
Thanks in advance!
Stephen

Hi,
Maybe you should have a look on XML Catalogs feature, but I am not sure if JDeveloper support it and how to support it.
-LJ

Z68A-GD80 B3 Boot Loop and Failed BIOS LED Flashing

I've been having "boot loop" issues with my system since it was built in June. Basically, when the system is powered on the lights/fans come on for around 3 seconds then it shuts itself off for another 3 seconds and repeats the loop infinitely. Meanwhile there are no POST code beeps and nothing shows up on screen. I also noticed today that the Dual BIOS control LED is flashing during boot loops indicating that the primary BIOS has failed.
As this was my first build in quite a while I didn't initially worry about it too much, figuring that it was probably just a BIOS setting or improperly seated hardware issue. Shortly there after my son was born and needless to say there wasn't a whole lot of time to trouble shoot a PC for a couple of months. Fast forward four months later to today and the boot looping is driving me nuts. It seems to occur when the system has been powered down overnight and more frequently if the reset button is used. I've read a lot of stuff saying that the Gigabyte boards are prone to this issue, but can't find anyone else with the same issue on a MSI z68 board. I've check/done the following to try and trouble shoot the issue.
1. Flash to BIOS 17.3 (twice)
2. Installed system speaker to hear post codes. Got a whole lot of nothing.
3. Installed one stick of RAM in slot one. Tried all four sticks. Nothing works.
4. Set BIOS values to default.
5. Tried disabling and enabling XMP profiles for the RAM.
6. Upped the voltage on the RAM to 1.5V, since the board reports an under-volt around 1.48 on auto. No effect.
7. Disabled PLL overvolt.
8. Enabled VDroop (still not clear on what this is).
9. Removed both video cards and used the on chip video. No effect.
10. Unplugged all USB devices.
11. Tried XMP enabled and disabled for the memory.
12. Hard drive plugged in and removed makes no difference.
13. Bare system with only one stick of RAM installed, no difference.
11. Lots of other crap that I can't think of right now.
Any help would be great as I'm at a loss here.
System specs are as follows;
Intel 2600K
Corsair H50 Cooler
MSI z68a-gd80 B3 with BIOS v 17.3
PNY Geforce GTX 560 Ti (2x in SLI)
Linksys Wireless G PCI card
Crucial Ballistix Sport RAM (4x2GB at 1600 MHz XMP enabled)
Segate Barracuda 7200 RPM Drive 500GB (2x in RAID0)
OCZ Vertex2 64 GB SSD as system cache
Corsair TX750 Power Supply
Corsair 600t case

More wierd stuff.
I couldn't get the board to boot without looping last night, tried the usual unplugging and clearing the CMOS nothing. Boot loops at every turn.
I wonder if maybe I've got some bad pins or a poor connection on my RAM slots. I removed the RAM and began testing one by one. First stick gave a boot loop. Second stick worked. On restart the BIOS LED wasn't flashing anymore, which is odd since I hadn't yet set the BIOS fix feature to enabled. I powered down again and put my RAM back in, set my BIOS settings as suggested, and then clocked the RAM to 1333MHz. Seemed stable last night through a number of restarts.
As for the backup BIOS reporting v 17.3. Yeah, that is odd. The manual says it can't be flashed either. Maybe BIOS just reports what the primary version number is no matter which chip (primary or secondary) is actually active and being booted from?
I'd like to think this is over, but I'm sure when I go home and power up I'll get another boot loop. I'd rather not be without a PC for a couple weeks, but I may just have to RMA so I don't have to deal with this anymore. It's quite frustrating to have fiddle around for 10+ minutes to get your PC up and running, plus with a RAID0 setup and SSD cache I'm just asking for a system failure with all these power on/off cycles.

Xbox 360/one problem and port forwarding

For a couple months now (since I got my AirPort Extreme) I have not been able to connect to a certain friend on xbox. I can connect to anybody else however. The only way we can (kind of) connect is if somebody else is host and we both connect to him.
My NAT type is Moderate. When I try to test my connection on my xbox it says that I can connect but I am limited in matchmaking (this is joining games and using voice chat, which is the problem named above for my particular friend). The xbox shows the error and suggests that I enable UPnP or open the port 3074.
The problem is that I have already have! I gave my xbox a static IP and forwarded the port 3074 to that IP.
(I have also tried forwarding all the ports that xbox live uses to the xbox. These being:
Port 88 (UDP)
Port 3074 (UDP and TCP)
Port 53 (UDP and TCP)
Port 80 (TCP)
as found on the xbox website... https://support.xbox.com/en-US/xbox-360/networking/network-ports-used-xbox-live
I made sure to put them in the right text boxes for UDP and TCP so that is not the problem either.)
I know that the AirPort Extreme does not support UPnP but does have a similar thing called NAT Port Mapping Protocol which was already enabled. (I tried all possibilities of enabling/disabling NAT...Protocol and port forwarding/not port forwarding.) --- This is not the solution as I see it
In short: My xbox tells me to open port 3074. I already have. It still tells me to open it and still won't work.
I posted this on the apple discussion page (instead of the xbox discussion page) because I know that it's not an xbox problem. When I had my old linksys router it worked perfectly.

I have this exact same question and problem. I know this doesn't help, but would appreciate any updated information if you find an answer. I'll keep working on this also and let you know if I find an anwer.

Z68A-GD80 (G3) and Port 7/esata port

Similar Messages

Maybe you are looking for