EverQuest2.exe- No Disk

[Trax]

I am receiving (EverQuest2.exe- No Disk popup box)

just says: There is no disk in the drive. Please insdert a disk into drive\Device\Harddisk2\DR2.

This is the first time I have ever seen this prompt after today's patch.

Anyone else running Windows 7 o.s. have this problem?

 

[Hendrix]

EQ2 has NEVER required a disk to play...

 

[ClassicCoke]

I've been getting this error a lot too lately.

No idea what the source of the message actually is; EQ2, isxeq2, or something else.


ClassicCoke

 

[pz]

i see it rarely (not recently) and usually end up throwing my hands up in the air and cursing and rebooting.

 

[Kevinshp]

i see it rarely (not recently) and usually end up throwing my hands up in the air and cursing and rebooting.

Primalz I can't picture you cursing!

 

[Trax]

This is the popup message and No idea what's causing the problem.

 

[Kannkor]

It may be my age.. but I can't see shit in that little picture...

 

[Trax]

Oops my Apologies! Let's try this again.

 

[Kannkor]

uhh.. yea. Never seen that one before.. so I'm of no help.

 

[Amadeus]

I'd delete everything and reinstall both EQ2, Innerspace, and ISXEQ2 ..in that order ...using the TRADITIONAL EQ2 client (not the streaming client.)

 

[bob_the_builder]

http://forums.station.sony.com/eq2/posts/list.m?topic_id=479290


We've received a few calls on this and making sure you are launching our LaunchPad as an Admin has been helping alleviate the issue. If you already have run as admin set, unset it, apply, and reset it. Do the same for any antivirus or firewall exceptions. This includes automatically set exceptions if you've ever received a Deny/Allow box when you ran our LaunchPad for the first time. For that, open Windows Firewall and remove the EQ2 exception. It will prompt you again when you launch it.

 

[Trax]

Thanks all for the feedback.

I delete everything and reinstall both EQ2, Innerspace, and ISXEQ2.

Problem fixed!

 

[Nuprecon]

I got this same issue on the 9th, I just repatched eq2 using the "patch day" method and it got rid of the problem...