Hi,
I have a laptop with AMD processor and 2 GB of RAM. I had Windows XP installed on it. Recently I downloaded Open SUSE 11 with KDE 4 and installed on it. Installation went through fine. After installation when I login to Windows I get the Blue Screen. Note, the windows booting completes and I am shown the desktop. After that even if I don’t do any thing still I get the blue screen. Any idea what can I try out?
Also I noticed my laptop had 3 drives C, D and E (E with the maximum amount of free space). I am not able to access C and D drive if I log in to SUSE. Any thing wrong with the Wine?
Did you let suse shrink windows? And if so, did you do a defrag in windows before hand?
[Arindam] Yes, I let Suse shirnk the windows partition. Before the installation the free space in all the drives were as follows: C (8 GB), D (10 GB) and E(21 GB).
Before starting the installation I did not do a defrag. I just disabled the virtual memory in windows.
Your post isn’t too clear in explaining what happens. Can you actually use windows?
[Arindam] I am not able to use windows. Previously in the boot menu if I selected Windows it will boot in windows and complete the boot sequence and show me the desktop. Then before I could do any thing with in few seconds it will show the blue screen. Currently if I select Windows while booting it dows not even show the screen saying loading windows.
Wine has nothing to do with access to drives.
[Arindam] Any idea then why I am not able to access C and D drive from SUSE, though I am able to access E drive contents.
Give us the output from a su terminal
[Arindam] I am not sure how to do this. Could you please elaborate.
I have important data in the windows drive and I am scared of loosing them. Any thing that I can do to protect them?
Thanks again
Device Boot Start End Blocks Id System
/dev/sda1 * 1 3824 30716248+ 7 HPFS/NTFS
/dev/sda2 3825 19456 125564040 f W95 Ext’d (LBA)
/dev/sda5 3825 11473 61440561 7 HPFS/NTFS
/dev/sda6 11474 17443 47945992 7 HPFS/NTFS
/dev/sda7 17443 17668 1815313+ 82 Linux swap/Solaris
/dev/sda8 17669 18447 6257286 83 Linux
/dev/sda9 18448 19456 81046761 83 Linux
I tried accessing the C and D drive from My computer,but was unsuccessful. I noticed for E drive my computer shows the amount of total space and the free space available. But for C and D drive it does not show the Free space available.
I went throw the manual pages provided by you. When I try to mount c drive using the mount command I get the following output:
mount /dev/sda1
$LogFile indicates unclean shutdown(0, 0)
Failed to Mmount ‘/dev/sda1’: Operation not supported.
Mount is denied because NTFS is marked to be in use.
If I’m not mistaken, the ntfs-3g driver overlooks the “dirty bit” set in the volume label because that in reality means “do a filesystem check”. The “dirty bit” which means there has been a crash thus invoking recovery from the logfile, is set in the logfile itself. This logfile is checked by the driver. Consequently, when the driver reports as it does above, it means there was a crash; this probably occurred at the BSOD. The volume can be mounted with ntfs-3g using the force option (-o force); note that this will clear the logfile altogether. If the Windows problem occurred soon after startup, as appears to be the case, then it is highly unlikely that the logfile contained anything important needing to be recovered. The OP should run chkdisk later however to repair any broken chains in the filesystem which usually occurs with a crash. Mounting the first partition in openSUSE may be necessary to make a backup of the Windows “Documents and Settings”, where most users store their data; apparently there is also a need to do so with data on the “D” volume, which it looks like openSUSE moved to sda5.
I suggest considering using YaST to restore the Windows MBR boot code. I notice that the first partition is still marked active, so if the boot sector is intact then that should work. Or alternatively, use YaST to install “generic boot code” which should do the same. Then OP can concentrate on dealing with whatever caused the BSOD. As you know, afterward it will be trivial to re-install grub to the MBR using the DVD.
. . .