Ryzom

read through it didnt understand much of the image creating by the burning tool software tbh

archerke wrote:read through it didnt understand much of the image creating by the burning tool software tbh

you dont need to make a bootable CD.. you can also boot up in DOS (if you have a win 98 boot diskette) and then run the program from another diskette http://www.memtest86.com/memt32.zip

The program itself is very small, and the bootable CD is just to make things easier for all (if you have any burning software at all, you are able to make a cd from an ISO). An ISO is like an image of the content of a cd... so all information needed + the content of the cd, is stored in one file, ready to instruct the burning software what to burn.

rasmus wrote:you dont need to make a bootable CD.. you can also boot up in DOS (if you have a win 98 boot diskette) and then run the program from another diskette http://www.memtest86.com/memt32.zip

The program itself is very small, and the bootable CD is just to make things easier for all (if you have any burning software at all, you are able to make a cd from an ISO). An ISO is like an image of the content of a cd... so all information needed + the content of the cd, is stored in one file, ready to instruct the burning software what to burn.

this is all to freekin complicated for me and nay i dont have all that stuff, its with my supplier. comp i all i have

now when it occurs again i'll just pull 1 of my 2 rams out (got one of 512 and one of 1k) and see if i can connect with 1 of the 2 (should be doable?) this should sort out if its a problem with my ram wouldnt it?

archerke wrote:this is all to freekin complicated for me and nay i dont have all that stuff, its with my supplier. comp i all i have

now when it occurs again i'll just pull 1 of my 2 rams out (got one of 512 and one of 1k) and see if i can connect with 1 of the 2 (should be doable?) this should sort out if its a problem with my ram wouldnt it?

Yes.. that way you would see if one of them is faulty (im currently only having 756 mb instead of 1024 Mb ). But you might want to cut all power from the PC before doing so

Edit: I just realized that even in in windows XP it is possible to make a MS-DOS boot diskette.
From Microsoft Windows:
1: Insert a floppy disk into your computer's floppy drive.
2: Open My Computer, and then click the floppy disk drive to select it.
3: On the File menu, point to the name of the floppy drive, and then click Format.
4: Under Format options, click Create an MS-DOS startup disk.
5: Click Start.

rasmus wrote:Yes.. that way you would see if one of them is faulty (im currently only having 756 mb instead of 1024 Mb ). But you might want to cut all power from the PC before doing so

yeah otherwise it goes in biiep mode

archerke wrote:Access Violation exception generated at 0x67DC5D (i get this messega after my select carracter screen while loggin in)

Hi archerke,

this alone is not very helpful... From the sentence in the error message AFTER the part you posted (for example: "The thread attempted to read from or write to a virtual address for which it does not have the appropriate access.") you can quite often see what causes your problem...

Would be nice to see a little bit more of the error message next time
You might even post the complete message, sometimes there's a useful hint near the end of the debug messages. If you can't get the clue what they mean, I'm pretty sure one of the techies here can...;D

if you need a boot disk then go here http://www.bootdisk.com/bootdisk.htm

download, put disk in drive, double click and away you go


if you want a translation of what it says on the memtest86 website

"download the file you want
unzip it
burn it with your burning program
reboot with cd in the drive"


not sure how to say this without sounding a bit harsh, so here goes. if you don't understand the words look them up http://dictionary.reference.com is a free service

since the last reinstall i didnt have any problems anymore, though i think i'm pushing my luck now lolz.

and i will post the whole message if it occurs again