The configuration file: 'gs.conf' configuration supplements: the 'gsalias.conf'
Failed to initialize the data of 100 Treasure House
The first step is initialization failed, error: -31
by Google
translated and yes I have been searching.
Printable View
The configuration file: 'gs.conf' configuration supplements: the 'gsalias.conf'
Failed to initialize the data of 100 Treasure House
The first step is initialization failed, error: -31
by Google
translated and yes I have been searching.
Im almost done testing everything soon il post all the results with wht works and what does not work
Good job :thumbup:
This tutorial works fine with new Ubuntu 12.04 LTS (in test )
I used vmware 7.0.0 and ubuntu 12.04 and everything ok
about Memory how many need to run all maps at same time and like 10 users?
omg ... fail !!!
http://forum.ragezone.com/f755/required-specs-826651/
i have a problem mounting the server image
here is a screenshot of the problem:
http://imageshack.us/photo/my-images/189/serverdg.jpg/
or here
http://img189.imageshack.us/img189/497/serverdg.jpg
Uploaded with ImageShack.us
I used daemon tools to make a virtual cd drive and mount the image there and put your vmware on auto detect on the cdrom and it should work .
kk tnx i'll try it
No offense, but I am going to make an example out of you:
This is the perfect example of how GOOGLE is your friend. This question is truly (technically) NOT related to PW in any way shape or form. This would be Linux itself that you're having a problem with. Looking > HERE < (which is the result from the GOOGLE search tearm "/dev/cdrom does not exist"). Which would be the error message you received from Linux > HERE <
Anywhoot, to answer your question:
For whatever reason the symbolic link that is normally associated with your 'cdrom' device upon installation of Linux is missing.
To correct this you can 'call it' by the actual device 'name' or you can create a 'symbolic link' so that you can refer to it as 'cdrom' in the future.
[example]{taken from link I have provided for you}
Code:Run 'dmesg', and find the line that mentions your DVD rom drive. It will
tell which device it is. Typically /dev/hdb, or hdc or hdd.
Once you've determined that, make a link, using 'ln -s'.
For example:
For me, dmesg shows this line:
hdc: _NEC DV-5700A, ATAPI CD/DVD-ROM drive
as root, run:
ln -s /dev/hdc /dev/cdrom
ln -s /dev/hdc /dev/dvd
The second link is optional, but many programs use it, so I recommend it.
Hope this helps, and I hope that everyone can learn something from this response :wink:Spoiler:
Add: BTW, (I just noticed your current post count [of 4]), Welcome to RZ :D:
Not really, because this 'problem' is in Linux ('inside' a [guest] VM at that) he could mount it 100 different ways from Friday and the symbolic link for /dev/cdrom will still not exist. It wouldn't matter if he mounted in his host OS as a "real drive" (using something like PowerISO or Daemon tools), it wouldn't matter if he physically burned the disc and then sat it in the tray of the optical drive of his host os, etc... ... The only 'true' way to "fix" this is to add the symbolic link for /dev/cdrom :wink: