Toshiba W-7 went dark

In message , HB writes:

"J. P. Gilliver (John)" wrote in message
...

It isn't that complicated once you grasp what we're trying to do at each
stage! Time consuming, yes. The first thing we're trying to do is
establish whether the HD is actually faulty or just corrupted.
[]

I have no idea what any of this means:

I burned it to a disc (Puppy), turned the Toshiba on, and it says this:

done (in green, upper right hand corner.)
Loading drivers needed to access disk drives. Searching for Puppy files in
computer disk drives. (The in RED is says), fd64-500. sfs not found.
Dropping out to intitial-ramdisk console. /bin/sh :can't acess tty; job
control turned off # -

That's it with Puppy. What next?


Excellent! You have clearly succeeded in making a bootable CD, and
making the BIOS settings on the PC boot from it, for the above to have
done what it has so far.

What to do next, I am afraid I can't say, as I don't know enough about
Linux. Someone who does, should be able to tell you what to do now to
see whether the hard drive is faulty, or just corrupted.
--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

"Not an electronic sausage!"

On Sat, 17 Mar 2018 18:52:57 -0400, "HB" wrote:


"J. P. Gilliver (John)" wrote in message
...

It isn't that complicated once you grasp what we're trying to do at each
stage! Time consuming, yes. The first thing we're trying to do is
establish whether the HD is actually faulty or just corrupted.
[]

I reburned puppy500 with a different Burner, making sure TWICE it was set to
OSI, but the result was the same.

It seems to need fd64-500.sfs which wasn't found. I have no idea what tty
is.

What's going wrong?


I would suggest that you download the latest version of Fatdog64.

That would be version Fatdog64-721.ISO

The version of Fatdog that you downloaded was released in July, 2010.

You would then have the latest drivers for your hardware and you might
eliminate most (if not all) error messages (item wasn't found).


Following that exercise, I would then suggest that you download

Macrium Reflect 7 Free Edition and install it on an operating PC.

With that program, you would have the opportunity to repair errors in
the boot menu (if that is where the problem is).

Once installed, you would start the program and on the menu bar you
would select "Other Tasks" and then select "Create Rescue Disk".

The "Rescue Media Wizard" will appear and then select "Next".
Then "Next" again and insert a blank CD in your CD drive.

When the CD is created, you can leave it in the drive and boot your PC
from it. After the booting has finished, you will see a list of
Restore Tasks.

Select the top option "Fix Windows boot problems". Follow the
on-screen instructions and, when finished, remove the CD and restart
your PC.

Good Luck!

HB wrote:
"J. P. Gilliver (John)" wrote in message
...
It isn't that complicated once you grasp what we're trying to do at each
stage! Time consuming, yes. The first thing we're trying to do is
establish whether the HD is actually faulty or just corrupted.
[]

I have no idea what any of this means:

I burned it to a disc (Puppy), turned the Toshiba on, and it says this:

done (in green, upper right hand corner.)
Loading drivers needed to access disk drives. Searching for Puppy files in
computer disk drives. (The in RED is says), fd64-500. sfs not found.
Dropping out to intitial-ramdisk console. /bin/sh :can't acess tty; job
control turned off # -

That's it with Puppy. What next?

Can I make a small suggestion ?

Look at your post for a moment.

Does the post contain standalone "context" information ?

What would help us, as readers, understand what we're
replying to ?

For example, this is a Windows group, and you're asking
a question about Linux. I started that, as a means to
step around the issue of having no Windows media to
speak of. I suggested trying a particular Linux distro,
and eventually gave you a page with files on it.

There are five hundred distributions of Linux times
multiple releases of each.

You switched to Puppy. You got it from somewhere. But...

*WHICH EXACT FILE WERE YOU RUNNING ???*

*******

I have a fair idea of what should have happened.
But I won't know for sure, until you tell me what
piece of cruft you found on the Internet. Which site.
Which exact file.

Puppy is best suited to older computers. It brings
up my Year 2000 P2B-S system with 1.1GHz processor,
pretty well perfectly. Everything has a driver.
The disk drivers for Puppy, would be IDE,
either I/O Space or PCI space.

More modern computers, have additional settings
for the disk interface. For example, I think my laptop
with InsydeH20 BIOS, can flip from AHCI to Native IDE
as a BIOS Setup Screen setting. If I didn't want
to putz with the BIOS settings (I normally don't
on that thing), I would use Fatdog64.

Native (=PCI space) IDE or === WinXP can handle
Compatible (I/O space,INT14/INT15) IDE === What Win98 likes

AHCI (command queuing like SCSI) === Vista era
RAID (Redundant Array Individual Disks)

The Fatdog64 concept of Puppy, uses a later kernel
and is more likely to have the AHCI your machine is
using. If you have InsydeH2O BIOS, that's a UEFI era
BIOS (Insyde is a young company), and a UEFI era setup
is more likely to be AHCI. It's not absolutely
precluded from having other settings, but I'd
really rather not go there.

Fatdog64 runs perfectly on my four year old computer.
Puppy runs perfectly on my eighteen year old computer.

On the 18 year old computer, it cannot even boot from
an IDE DVD drive. The 18 year old BIOS has no concept of
what a 4.7GB DVD is. It won't even issue a command to the drive!
The light won't blink. A distro like Puppy is essential
in that case, since optical media in the form of CDs
and associated IDE CD drives, ls all that an 18 year old
computer understands. I have run a recent Ubuntu on the
18 year old computer, but that was done by transplanting
an IDE drive to it, with the software already on it.
You can do that.

*******

If I went to Napa Auto Parts and said:

"Gimme some windshield wipers"

what's the first thing the clerk is going to ask ?

"Uh, what make and model of car do you have, sir."

Try to anticipate the natural questions we're going to ask.

If you go to any fabrication shop, with a poorly prepared
specification for something, the staff go out of their
way to produce an absurd item in response (shades of the
Spinal Tap movie). I don't think you'd enjoy these threads
quite as much, with an audience filled with such people.
But at least in my experience, the response is consistent.
All the fabricators would do the same thing to me :-(

(Here, the Spinal Tap band members visit Stonehenge, only to
discover it really is only 13 inches high.)

https://www.thewrap.com/wp-content/u...stonehenge.jpg

Paul

On 17/03/2018 02:08, HB wrote:
https://support.toshiba.com/repair
In reading the site the PC is out of warranty and isn't W-8.

Scroll down to Get Recovery Media.

Don't show or tell us the Licence number (Certificate Of Authenticity)
which could be stolen from you if you show/reveal it. Said Licence
number (COA) has the format; xxxxx-xxxxx-xxxxx-xxxxx-xxxxx (five groups
of five digits), it should also be the the one that you used trying to
download W7 from Microsoft but it was rejected because it is an OEM
(Original Equipment Manufacture) licence. Thus it is that MS rejected it
because it is not thiere responsibility but the OEM's (Toshiba).

I suspect that when you went to the Toshiba site
https://support.toshiba.com/repair
to get the Recovery Media from them, that you tried to put in the above
mentioned COA rather than the Serial-Number of your machine/laptop


Can you please take a photo of the label that is on the underside of the
Laptop, and then give us a link to said picture/s?

On 18/03/2018 11:15, Patrick wrote:
On 17/03/2018 02:08, HB wrote:
https://support.toshiba.com/repair
In reading the site the PC is out of warranty and isn't W-8.

Scroll down to Get Recovery Media.

Don't show or tell us the Licence number (Certificate Of Authenticity)
which could be stolen from you if you show/reveal it. Said Licence
number (COA) has the format; xxxxx-xxxxx-xxxxx-xxxxx-xxxxx (five groups
of five digits), it should also be the the one that you used trying to
download W7 from Microsoft but it was rejected because it is an OEM
(Original Equipment Manufacture) licence. Thus it is that MS rejected it
because it is not thiere responsibility but the OEM's (Toshiba).

I suspect that when you went to the Toshiba site
https://support.toshiba.com/repair
to get the Recovery Media from them, that you tried to put in the above
mentioned COA rather than the Serial-Number of your machine/laptop


Can you please take a photo of the label that is on the underside of the
Laptop, and then give us a link to said picture/s?



Please see here, to get the Serial-Number etc., of your machine;
https://support.toshiba.com/sscontent?contentId=4007069

On 17/03/2018 22:38, HB wrote:
I have no idea what any of this means:

I've not seen that before either, however ...

I burned it to a disc (Puppy), turned the Toshiba on, and it says this:

done (in green, upper right hand corner.)
Loading drivers needed to access disk drives.

Good - as others have said, it shows that your BIOS settings are
sufficient to boot from the media you used, and that the PC is bootable.

Searching for Puppy files in
computer disk drives. (The in RED is says), fd64-500. sfs not found.

I can't find a reference to fd64-500.sfs as such, only ...

http://gorgeaccess.net/fatdog/ro/ind...ge=Sfs%20files

"An sfs file is a file system that is merged with your normal file
system at boot.

.... (it then lists the following, the first is repeated 3 times with
different values of z = 0, 1, 2, but I wouldn't have expected the
absence of any of them to be a show stopper such as you encountered) ...

fd64-devx_5z0.sfs
Devx - for compilation and development.
Part of Fatdog64 proper.
Note: This is only for Fatdog 5z0

.... (finally, and the absence of this might be a show stopper) ...

fd64-32bit-libs-7.sfs
Compatibility library for running 32-bit applications.
Re-packaged for Fatdog from Quirky 1.1, Fatdog's little brother."

Perhaps you didn't quite copy the file name right? At any rate see
below ...

Dropping out to intitial-ramdisk console. /bin/sh :can't acess tty; job
control turned off # -

It's encountered a show-stopping error and tried to drop out to a
command console or shell, the Linux equivalent of what in Windows is
sometimes called a command prompt or a DOS box. However, I'm not sure
from the above whether or not it actually succeeds in getting to a
command prompt that you can use. If it does, there might some commands
that you can give there which might be useful.

So the next question is ...

What happens when you try to enter something harmless (where obviously
Enter means press the Enter or Return key):

1) First type this, it should give you a directory listing ...
ls -alEnter

2) Next try this ...
which shEnter
.... which should give you a path name, most probably ...
/bin/sh

Try this and report back to us.

I'm not familiar with this particular Linux distro, so can someone else
tell us:
Would lilo would be available in such a command shell?
If not, would it be on the media and what command to install it?
If not, would the network be running?
If not, could the network it be started, and by what command?
What command to install lilo via the network?

Ditto for either fdisk or cfdisk.

That's it with Puppy. What next?

If you get a usable command shell, that's not it with Puppy!

On 18/03/2018 11:43, Java Jive wrote:

I'm not familiar with this particular Linux distro, so can someone else
tell us:
Â*Â*Â*Â*Would lilo would be available in such a command shell?

I suppose I should've asked HB also to try typing:
lilo --helpEnter

In message , Monty
writes:
On Sat, 17 Mar 2018 18:52:57 -0400, "HB" wrote:
[]
I reburned puppy500 with a different Burner, making sure TWICE it was set to
OSI, but the result was the same.

It seems to need fd64-500.sfs which wasn't found. I have no idea what tty
is.

What's going wrong?


I would suggest that you download the latest version of Fatdog64.

That would be version Fatdog64-721.ISO

The version of Fatdog that you downloaded was released in July, 2010.

Wouldn't even that one have had drivers for SATA? I can understand that
maybe Puppy wouldn't have. Though not important.

You would then have the latest drivers for your hardware and you might
eliminate most (if not all) error messages (item wasn't found).


Following that exercise,

Why "Following that exercise": surely what you propose below is purely a
Windows/Macrium solution, and shouldn't require any Linux at all? Or am
I missing something?

I would then suggest that you download

Macrium Reflect 7 Free Edition and install it on an operating PC.
https://www.macrium.com/reflectfree appears to be the site.

With that program, you would have the opportunity to repair errors in
the boot menu (if that is where the problem is).
On the faulty PC.

Once installed
On the working PC
, you would start the program and on the menu bar you
would select "Other Tasks" and then select "Create Rescue Disk".

The "Rescue Media Wizard" will appear and then select "Next".
Then "Next" again and insert a blank CD in your CD drive.

When the CD is created, you can leave it in the drive

No, move it from the working PC (where you created it) to the faulty PC
[Monty, am I right here, that this is what you meant?]
and boot your PC
from it. After the booting has finished, you will see a list of
Restore Tasks.

Select the top option "Fix Windows boot problems". Follow the
on-screen instructions and, when finished, remove the CD and restart
your PC.

Good Luck!

That sounds like a good thing to try (and simple). I didn't know the
free version of Macrium had the ability to [create a CD that can] fix,
specifically, Windows boot problems. (Is it only Macrium 7 that has
this?)

If all that is wrong is that something has become corrupted, then this
sounds like it will work. Without any need (including for me!) to learn
how to access, and assess, a hard drive from within a Linux.
--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

What has happened since 1979, I suspect, is that the spotting of mistakes has
become entirely associated with mean-spiritedness, snobbishness and
judgementalism. But...can be...funny and interesting.
Lynn Truss, RT 2015/2/21-27

On Sun, 18 Mar 2018 16:12:36 +0000, "J. P. Gilliver (John)"
wrote:

In message , Monty
writes:
On Sat, 17 Mar 2018 18:52:57 -0400, "HB" wrote:
[]
I reburned puppy500 with a different Burner, making sure TWICE it was set to
OSI, but the result was the same.

It seems to need fd64-500.sfs which wasn't found. I have no idea what tty
is.

What's going wrong?


I would suggest that you download the latest version of Fatdog64.

That would be version Fatdog64-721.ISO

The version of Fatdog that you downloaded was released in July, 2010.

Wouldn't even that one have had drivers for SATA? I can understand that
maybe Puppy wouldn't have. Though not important.

You would then have the latest drivers for your hardware and you might
eliminate most (if not all) error messages (item wasn't found).


Following that exercise,

Why "Following that exercise": surely what you propose below is purely a
Windows/Macrium solution, and shouldn't require any Linux at all? Or am
I missing something?

I would then suggest that you download

Macrium Reflect 7 Free Edition and install it on an operating PC.
https://www.macrium.com/reflectfree appears to be the site.

With that program, you would have the opportunity to repair errors in
the boot menu (if that is where the problem is).
On the faulty PC.

Once installed
On the working PC
, you would start the program and on the menu bar you
would select "Other Tasks" and then select "Create Rescue Disk".

The "Rescue Media Wizard" will appear and then select "Next".
Then "Next" again and insert a blank CD in your CD drive.

When the CD is created, you can leave it in the drive

No, move it from the working PC (where you created it) to the faulty PC
[Monty, am I right here, that this is what you meant?]
and boot your PC
from it. After the booting has finished, you will see a list of
Restore Tasks.

Select the top option "Fix Windows boot problems". Follow the
on-screen instructions and, when finished, remove the CD and restart
your PC.

Good Luck!

That sounds like a good thing to try (and simple). I didn't know the
free version of Macrium had the ability to [create a CD that can] fix,
specifically, Windows boot problems. (Is it only Macrium 7 that has
this?)
Two of my neighbours recently had a problem booting their PCs.
A Google search included Macrium Free as a possible solution to fixing
boot problems. I tried it and it worked perfectly. The simplicity
and success of using that program impressed me and so I am happy to
recommend it. I am sure there are other programs that have a similar
facility but if I find something that is very easy to use, I don't see
any need for doing any further research.

Fixing PCs is just a hobby that I extend to nearby (elderly) neighbors
if I think I can help them.

Many thanks for your corrections (and adjustments) to my input to this
thread. Just hope that HB can get his PC up and running. I also hope
he drops his attempts at creating new symbols in his writings
(otherwise he may find he has fewer readers).


If all that is wrong is that something has become corrupted, then this
sounds like it will work. Without any need (including for me!) to learn
how to access, and assess, a hard drive from within a Linux.

Cheers,

"Paul" wrote in message
news
HB wrote:

Which one do I download from the list? Any one of them?




The picture of the screen I took, was done with this version.

Fatdog64-710.iso 2016-Dec-03 10:04:55 360MB
application/octet-stream

The latest release of the software is this one.

Fatdog64-710.iso 2016-Dec-03 10:04:55 360MB application/octet-stream

Either one would do, for the purposes of a boot test.

Paul

OK. I'll try again before the 1st one was missing something and didn't boot
the Toshiba. That was Fatdog64-500.iso. I posted about that and the error I
got the night before last.

"J. P. Gilliver (John)" wrote in message
...
In message , HB writes:

-snip-


If "every time you plug it in it loads" stuff, then you obviously
_haven't_ deleted it from the Seagate. (It can't load it if you've
deleted
it.)

I understood that if it was deleted from the PC, SG would not copy it
again
in the next update But it appears to copy the new files and adds them to
the old, whether they're on my PC or not anymore. WTH... I'll just clean
it
off when I get the time and start again.

You've thoroughly confused me with that paragraph (even if I guess "SG"
means the Seagate external drive). What are the various "it"s? Something
that has been deleted? Something that copies something? And you're
referring to "SG" as if it does copying. A drive will not of itself copy.
It might conceivably have software on it which, if allowed to autorun,
will copy something.

