Original CD won't 'restore' system ??

[Robert Macy]

During bootup came up with error message about running original disk
and restore from that.

Inserted disk, booted from CD, system downloaded many programs and
then presented a screen with 3 choices.

Install
restore
escape


The 'r' key did NOTHING!

Hitting escape to exit did NOTHING

Had to pull power to reboot, and comes back with same message

Upon executing the sequence of insert disk, select 'r', still nothing
happens and have to power off.

Any ideas?

 

[Paul]

During bootup came up with error message about running original disk
and restore from that.

Inserted disk, booted from CD, system downloaded many programs and
then presented a screen with 3 choices.

Install
restore
escape


The 'r' key did NOTHING!

Hitting escape to exit did NOTHING

Had to pull power to reboot, and comes back with same message

Upon executing the sequence of insert disk, select 'r', still nothing
happens and have to power off.

Any ideas?

So the keyboard doesn't work ?

Or the keyboard is outputting something not recognized by the installer,
like a shift or modifier key jammed, locale different than expected
(French keyboard with English CD perhaps?).

Test the keyboard with something.

If you have an old MSDOS floppy, perhaps you can type in the command line
when the floppy boots up. Or, use a Linux CD and do some typing after
that comes up. Useful Linux CDs are usually bloated with software
you don't need for a test like this. But some of the smaller distros
are so convoluted, you'll never figure out how to use them.

http://mirror.switch.ch/ftp/mirror/knoppix/

KNOPPIX_V6.7.1CD-2011-09-14-EN.iso 14-Sep-2011 17:29 700M

*******

When you say the "system downloaded many programs", I think you're
seeing the driver loading statements as the installer CD boots using
it's collection of drivers for hardware support. It's real slow to
do that (due to all the random seeking of the CD drive, at 110 milliseconds
a pop). All of that software, comes off the CD, not the network or anything.

Paul

 

[Robert Macy]

So the keyboard doesn't work ?

Or the keyboard is outputting something not recognized by the installer,
like a shift or modifier key jammed, locale different than expected
(French keyboard with English CD perhaps?).

Test the keyboard with something.

If you have an old MSDOS floppy, perhaps you can type in the command line
when the floppy boots up. Or, use a Linux CD and do some typing after
that comes up. Useful Linux CDs are usually bloated with software
you don't need for a test like this. But some of the smaller distros
are so convoluted, you'll never figure out how to use them.

http://mirror.switch.ch/ftp/mirror/knoppix/

KNOPPIX_V6.7.1CD-2011-09-14-EN.iso        14-Sep-2011 17:29  700M

*******

When you say the "system downloaded many programs", I think you're
seeing the driver loading statements as the installer CD boots using
it's collection of drivers for hardware support. It's real slow to
do that (due to all the random seeking of the CD drive, at 110 milliseconds
a pop). All of that software, comes off the CD, not the network or anything.

    Paul

Thank you for your reply. Not on a network, isolated PC purposely
originally made C: drive FAT32, partition for 5GB to speed an install
and make compatible with Win98


The technique for a clean install is to use a Win98 boot disk, select
install CD Rom, and format the C: drive - completely wiping clean.

Remove from A: the Win98 boot disk insert the WinXP CD and reboot the
system, when asked 'start from CD?' hit enter and usually off
reinstalling WinXP Professional absolutely clean. But NOT today!

While in Win98 DOS I thought I had completely verified the operation
of the keyboard by checking dir a: or C: or copy a file frorm D: to C:
even run scandisk. All the letters come up correctly. so assumed
keyboard works and there is apparently no hung key.

After posting this, I gave up trying to restore and went back to a
clean install, everything works great until the EULA shows, can scan
up and down, but neither F8 to accept, nor esc to bail out works.
Nothing happens when I hit F8 to accept, and once hit, the system is
locked up tight, only way out is power down. and have reformatted C:
and started again, but each time when get to the question to accept
the license, HANG

Any ideas?

 

[Paul]

Thank you for your reply. Not on a network, isolated PC purposely
originally made C: drive FAT32, partition for 5GB to speed an install
and make compatible with Win98


The technique for a clean install is to use a Win98 boot disk, select
install CD Rom, and format the C: drive - completely wiping clean.

Remove from A: the Win98 boot disk insert the WinXP CD and reboot the
system, when asked 'start from CD?' hit enter and usually off
reinstalling WinXP Professional absolutely clean. But NOT today!

While in Win98 DOS I thought I had completely verified the operation
of the keyboard by checking dir a: or C: or copy a file frorm D: to C:
even run scandisk. All the letters come up correctly. so assumed
keyboard works and there is apparently no hung key.

After posting this, I gave up trying to restore and went back to a
clean install, everything works great until the EULA shows, can scan
up and down, but neither F8 to accept, nor esc to bail out works.
Nothing happens when I hit F8 to accept, and once hit, the system is
locked up tight, only way out is power down. and have reformatted C:
and started again, but each time when get to the question to accept
the license, HANG

Any ideas?

A similar description to yours here, except the person is using
an Upgrade disk, and the installer goes off looking for a previous
OS installation.

http://www.realgeek.com/forums/install-hangs-after-accepting-license-agreement-417052.html

The suggestion here, is the installer may be attempting to mount
partitions right at that moment, so the hang could be a problem
accessing the disk.

http://en.community.dell.com/support-forums/disk-drives/f/3534/p/19174720/19298435.aspx

Maybe someone else will have some ideas.

Paul

 

[Paul]

Thank you for your reply. Not on a network, isolated PC purposely
originally made C: drive FAT32, partition for 5GB to speed an install
and make compatible with Win98


The technique for a clean install is to use a Win98 boot disk, select
install CD Rom, and format the C: drive - completely wiping clean.

Remove from A: the Win98 boot disk insert the WinXP CD and reboot the
system, when asked 'start from CD?' hit enter and usually off
reinstalling WinXP Professional absolutely clean. But NOT today!

While in Win98 DOS I thought I had completely verified the operation
of the keyboard by checking dir a: or C: or copy a file frorm D: to C:
even run scandisk. All the letters come up correctly. so assumed
keyboard works and there is apparently no hung key.

After posting this, I gave up trying to restore and went back to a
clean install, everything works great until the EULA shows, can scan
up and down, but neither F8 to accept, nor esc to bail out works.
Nothing happens when I hit F8 to accept, and once hit, the system is
locked up tight, only way out is power down. and have reformatted C:
and started again, but each time when get to the question to accept
the license, HANG

Any ideas?

What would happen, if a necessary disk driver wasn't offered via F6 ?

On an older system, you'd expect the default Windows driver to be
enough, in which case pressing F6 would not be necessary during
the install.

Now, if a driver was needed, what would the system response be ?
I would not have expected "freezing" to be an acceptable solution.

You could check the BIOS and make sure the storage interface
is in an easy-to-use mode. Intel chipsets might have
IDE, AHCI, or RAID as choices, and I'd choose IDE to make
the installation proceed as easily as possible. Now, chances
are it's already set that way, because you mentioned "win98".

Paul

 

[Robert Macy]

What would happen, if a necessary disk driver wasn't offered via F6 ?

On an older system, you'd expect the default Windows driver to be
enough, in which case pressing F6 would not be necessary during
the install.

Now, if a driver was needed, what would the system response be ?
I would not have expected "freezing" to be an acceptable solution.

You could check the BIOS and make sure the storage interface
is in an easy-to-use mode. Intel chipsets might have
IDE, AHCI, or RAID as choices, and I'd choose IDE to make
the installation proceed as easily as possible. Now, chances
are it's already set that way, because you mentioned "win98".

    Paul

Thankyou for the URLs four things caught my attention:
could be looking for old version
could be bad RAM
could be bad CD
could be scratched CD

I don't see how it can look for old version the disk was formatted?

bad RAM, hmmm don't know I think RAM is used as part of bht WIN98
boot, so unlikely too

bad CD is VERY likely, maybe not CD, or maybe the cabling, or the
actual drivers on the motherbd.

scratched CD, just noticed there is a tiny smudge scratch I've never
seen before. but it's so close to the hub can't believe it's in the
middle ofa setup program

