The "Freeola Customer Forum" forum, which includes Retro Game Reviews, has been archived and is now read-only. You cannot post here or create a new thread or review on this forum.
Here's what happens:
I boot up, it loads normally. Scandisk comes up (naturally), but at the end it says it can't write to C:syslog.txt, possibly due to lack of space. However, I know I have 308mb left. Then, it continues and asks me to log on. I have never logged on before, so I just press "enter" or "cancel", and it continues as before. At this point it went through the new hardware thing once. Then, it just freezes. When i do ctrl+alt+delete, I have Rnaapp running and Msgrs32 (I think) which is "not responding". Then I have to turn it off at the plug, and the process repeats.
Possible causes:
Well, I ran it with VMware a few times, so this is my prime suspect at the moment. Something else could be that I ran a chmod on the whole drive. The weird thing is, it took ages and worked, even though Fat32 filesystems blatently don't support these permissions. Now, I think my kernel is storing these permissions but still, it could have corrupted it or something. Note I can still read the drive from Linux.
So, if anyone has any ideas, let me know. Getting Windows up isn't a priority, but getting my Dad's address is, so alternatively if anyone knows how I can extract this from the Address Book that'd be great. Cheers.
Turbo has actually *gasp* caused a computer problem!!
Here's what happens:
I boot up, it loads normally. Scandisk comes up (naturally), but at the end it says it can't write to C:syslog.txt, possibly due to lack of space. However, I know I have 308mb left. Then, it continues and asks me to log on. I have never logged on before, so I just press "enter" or "cancel", and it continues as before. At this point it went through the new hardware thing once. Then, it just freezes. When i do ctrl+alt+delete, I have Rnaapp running and Msgrs32 (I think) which is "not responding". Then I have to turn it off at the plug, and the process repeats.
Possible causes:
Well, I ran it with VMware a few times, so this is my prime suspect at the moment. Something else could be that I ran a chmod on the whole drive. The weird thing is, it took ages and worked, even though Fat32 filesystems blatently don't support these permissions. Now, I think my kernel is storing these permissions but still, it could have corrupted it or something. Note I can still read the drive from Linux.
So, if anyone has any ideas, let me know. Getting Windows up isn't a priority, but getting my Dad's address is, so alternatively if anyone knows how I can extract this from the Address Book that'd be great. Cheers.