Sorry for the confusion. SG = Seagate. SG appears to add new files to the
old that it stores. If I remove them from my PC, they are not removed from
the SG. New files are added to the old. I assumed when it did a backup it
would delete what was no longer on my PC and add the new files and folders
it found. In other words replacing what is on the PCs HD at the time of
backup - including the new and deleting the last backup. Apparently that
doesn't happen. It also accumulates backups and never gets rid of them.
Those I deleted by hand. They were strings of numbers and dates it made
them.


Why it puts hundreds of things on the DT is a mystery to me.

It may even be virus-infected.

LOL!!! That would be just my luck.


Turn off autorun, autoplay, and anything like that, before connecting
it.
Then connect it and format it.

I just shut off autorun. Done and the Seagate is being formatted as I type
this. I'll go over the "Manager" later and reset the backups. It's the
FreeAgent-Go, 500 GB.



As E: or F: or whatever. (I'm guessing you haven't partitioned your HD
into more than one partition, so D: is your CD/DVD drive.)


C: is the OS on this old W-7 DT.
D: is the Recovery drive and
E: is the DVD RW drive, and there's an
F: that says Boot, System Volume Information and Recycle Bin.


If you right-click on D: or F:, and select properties, you should get a
pie chart showing amount used and free, so you can work out the total
capacity, which should enable you to figure out which is which, assuming
you know what capacity your "TD" is.