What bothers me is that I've done this maybe a hundred times and this
is the first time it's hung.

I don't know how to check the 'health' of the partition from the Win98
DOS from the boot disk.

here's a snap shot of the Dell setup:
two HD, one CD, one floppy

Not sure this is right, but you get the idea:
During DOS bootup hit F2 for setup which shows the drives are:
Primary 0
Drive 0 Auto EIDA 10GB
Drive 1 Auto EIDA 40GB
Secondary
Drive 0 Auto CD ROM
Drive 1 None

So one cable goes to two hard drives and the other cable goes to the
CD

the 10GB has a bad section that bombs almost everything, so Ijust
don't use it by partitioning 5GB and 3.5GB

When it used to operate those disks came up
C: 5GB
D: 40GB
E: 3.5GB

Oddly at one time I could dir C: or copy to C: and then dir everything
worked, but when I scandisk c:itwould come back with 'does not exist'
message?! sometimes in DOS the display suddenly tries to do something
with G: and can't, so gives that not ready error: (a)bort, (r)etry,
can't even remember the other choice now, but odd.

Just now I formatted C: then ran scandisk /surface and came up perfect
Sometimes I get to the screen after the EULA, to where it shows the
drives, size etc, then hangs there, but more often hangs with license
acceptance.

I can't think of any more cleaner install than having C: completely
wiped and empty!





The 10GB i

 

[Paul]

Thankyou for the URLs four things caught my attention:
could be looking for old version
could be bad RAM
could be bad CD
could be scratched CD

I don't see how it can look for old version the disk was formatted?

bad RAM, hmmm don't know I think RAM is used as part of bht WIN98
boot, so unlikely too

bad CD is VERY likely, maybe not CD, or maybe the cabling, or the
actual drivers on the motherbd.

scratched CD, just noticed there is a tiny smudge scratch I've never
seen before. but it's so close to the hub can't believe it's in the
middle ofa setup program

What bothers me is that I've done this maybe a hundred times and this
is the first time it's hung.

I don't know how to check the 'health' of the partition from the Win98
DOS from the boot disk.

here's a snap shot of the Dell setup:
two HD, one CD, one floppy

Not sure this is right, but you get the idea:
During DOS bootup hit F2 for setup which shows the drives are:
Primary 0
Drive 0 Auto EIDA 10GB
Drive 1 Auto EIDA 40GB
Secondary
Drive 0 Auto CD ROM
Drive 1 None

So one cable goes to two hard drives and the other cable goes to the
CD

the 10GB has a bad section that bombs almost everything, so Ijust
don't use it by partitioning 5GB and 3.5GB

When it used to operate those disks came up
C: 5GB
D: 40GB
E: 3.5GB

Oddly at one time I could dir C: or copy to C: and then dir everything
worked, but when I scandisk c:itwould come back with 'does not exist'
message?! sometimes in DOS the display suddenly tries to do something
with G: and can't, so gives that not ready error: (a)bort, (r)etry,
can't even remember the other choice now, but odd.

Just now I formatted C: then ran scandisk /surface and came up perfect
Sometimes I get to the screen after the EULA, to where it shows the
drives, size etc, then hangs there, but more often hangs with license
acceptance.

I can't think of any more cleaner install than having C: completely
wiped and empty!





The 10GB i

Disconnect the defective drive, connect the working drive,
check jumpers on the working drive to be sure they're OK.
With a Dell, you could have got in the habit of using Cable
Select for both drives, in which case there's nothing to worry
about. When running one drive, plug it into the "end" connector,
not the "middle" one.

Then try the install.

If a hard drive is defective, I'd move it out of the way, until
the "fun" (install) is finished. Then, if you want to throw
it back into the mix, go right ahead.

Paul

 

[Robert Macy]

Disconnect the defective drive, connect the working drive,
check jumpers on the working drive to be sure they're OK.
With a Dell, you could have got in the habit of using Cable
Select for both drives, in which case there's nothing to worry
about. When running one drive, plug it into the "end" connector,
not the "middle" one.

Then try the install.

If a hard drive is defective, I'd move it out of the way, until
the "fun" (install) is finished. Then, if you want to throw
it back into the mix, go right ahead.

    Paul

Thank you for the suggestions.

The drive that becomes C: drive is plugged into the last cable plug. I
did remove one drive so only one was there.

Same symtom.

I used to boot up the Win98 disk and specifically ask for NO CD
support, format the C: and install the WinXP.

But, doing that took quite a few boots before the CD would kick in and
install WinXP. Only recently did I notice that *IF* I booted up the
Win98 with CD enabled, did the WinXP CD catch everytime the first
time. So reinstalls went faster.

The 'faulty' disk 10GB that I paired down to 8.5GB to avoid something
that prevented formatting it is the one I install WinXP on. That same
disk, the section that becomes C: I did a complete scandisk check on
including surface and came back perfect.

The most frustrating part of this is that the automation of everything
prevents me from looking at what is going on, including flahsing
cryptic information [and completely unintelligible since I'm in the
middle of an autlmated simplified proces for dummies anyway. For
example, I've NEVER figured out what the heck, "Do you want to revert
to the original form?" means when Word has an error], these 'error'
message disappear just at the time you focus your eyes on one, not
even being able to read it. Yet the directions from MS to 'solve' a
problem are so involved using language and dialogue of a programmer,
they require having another PC running next to you?!

 

[glee]

The 'faulty' disk 10GB that I paired down to 8.5GB to avoid something
that prevented formatting it is the one I install WinXP on. That same
disk, the section that becomes C: I did a complete scandisk check on
including surface and came back perfect.

Why on earth would you install Windows on the faulty drive in the first
place?? Whether or not you have excluded the damaged 1.5GB from use,
the drive has damage and should not even be considered for the
system/boot drive.... no matter what Scandisk "thinks". Scandisk is
simply not a great indicator. Drive integrity should be checked with
the drive manufacturer's diagnostic boot CD.... but even them, a damaged
drive as the system/boot drive is folly.

 

[Dominique]

Robert Macy <[email protected]> écrivait (e-mail address removed):

scratched CD, just noticed there is a tiny smudge scratch I've never
seen before. but it's so close to the hub can't believe it's in the
middle ofa setup program

<snip>

I don't have a solution for your problem but FWIW CDs are read from the hub
toward the edge (from inside to outside), so in your case if the scratch is
close to the hub, it's at the beginning of the CD.

You could try copying the disk.

 

[Robert Macy]

Why on earth would you install Windows on the faulty drive in the first
place??  Whether or not you have excluded the damaged 1.5GB from use,
the drive has damage and should not even be considered for the
system/boot drive.... no matter what Scandisk "thinks".  Scandisk is
simply not a great indicator.  Drive integrity should be checked with
the drive manufacturer's diagnostic boot CD.... but even them, a damaged
drive as the system/boot drive is folly.

True, but I've been using it for over 8 years.


Now the install really got strange!

to check if the CD Drive was bad I installed Win98, during
installation as it ran scandisk found something wrong on the E: drive
and fixed it. Not sure why anything on the E: drive should impact the
C: drive but who can question the wisdom? Especially since install has
no idea where E: resides.

Win98 would not install, either. Just as I was convinced the CD Drive
was at fault and several attempts later, each time the Win98 would
also hang, left dangling fragments everywhere since I would simply
pull the plug. Finally Win98 became happy. installed Win98 and copied
all the files I wanted from E: to a section on D:\CopyofDriveE\*.*, I
was planning on running fdisk, or something drastic.

After I did the install of Win98 thought I would format E but forgot,
continued on and formatted C: insert WinXP Professional and it went
off and running EXTREMELY happy to completion [first time tried!] and
I'm using WinXP on the machine.

What's very strange is that this time during installation the screen
was completely a different form. The window showing files downloading
instead of being up near the middle was down at the bottom lower right
corner! Plus, the files downloading weren't like the 'high' level
ones that kept displaying during the failure sequence, but were tons
of those itty bitty .dll files whisking by in a total flash!

After new screen and different set of files downloaded WinXP worked!

So why and how could I get a different screen display since both times
I had formatted C: drive? Where does the information reside that
formatting evidently did NOT remove it. Not until successfully
installing Win98 did anything change.

 

[glee]

True, but I've been using it for over 8 years.


Now the install really got strange!

to check if the CD Drive was bad I installed Win98, during
installation as it ran scandisk found something wrong on the E: drive
and fixed it. Not sure why anything on the E: drive should impact the
C: drive but who can question the wisdom? Especially since install has
no idea where E: resides.

The E: partition is part of the same physical disk as your C:, and setup
is probably checking the integrity of the physical disk before
continuing.

Win98 would not install, either. Just as I was convinced the CD Drive
was at fault and several attempts later, each time the Win98 would
also hang, left dangling fragments everywhere since I would simply
pull the plug. Finally Win98 became happy. installed Win98 and copied
all the files I wanted from E: to a section on D:\CopyofDriveE\*.*, I
was planning on running fdisk, or something drastic

Every time you pulled the plug on a failed installation, did you
reformat before the next attempt? If not, you may have either been
leaving some installation files on C: between attempts, or you were
actually continuing the previously failed setup on the subsequent
attempts.

After I did the install of Win98 thought I would format E but forgot,
continued on and formatted C: insert WinXP Professional and it went
off and running EXTREMELY happy to completion [first time tried!] and
I'm using WinXP on the machine.

Could be a couple of reasons.... setup may have finally seen the
physical drive as without errors and could continue, or the CD may have
been hanging due to the scratch, or the CD drive may be intermittently
failing (which is common), or....?

What's very strange is that this time during installation the screen
was completely a different form. The window showing files downloading
instead of being up near the middle was down at the bottom lower right
corner! Plus, the files downloading weren't like the 'high' level
ones that kept displaying during the failure sequence, but were tons
of those itty bitty .dll files whisking by in a total flash!

After new screen and different set of files downloaded WinXP worked!

Are you sure XP setup did not install any system or boot files on E:?
As far as the visual differences you describe, I have no idea.... your
procedure has been too convoluted to take a guess. I'm still wondering
why you boot with a floppy in the first place, to format 5GB, when the
XP CD could do the same in one run.

So why and how could I get a different screen display since both times
I had formatted C: drive? Where does the information reside that
formatting evidently did NOT remove it. Not until successfully
installing Win98 did anything change.

What makes you think formatting didn't remove things from C:? Also, as
I mentioned above, are you surte neither setup was using E: for anything
(which you did NOT format)?

 

[Robert Macy]

True, but I've been using it for over 8 years.

Now the install really got strange!

to check if the CD Drive was bad I installed Win98, during
installation as it ran scandisk found something wrong on the E: drive
and fixed it. Not sure why anything on the E: drive should impact the
C: drive but who can question the wisdom? Especially since install has
no idea where E: resides.

The E: partition is part of the same physical disk as your C:, and setup
is probably checking the integrity of the physical disk before
continuing.

Win98 would not install, either. Just as I was convinced the CD Drive
was at fault and several attempts later, each time the Win98 would
also hang, left dangling fragments everywhere since I would simply
pull the plug. Finally Win98 became happy. installed Win98 and copied
all the files I wanted from E: to a section on D:\CopyofDriveE\*.*, I
was planning on running fdisk, or something drastic

Every time you pulled the plug on a failed installation, did you
reformat before the next attempt?  If not, you may have either been
leaving some installation files on C: between attempts, or you were
actually continuing the previously failed setup on the subsequent
attempts.

After I did the install of Win98 thought I would format E but forgot,
continued on and formatted C: insert WinXP Professional and it went
off and running EXTREMELY happy to completion [first time tried!] and
I'm using WinXP on the machine.

Could be a couple of reasons.... setup may have finally seen the
physical drive as without errors and could continue, or the CD may have
been hanging due to the scratch, or the CD drive may be intermittently
failing (which is common), or....?

What's very strange is that this time during installation the screen
was completely a different form.  The window showing files downloading
instead of being up near the middle was down at the bottom lower right
corner!  Plus, the files downloading weren't like the 'high' level
ones that kept displaying during the failure sequence, but were tons
of those itty bitty .dll files whisking by in a total flash!

After new screen and different set of files downloaded WinXP worked!

Are you sure XP setup did not install any system or boot files on E:?
As far as the visual differences you describe, I have no idea.... your
procedure has been too convoluted to take a guess.  I'm still wondering
why you boot with a floppy in the first place, to format 5GB, when the
XP CD could do the same in one run.

So why and how could I get a different screen display since both times
I had formatted C: drive?  Where does the information reside that
formatting evidently did NOT remove it. Not until successfully
installing Win98 did anything change.

What makes you think formatting didn't remove things from C:?  Also, as
I mentioned above, are you surte neither setup was using E: for anything
(which you did NOT format)?

Glen,

Thank you for your insights. I use Win98 to format C: in order to
leave NOTHING [at least I thought] on the C: drive relating to the
previous WinXP installation. I thought formatting overwrote wiping the
surface of all vestige - everywhere. But, evidently not, since the
WinXP tried seemed to download 'different' programs the time it
worked. Plus, that different screen?!!! The screen was so different
even oblivious me saw it.

If you saw the CD, you'd probably claim it pristine with no scratches,
but 'any' thing can cause a problem [I assume] I didn't know drives
hung. I tried two different drives to check. Didn't seem to make a
difference.

I don't know if anything went to E: Don't know why, there was always
D: available.

I'm not sure, but I think the monitor driver would change and stay
also ?? I don't know where that resides, but the screen resolution
got changed, when to me, it should have alwys been the same, some
default, each time.

I didn't know the WinXP disk had the ability to format C: I heard that
formatting a drive with WinXP vs Win98 even as FAT32 left vestiges of
something on the drive foreign to Win98. Plus, this is a 'reinstall'
of my purchased, but never registered, copy of WinXP, that I kept
reinstalling every month to do the work I needed to do in 2004. After
the work was completed I only run WinXP to do some C++ writing and get
the pictures off my cell phone.

Not certain it's germaine, but lost a small thumb drive by formatting
it with WinXP, whereas Win98 never caused a problem. No biggie, it
was a complementary stick from a vendor, irritating to lose the
function.

Since all is up and running, I'll try the machine again and see if
it's still running WinXP alright. If the drive is intermittent, which
could explain one heck of lot here, it'll show up now. Will let you
know.

 

[BillW50]

In
Robert Macy typed:

During bootup came up with error message about running original disk
and restore from that.

Inserted disk, booted from CD, system downloaded many programs and
then presented a screen with 3 choices.

Install
restore
escape


The 'r' key did NOTHING!

Hitting escape to exit did NOTHING

Had to pull power to reboot, and comes back with same message

Upon executing the sequence of insert disk, select 'r', still nothing
happens and have to power off.

Any ideas?

After reading the thread up to this point of time (although I probably
missed a thing or two along the way). I do have a question. Are you
trying to restore with an USB optical drive? If so, you can run into
problems like this and sometimes there are workarounds to make it work.

 

[BillW50]

In Paul typed:

So the keyboard doesn't work ?

Or the keyboard is outputting something not recognized by the
installer, like a shift or modifier key jammed, locale different than
expected (French keyboard with English CD perhaps?).

Test the keyboard with something.

If you have an old MSDOS floppy, perhaps you can type in the command
line when the floppy boots up. Or, use a Linux CD and do some typing
after that comes up. Useful Linux CDs are usually bloated with
software you don't need for a test like this. But some of the smaller
distros are so convoluted, you'll never figure out how to use them.

My favorite tools for NT based Windows is either BartPE or WinPE. And I
would stay away from Live Linux, since they have been known to mess up
some Windows installs and to make Windows unbootable. It appears some
Linux distros borrows the Windows swapfile and can leave it in a state
that makes Windows unbootable.

But a quick test to checkout if the keyboard is functioning or not, I'll
use the BIOS Setup. Sure it doesn't use much of the keys, but at least
you learn whether or not the BIOS can see the keyboard or not.

 

[BillW50]

In Paul typed:

What would happen, if a necessary disk driver wasn't offered via F6 ?

On an older system, you'd expect the default Windows driver to be
enough, in which case pressing F6 would not be necessary during
the install.

Now, if a driver was needed, what would the system response be ?
I would not have expected "freezing" to be an acceptable solution.

You could check the BIOS and make sure the storage interface
is in an easy-to-use mode. Intel chipsets might have
IDE, AHCI, or RAID as choices, and I'd choose IDE to make
the installation proceed as easily as possible. Now, chances
are it's already set that way, because you mentioned "win98".

I can't ever remember trying to install DOS or Windows 98 on a SATA
drive before. But I don't think those care if it is or not. Although
some NT based Windows does care. Windows 2000 and XP are the ones that
do. And unless there is a setting in the BIOS, Windows will need a SATA
driver before it can see the drive. And I am pretty sure without the
SATA driver, the install will not react to keys if it can't find a drive
to install Windows.

 

[glee]

snip
My favorite tools for NT based Windows is either BartPE or WinPE. And
I would stay away from Live Linux, since they have been known to mess
up some Windows installs and to make Windows unbootable. It appears
some Linux distros borrows the Windows swapfile and can leave it in a
state that makes Windows unbootable.
snip

Linux Live CDs are loaded entirely in memory and do not touch a hard
drive in any way, without explicit direction from the user.

They don't use the Windows swap file even if the user chooses to install
Linux on the hard drive.... the swap file is OS-dependent and Linux
installed on the hard drive creates its own.

What Linux distro are you referring to, that makes Windows unbootable
and/or "borrows the Windows swap file?"

 

[BillW50]

In glee typed:

Linux Live CDs are loaded entirely in memory and do not touch a hard
drive in any way, without explicit direction from the user.

Yes I know that is the claim and yes I know that is what about 99% or
better believe.

They don't use the Windows swap file even if the user chooses to
install Linux on the hard drive.... the swap file is OS-dependent and
Linux installed on the hard drive creates its own.

Actually that isn't so. It depends on the one compiles the Linux code if
it does or not. Just like the Xandros Linux that was used on Asus EeePC
machines only could access 1GB of RAM max, no matter how much RAM the
machine actually had. Why when Xandros was configured with this
limitation when compiled, who only knows?

What Linux distro are you referring to, that makes Windows unbootable
and/or "borrows the Windows swap file?"

The one example I know very well was Ubuntu v8.10 back in 2009. I also
tested Puppy Linux during this period and it didn't have this problem.
Whether later Ubuntu builds has the same problem or not, I do not know
or even care. As I learned to not mix Linux and Windows at the same
time. Far less problems that way.

 

[glee]

In glee typed:

Yes I know that is the claim and yes I know that is what about 99% or
better believe.


Actually that isn't so. It depends on the one compiles the Linux code
if it does or not. Just like the Xandros Linux that was used on Asus
EeePC machines only could access 1GB of RAM max, no matter how much
RAM the machine actually had. Why when Xandros was configured with
this limitation when compiled, who only knows?


The one example I know very well was Ubuntu v8.10 back in 2009. I also
tested Puppy Linux during this period and it didn't have this problem.
Whether later Ubuntu builds has the same problem or not, I do not know
or even care. As I learned to not mix Linux and Windows at the same
time. Far less problems that way.

What you are stating is about Linux installations, not Live CDs. Live
CDs don't touch the hard drive other than to poll what is there in case
the user wants to mount one later. I don't doubt that you've seen Linux
installations that have caused issues with Windows, but you referred
originally to Live Linux , which are bootable Live CDs, and they don't,
by default, touch the hard drive.

 

[BillW50]

In glee typed:

What you are stating is about Linux installations, not Live CDs. Live
CDs don't touch the hard drive other than to poll what is there in
case the user wants to mount one later. I don't doubt that you've
seen Linux installations that have caused issues with Windows, but
you referred originally to Live Linux , which are bootable Live CDs,
and they don't, by default, touch the hard drive.

No, what I am referring to is about *only* Live Linux. And using Live
Linux and purposely not accessing the Windows drive at all. But at least
Ubuntu Live Linux does anyway behind your back.