Forum: Poser - OFFICIAL


Subject: Space Helmet Prop-No Disk Problem

Philywebrider opened this issue on Nov 28, 2004 ยท 15 posts


Philywebrider posted Sun, 28 November 2004 at 5:40 PM

I purchased a Space Helmet Prop, but I can't get it to load. I install it in poser, but when I try to load it from the library I get the following message; "No disk in drive/please insert a disk into drive/device/harddisk2/dr4" Then every thing locks up, and I have to shut down Poser. I tried reinstalling several times. but everytime I try to load from the library, I get the same "no Disk in Drive message" and it locks up. Any idea what the problem might be? Am I doing something wrong?


Ajax posted Sun, 28 November 2004 at 7:11 PM

Sounds like a bad texture reference or geometry reference. Hogwarden's Correct Referrence Pro will probably fix it for you, but really you should contact the maker so they can fix it for all of their customers.


View Ajax's Gallery - View Ajax's Freestuff - View Ajax's Store - Send Ajax a message


Philywebrider posted Sun, 28 November 2004 at 7:53 PM

I had sent an e-mail to the vender, I just haven't heard from him yet. I posted here because I thought maybe I was doing something wrong. Hogwarden's Correct Reference Pro? I'll look it up.


Ajax posted Sun, 28 November 2004 at 9:59 PM

CR Pro is a very useful program if you have a big runtime. It can improve object load times quite a lot by making sure Poser looks in the right place for textures first time. Of course, you could always just open the prop in a text editor and search for "harddisk2:dr4". Then you could correct the file path for whichever file is causing the problem.


View Ajax's Gallery - View Ajax's Freestuff - View Ajax's Store - Send Ajax a message


Huolong posted Sun, 28 November 2004 at 11:33 PM

I always run CorrectReference against all new downloads from the unzipped directory with the texture files properly placed before moving any library item into the library. You would be surprised how many references folks make in their library items that aren't on your default drive

Gordon


Philywebrider posted Mon, 29 November 2004 at 4:44 AM

I just checked CorrectReference, and it looks like a good program, but it's $35.00. I can't afford to put out $35.00 to get a $15.00 item working. I realize CR would be/could be useful later, but the Space Helmet is the ONLY problem I had so far, and I feel it shouldn't cost me money, (I can't afford to spend now), to get it working. I have a PC with XP, 1.5 gig of ram, and a 450 gig hard drive. I've installled Poser items before I installed the Helmet, and after I installed the Helmet, and none of the other items had a problem... none of them, so I don't think it is a virius that affects only the one prop file. I just want a item that works for me.


Philywebrider posted Mon, 29 November 2004 at 5:10 AM

I got a reply; About 30 people have bought the helmet and no one has reported a similar problem. He said Sounds to him like I have a serious hardware or operating system issue going on with my PC. Maybe a virus. He's pretty sure it has nothing to do with the prop. He asked much memory do I have, what OS. The bitmaps for the prop are pretty big. He suggested I might not have enough memory or even bad memory. He mentioned theres a way to test the prop files. If I have microsoft word on your system then go to the directory on your hard drive where the prop is installed. Open the prop file. If it loads in word then its not the file. If it doesnt, then my system is underpowered or there is a memory or hardware problem or a virus. I got garbage when I opened the prop folder in Word. He Also suggested I open up the bitmap images supplied with the prop. I opened the bit map without any problem. He said, Hope I was of some help, and I do appreicate his suggestions, but I'm getting into deep water. This tech stuff is over my head and I'm getting lost. Are there any other suggestions? :O(


Ajax posted Mon, 29 November 2004 at 5:23 AM

You could try the free version of CR Pro. It's called "Correct Referrence" and you should be able to find it in the free stuff area. That should fix it if it's a bad texture reference, but it won't fix bad geometry referrences IIRC.


View Ajax's Gallery - View Ajax's Freestuff - View Ajax's Store - Send Ajax a message


Ajax posted Mon, 29 November 2004 at 5:26 AM

BTW, I very much doubt this is a hardware/OS/Virus issue. I really think it's a bad reference of some sort.


View Ajax's Gallery - View Ajax's Freestuff - View Ajax's Store - Send Ajax a message


randym77 posted Mon, 29 November 2004 at 8:17 AM

Could it be a corrupt download? If opening the prop file in a text editor gave you "garbage," it sounds like more than a bad reference. Can you download the file again?


jentron posted Mon, 29 November 2004 at 11:05 AM

Phily, Are you using a Mac?


Philywebrider posted Mon, 29 November 2004 at 11:30 AM

jentron-I have a PC with XP, 1.5 gig of ram, and a 450 gig hard drive. (see posting 6) randym77-I deleted everything on my hard drive, and redownloaded the file. I deleted everything from poser and reinstalled the Space Helmet. I still have the "No Disc in drive message"


randym77 posted Mon, 29 November 2004 at 11:44 AM

I get that error message regularly. In my case, it's related to Quicktime. (The software from hell, if you ask me.) Not sure what causes it; some kind of conflict, possibly with a USB device. Removing and reinstalling Quicktime may help. Me, I just disable Quicktime when I'm not using it. (By unchecking the qtask.exe under msconfig.)


Huolong posted Mon, 29 November 2004 at 12:19 PM

Attached Link: http://www.hogsoft.com/catalog/

The free version of CorrectReference is at Hogsoft. Don't use Poser without it. Your loading and render times in P5 depend very much on how much you apply CorrectReference to your library items The Pro version checks for more things than just text files

Gordon


randym77 posted Thu, 02 December 2004 at 1:38 PM

Attached Link: http://www.renderosity.com/messages.ez?ForumID=12356&Form.ShowMessage=2028530

Phily, do you have a Zip drive?

That could be the problem. (See linked thread.)