The HD on this Desktop is 1 TB.

I have no available Thumbdrives - all are full. My largest in any case is
128 GBs. The external Seagate HD is 500 GBs.

..

Once opened, if that's possible, what would the next step be?

Inside it, there will be a drive! Hopefully, it will be the same sort - i.
e. a SATA, with two connectors - as the one you have taken out of the
poorly laptop. If it _is_ the same kind, then if you take out the existing
drive and put it somewhere safe, and put the drive from the laptop in its
place. You should then be able yo connect the USB cable to one of your
working computers, and examine whether you can see it, probably as E: or
F: on that computer. If you can't, can you see it with the partitioning
tool (in Windows 7, I get to that by typing parti into the start box and
then going for "Create and format hard disk partitions"; it may be
different in 10), which should be able to "see" through a USB interface.

The above is a bit confusing. Both the DT and the Toshiba are W-7 Home-64
bit. I don't have a USB cable to connect the Toshiba's HD to my DT. Wouldn't
the HD from the Toshiba work like the Seagate if a USB cable can be attached
to it? In that case it would show up under F: drive.


(Do you know what the capacity of the drive from the poorly PC is?)
[]
I'm trying.

I think it's 1 TB also.


Yes, very. (Sorry, couldn't resist; you're not really. Both my parents
were teachers, and "This boy is trying. Very trying" was a standard
teacher joke at report-writing times.)

I know and appreciate it.

[]
Maybe - I think at least one of Paul's posts suggested where you can get
a
rescue disc for 7 (I'm pretty sure that would be a DVD rather than a
CD),
but I'm not sure, as he's made lots of posts in this thread!

Yes he did but it's out or warranty and the Serial number was rejected.

I think it was rejected because the number you gave it was an OEM one not
a retail one, rather than it being out of warranty.

Where would that number be? It's not called that on the Toshiba. Maybe on
the recept from where she bought it?

--

Microsoft motto "If it ain't broke keep fixing it till it is."

"Paul" wrote in message
news
HB wrote:

I burned it to a disc (Puppy), turned the Toshiba on, and it says this:

done (in green, upper right hand corner.)
Loading drivers needed to access disk drives. Searching for Puppy files
in computer disk drives. (The in RED is says), fd64-500. sfs not found.
Dropping out to intitial-ramdisk console. /bin/sh :can't acess tty; job
control turned off # -

That's it with Puppy. What next?

Can I make a small suggestion ?

Look at your post for a moment.

Does the post contain standalone "context" information ?


What would help us, as readers, understand what we're
replying to ?

I wrongly assumed you would know it was pertaining to using Linux to see
if the Toshiba can boot. This was the smallest Linux to see with since my
downloads are not unlimited. I think I replies to the wrong person. Not
getting much sleep causes such things - sorry.


You switched to Puppy. You got it from somewhere. But...

*WHICH EXACT FILE WERE YOU RUNNING ???*

Fatdog64-500 Ihad no way to know exactly what it was.
http://distro.ibiblio.org/fatdog/iso/



*******

I have a fair idea of what should have happened.
But I won't know for sure, until you tell me what
piece of cruft you found on the Internet. Which site.
Which exact file.

Puppy is best suited to older computers. It brings
up my Year 2000 P2B-S system with 1.1GHz processor,
pretty well perfectly. Everything has a driver.
The disk drivers for Puppy, would be IDE,
either I/O Space or PCI space. More modern computers, have additional
settings
for the disk interface. For example, I think my laptop
with InsydeH20 BIOS, can flip from AHCI to Native IDE
as a BIOS Setup Screen setting. If I didn't want
to putz with the BIOS settings (I normally don't
on that thing), I would use Fatdog64.

Native (=PCI space) IDE or === WinXP can handle
Compatible (I/O space,INT14/INT15) IDE === What Win98 likes

AHCI (command queuing like SCSI) === Vista era
RAID (Redundant Array Individual Disks)

The Fatdog64 concept of Puppy, uses a later kernel
and is more likely to have the AHCI your machine is
using. If you have InsydeH2O BIOS, that's a UEFI era
BIOS (Insyde is a young company), and a UEFI era setup
is more likely to be AHCI. It's not absolutely
precluded from having other settings, but I'd
really rather not go there.

Fatdog64 runs perfectly on my four year old computer.
Puppy runs perfectly on my eighteen year old computer.

OK, this is version Fatdog64-702 Dec 2016 as someone here recommended. It
saw and loaded Fatdog. Fatdog works - so what does this tell me about the
Toshiba and why it can't load Windows?

- brevity snip -

"Java Jive" wrote in message
news
On 17/03/2018 22:38, HB wrote:
I have no idea what any of this means:

