I am currently running Windows Xp with service pack 3 and OpenSuse 11.0 (i586) on the same machine on separate hard drives. I don’t know if it will help with my question but here are the specs on the machine. (Note: it is only a single core machine. I have no idea why both Suse and Windows say it is dual core as the processor was bought and installed months before dual cores went on the market.)
OS Information
OS: Linux 2.6.25.20-0.5-default i686
Current user: telknor@linux-l3e2
System: openSUSE 11.0 (i586)
KDE: 4.0.4 (KDE 4.0.4 >= 20080505) “release 15.4”
Display Info
Vendor: ATI Technologies Inc
Model: Radeon X1300 / X1550 Series (RV515 7146)
Driver: fglrx
CPU Information
Processor (CPU): Intel(R) Pentium(R) 4 CPU 2.80GHz
Speed: 2,799.49 MHz
Cores: 2
Memory Information
Total memory (RAM): 1,009.6 MB
Free memory: 23.8 MB (+ 130.2 MB Caches)
Free swap: 1.9 GB
Disk Information
Device Filesystem Total space Available space Currently used
/home ext3 51.7 GB 8.6 GB 43.1 GB
/ ext3 19.7 GB 16.4 GB 3.3 GB
/windows/C ntfs 232.9 GB 26.3 GB 206.6 GB
Now on to my problem. About a year ago I had to wipe my Windows drive and backed up about 32 GB of stuff from it to my OpenSuse drive. I did this from the Suse OS using Dolphin. In fact I can see, open, change, delete, modify layout, and move stuff around on the Windows drive all day long from Suse. I can as I said pull stuff over to the Suse drive from Windows drive while in Suse and save to Suse drive. Now I have need of the stuff that was moved but Windows does not see the Suse drive for what it is. Just says ‘unknown partion type’ gives size in GB and ignores it otherwise. From Suse if I try to move stuff back to the Windows drive it starts to transfer then stops and tells me it does not have permission to access the destination drive, folder, or location depending on how I tried to save it to the Windows drive. Adding new hard drives to the system does not help and the external 1 TB drive we have Suse can see it but will not do anything with it. The thumb drives on the other hand Suse does not have a problem with. It will open, read, and write to them all day long. Suse will not access the network to dump files to the network file server and it does not see any other systems on the network not even the ones running the same OS. I want to do the following:
Move the Windows files from the Suse drive to the Windows drive in same machine or to the network file server (also a windows machine)
Move all the Suse files to another machine running same Suse OS.
Wipe the Suse drive in this Machine so that Windows can use it.
If there is more info needed to help fix the problem please ask. I have been trying to solve this problem for about six months now the last five and a half of them without internet access.
The problem you are having is that you can move files form Windows to Linux partitions because Suse can read the NTFS partition. Thus you were able to copy your data over.
Putting the data back requires you mount the windows partition in read / write mode. This requires you use a file system drive that supports this, which should not be an issue with newer versions of Suse as it come built in.
From a command line, type ‘mount’ and see what it shows. Is the Windows partition show ro or rw? If it is not mounted, try mounting it with something like:
Callandor:~ # mount -t ntfs-3g /dev/sdb1 /mnt
You can also format a drive as vfat, which BOTH windows and Suse can read. This is a very easy way to move files between the two OSes.
Lastly, you can certainly move the files between two Suse computers. If they are networked together, and you have SSH running on them, you can directly open the destination computer in Dolphin using the fish protocol. For the location, just use: fish://user@host
Also, try entering remote:/ in the Dolphin location bar, and see if it recognizes any of the other systems.
telknor@linux-l3e2:~> mount
/dev/sdb2 on / type ext3 (rw,acl,user_xattr)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
debugfs on /sys/kernel/debug type debugfs (rw)
udev on /dev type tmpfs (rw)
devpts on /dev/pts type devpts (rw,mode=0620,gid=5)
/dev/sdb3 on /home type ext3 (rw,acl,user_xattr)
/dev/sda1 on /windows/C type fuseblk (rw,noexec,nosuid,nodev,allow_other,default_permissions,blksize=4096)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
securityfs on /sys/kernel/security type securityfs (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
telknor@linux-l3e2:~>
As to which drives are which. The /Home and / are both the Suse and the /windows/C is the Windows one as Suse sees it. I know that the bulk of the information for Suse stuff is in the /Home dir but the / dir also shows most of the same files and some that the /home dir does not. They both have links to /Windows/C and the main system page has link to all three. Also I just noticed in the Windows disk manager that Windows shows three drive dir in the Suse drive all I am assuming are ext3 as Windows can’t read them. Suse only shows the first two and not the third. Since the Suse drive is only 80 GB total size and the three shown in Windows equal that as do the only two shown in Suse I have to assume that there is an error in the way Windows is seeing the Suse drive. However the cat /etc/fstab command also shows three drive dir for the Suse drive. Before I use the mount -t ntfs-3g /dev/sdb1 /mnt command line I want to know what all the stuff the terminal just spit out means. Suse is new to me.
Ok I have modified the windows line as instructed caf4926 and rebooted the system in Suse then as a test I moved one file from the windows files on the Suse drive to the Windows drive in the desktop folder. I then rebooted in Windows and the moved file is present on the desktop and fully accessible. I do believe the problem to be fixed unless you can think of anything else.
Once again, Thank you for your time. As to the help/how-to files on the forums. I looked there for the ‘how to transfer from Suse to Windows.’ But did not think to look there for simple terminal command. Sorry about that.
Telknor
PS: I love the Avatar caf4926. Certainly how I feel about Windows at times.