dual boot

philipsyyy · 09-16-2002, 12:09 PM

I have intsalled win98 and RedHat 6.1 (kernel 2.2.x) on my harddrive. Quite often, two systems seem acces the other's partition, some files got messed up by the other system.
I have tried take 65% of HD for the windows and 30% for linux and leave 5% for free space. This does not saeem resolve the problem.
There is another thing I suspect: I Have 256M RAM, I only have
abouy 70M for swap partition, is that could be a problem?
Thanks for you help.
Philips

nautilus_1987 · 09-16-2002, 12:50 PM

philipsyyy, If you have 256 RAM, such swap partition is quite OK.
I have 128MB, and as I can see swap (256MB) is used very seldomly

If you have two different partitions, files shouldn't mess up

Half_Elf · 09-16-2002, 01:56 PM

I don't think Linux can corrupt Fat32 files BUT your kernel seems really old. Maybe you should upgrade to a newer (safer) one?

(and I don't think windoze access your redhat files... windoze supports only fat and fat32 so...)

born4linux · 09-16-2002, 05:35 PM

did you just resize the partitions? I recommend a complete repartition and that these partitions be created first under Red Hat's fdisk (even with the Windows FAT partition).

I still have some test machines here with 6.x and LILO still works out fine.

You can install Linux first (allot the first partition for Windows), create a bootdisk, install Windows and then boot into Linux using the bootdisk and then edit /etc/lilo.conf and then re-install it in the MBR:

/sbin/lilo -v

philipsyyy · 09-16-2002, 05:55 PM

Quote:

Originally posted by Half_Elf
I don't think Linux can corrupt Fat32 files BUT your kernel seems really old. Maybe you should upgrade to a newer (safer) one?
Just copy a portion from my word document under windows to show how they corrept each other:

ÿu j èÛÄÿÿ‹]üÉÃU‰åS»äñ ƒ=äñ ÿt
‹ ÿÐƒÃüƒ;ÿuô‹]üÉÃU‰åÉÃU‰åSè [Ã¯& èÆÿÿ‹]üÉÃ œË —Ë Ë always auto never •Í a ŽÍ b ˆÍ f Í € uÍ i pÍ l aÍ d QÍ x IÍ P DÍ P ;Í p 1Í R *Í S Í s Í u
Í v ýÌ V øÌ Üô ðÌ àô version help version-control verbose update symbolic-link suffix recursive preserve path parents one-file-system no-dereference link interactive sparse force backup archive Try `%s --help' for more information.
Usage: %s [OPTION]... SOURCE DEST
or: %s [OPTION]... SOURCE... DIRECTORY
Copy SOURCE to DEST, or multiple SOURCE(s) to DIRECTORY.

-a, --archive same as -dpR
-b, --backup make backup before removal
-d, --no-dereference preserve links
-f, --force remove existing destinations, never prompt
-i, --interactive prompt before overwrite
-l, --link link files instead of copying
-p, --preserve preserve file attributes if possible
-P, --parents append source path to DIRECTORY
-r copy recursively, non-directories as files
--sparse=WHEN control creation of sparse files
-R, --recursive copy directories recursively
-s, --symbolic-link make symbolic links instead of copying
-S, --suffix=SUFFIX override the usual backup suffix
-u, --update copy only when the SOURCE file is newer
than the destination file or when the
destination file is missing
-v, --verbose explain what is being done
-V, --version-control=WORD override the usual version control
-x, --one-file-system stay on this file system
--help display this help and exit
--version output version information and exit

By default, sparse SOURCE files are detected by a crude heuristic and the
corresponding DEST file is made sparse as well. That is the behavior
selected by --sparse=auto. Specify --sparse=always to create a sparse DEST
file whenever the SOURCE file contains a long enough sequence of zero bytes.
Use --sparse=never to inhibit creation of sparse files.

The backup suffix is ~, unless set with SIMPLE_BACKUP_SUFFIX. The
version control may be set with VERSION_CONTROL, values are:

t, numbered make numbered backups
nil, existing numbered if numbered backups exist, simple otherwise
never, simple always make simple backups

As a special case, cp makes a backup of SOURCE when the force and backup
options are given and SOURCE and DEST are the same name for an existing,
regular file.

Report bugs to <bug-fileutils@gnu.org>. %s preserving times for %s preserving ownership for %s preserving permissions for %s cannot make directory `%s' `%s' exists but is not a directory missing file arguments missing destination file virtual memory exhausted %s -> %s
.. when preserving paths, last argument must be a directory copying multiple files, but last argument (%s) is not a directory /usr/share/locale fileutils SIMPLE_BACKUP_SUFFIX VERSION_CONTROL abdfilprsuvxPRS:V: sparse type 4.0 GNU fileutils cp (%s) %s
cannot make both hard and symbolic links ¢¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ¢ ˜¢ 2¢ €¢ ˜¢ ˜¢ ¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ q¡ ¡ ˜¢ °¡ ˜¢ À¡ ˜¢ ˜¢ Ó¡ ˜¢ ˜¢ æ¡ ˜¢ ˜¢ ˜¢ ò¡ ˜¢ "¢ B¢ ˜¢ P¢ `¢ ˜¢ p¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ˜¢ ÷ %s virtual memory exhausted `%s' and `%s' are the same file cannot create regular file `%s' %s: omitting directory %s: cannot overwrite directory with non-directory %s: overwrite `%s', overriding mode %04o? %s: overwrite

(and I don't think windoze access your redhat files... windoze supports only fat and fat32 so...)

philipsyyy · 09-16-2002, 05:58 PM

[QUOTE]Originally posted by born4linux
[B]did you just resize the partitions?

I did not resize them. I delete one of unused extended dos partition to free the space and then installed the RedHat linux.

Half_Elf · 09-17-2002, 09:28 AM

Do you try to open the .doc files under RedHat? Maybe the prog you are using to open win .doc document does not support your version of Word very well. Or do you have the right code paging? Also,If you have enabled a different codepaging, Linux can not be able to correctly open the files.

Also, I repeat, Red Hat will NOT play on your Fat32 partition unless you ask him to do. If you haven't open the corrupted .doc under Linux before you noticed of damage in it (under Windoze), it's not the linux fault. Maybe you have a virus? or there are something wrong with your office/word suit?