I've not seen that before either, however ...

I burned it to a disc (Puppy), turned the Toshiba on, and it says this:

done (in green, upper right hand corner.)
Loading drivers needed to access disk drives.

Good - as others have said, it shows that your BIOS settings are
sufficient to boot from the media you used, and that the PC is bootable.

Searching for Puppy files in
computer disk drives. (The in RED is says), fd64-500. sfs not found.

I can't find a reference to fd64-500.sfs as such, only ...

http://gorgeaccess.net/fatdog/ro/ind...ge=Sfs%20files

"An sfs file is a file system that is merged with your normal file system
at boot.

... (it then lists the following, the first is repeated 3 times with
different values of z = 0, 1, 2, but I wouldn't have expected the absence
of any of them to be a show stopper such as you encountered) ...

fd64-devx_5z0.sfs
Devx - for compilation and development.
Part of Fatdog64 proper.
Note: This is only for Fatdog 5z0

... (finally, and the absence of this might be a show stopper) ...

fd64-32bit-libs-7.sfs
Compatibility library for running 32-bit applications.
Re-packaged for Fatdog from Quirky 1.1, Fatdog's little brother."

Perhaps you didn't quite copy the file name right? At any rate see below
...

I downloaded this version of Fatdog64-702 Dec 2016 (as someone here
recommended). It saw and loaded Fatdog. Fatdog works - so what does this
tell me about the Toshiba and why it can't load Windows? It seems to work
fine on the Toshiba but I would like to run Windows on this PC.... where do
I go from here?


Dropping out to intitial-ramdisk console. /bin/sh :can't acess tty; job
control turned off # -

It's encountered a show-stopping error and tried to drop out to a command
console or shell, the Linux equivalent of what in Windows is sometimes
called a command prompt or a DOS box. However, I'm not sure from the
above whether or not it actually succeeds in getting to a command prompt
that you can use. If it does, there might some commands that you can give
there which might be useful.

So the next question is ...

What happens when you try to enter something harmless (where obviously
Enter means press the Enter or Return key):

1) First type this, it should give you a directory listing ...
ls -alEnter

2) Next try this ...
which shEnter
... which should give you a path name, most probably ...
/bin/sh

Try this and report back to us.

I'm not familiar with this particular Linux distro, so can someone else
tell us:
Would lilo would be available in such a command shell?
If not, would it be on the media and what command to install it?
If not, would the network be running?
If not, could the network it be started, and by what command?
What command to install lilo via the network?

Ditto for either fdisk or cfdisk.

That's it with Puppy. What next?

If you get a usable command shell, that's not it with Puppy!

"Java Jive" wrote in message
news
On 18/03/2018 11:43, Java Jive wrote:

I'm not familiar with this particular Linux distro, so can someone else
tell us:
Would lilo would be available in such a command shell?

I suppose I should've asked HB also to try typing:
lilo --helpEnter


In Linux I see nowhere to type anything. Linux can only run with the DVD in
the drive. When I removed the DVD, no more Linux. what does this tell us?

"Rene Lamontagne" wrote in message
...
On 03/17/2018 5:52 PM, HB wrote:
"J. P. Gilliver (John)" wrote in message
...

It isn't that complicated once you grasp what we're trying to do at each
stage! Time consuming, yes. The first thing we're trying to do is
establish whether the HD is actually faulty or just corrupted.
[]

I reburned puppy500 with a different Burner, making sure TWICE it was set
to
OSI, but the result was the same.

It seems to need fd64-500.sfs which wasn't found. I have no idea what
tty
is.

What's going wrong?




OK, I will jump in and try to help, What you need to download is
Fatdog64-721.ISO,
second from the bottom on Pauls index page. that should get you on track


Rene


I did that and burned it as an ISO file. The computer can run Linux but only
from the DVD. When I removed the DVD, no more Linux. I get the same "Disk
read error occured" error. It did not install on the Toshiba.