Windows 95 Start-Up Problem
Pyrus Torrel
I was recently given a old computer. An IBM Aptiva, model 2176-C67 with
Windows 95 installed on it, but I wasn't given an installation or backup disk.
When I start the computer it checks the memory, the diskette drive, CD
drive, starts the antiviral program, and checks or starts some things
relating to DOS that I don't really remember.
Then I get the message, "data error reading C drive" followed by the prompt
line: "Abort, Retry, Fail?" Choosing retry or fail results in the prompt line
repeating. Choosing Abort results in a different prompt: "C:>//."
Is this a problem with the computer as a whole?
Is this a problem with the C drive or the data on it?
Is this a problem with the OS program?
What do I do about it?
MEB
Hi, glad you made it. Sorry about your reception in the other group.
As mentioned elsewhere, you may have a failing disk, however, other
issues may be involved.
Have you tried running scandisk to check the drive?
Either use the hard drive commend prompt by:
press and hold down the CTRL key, or
tapping f8 [to get to the boot menu then using the Command Prompt] or
by using a boot disk.
If you don't have a Emergency Boot Disk then you can download one from:
http://www.bootdisk.com/bootdisk.htm
I can't find the specs for your particular computer, it would likely
have version B [or OSR2 - C] since it is an OEM.
What you then do is type scandisk c:
I presume you are familiar with the program, if not post further
questions or if you have additional issues.
Just in case:
Error Message: ScanDisk Cannot Check Drive
http://support.microsoft.com/kb/154998
Windows 98 or Windows 95 Startup Disk Tools and Capabilities
http://support.microsoft.com/kb/259066
--
MEB
http://peoplescounsel.org/ref/windows-main.htm
Windows Info, Diagnostics, Security, Networking
http://peoplescounsel.org
The "real world" of Law, Justice, and Government
___---
Hot-text
"MEB" <MEB-no...@hotmail.com> wrote in message
news:#rw8Bgxn...@TK2MSFTNGP06.phx.gbl...
J. P. Gilliver (John)
>On 01/27/2010 12:03 AM, Pyrus Torrel wrote:
>> I was referred here from the Security Discussions Group board for
>>this problem:
>>
>> I was recently given a old computer. An IBM Aptiva, model 2176-C67 with
>> Windows 95 installed on it, but I wasn't given an installation or
>>backup disk.
>> When I start the computer it checks the memory, the diskette drive, CD
How much memory (and hard disc, if you can tell that) does it actually
have? (Hint: this is one of the few places where the Pause key - on the
keyboard - is actually of use. [You get out of "paused" by pressing
enter.])
>> drive, starts the antiviral program, and checks or starts some things
>> relating to DOS that I don't really remember.
>> Then I get the message, "data error reading C drive" followed by the prompt
>> line: "Abort, Retry, Fail?" Choosing retry or fail results in the
>>prompt line
>> repeating. Choosing Abort results in a different prompt: "C:>//."
Really, with two forward slashes and a dot?
>> Is this a problem with the computer as a whole?
_Probably_ not. It's doing the BIOS checks (I presume without error
messages).
>> Is this a problem with the C drive or the data on it?
That's the most likely.
>> Is this a problem with the OS program?
Probably; could also be a problem with something that's set to run at
startup, though that would normally be after the GUI has loaded, unless
it's a(nother) DOS prog..
>> What do I do about it?
>>
Well, let's see what MEB's suggestions result in. Read on:
>
>Hi, glad you made it. Sorry about your reception in the other group.
>
> As mentioned elsewhere, you may have a failing disk, however, other
>issues may be involved.
>
> Have you tried running scandisk to check the drive?
>
> Either use the hard drive commend prompt by:
> press and hold down the CTRL key, or
> tapping f8 [to get to the boot menu then using the Command Prompt] or
>
>by using a boot disk.
>
> If you don't have a Emergency Boot Disk then you can download one from:
>http://www.bootdisk.com/bootdisk.htm
>
> I can't find the specs for your particular computer, it would likely
>have version B [or OSR2 - C] since it is an OEM.
>
(Hopefully OSR2, ideally B.)
>
> What you then do is type scandisk c:
(and press Enter of course.)
>
> I presume you are familiar with the program, if not post further
>questions or if you have additional issues.
If scandisk finds errors and offers to fix them, it might be best to
decline the offer at first, just to see how many it finds; if a lot, and
they're random, then the disc probably is on the way out. If not a lot,
or they're in a discernible pattern, then it _might_ not be; if you do
another scan later, see if the number of bad sectors is increasing.
Depends what you want to do with the computer. If it's just for
curiosity, you could let scandisk try to fix errors, especially if you
feel the disk is OK. If you want to see what's on the disc, you could
take it (the disc) out and put it in an external box on another computer
(including the "poor man's box", i. e. just a cable and power supply).
>
> Just in case:
>Error Message: ScanDisk Cannot Check Drive
>http://support.microsoft.com/kb/154998
>
>Windows 98 or Windows 95 Startup Disk Tools and Capabilities
>http://support.microsoft.com/kb/259066
>
If the OS is hosed but the disc is OK (or the disc isn't and you replace
it with another you happen to have), then (almost) any machine capable
of running '95 will also be capable of running '98, if you use 98lite in
sleek mode. (See the litepc site.) I'd say the amount of RAM is more
significant than anything else such as processor speed or disc size;
From what I remember, 16M is the theoretical minimum, but I'd say 32 or
64 to get any of your life back. 128 is enough for most purposes (and
may be the most it can take: I have one which is fully loaded with 4 32M
72"pin" modules, and 32M 72"pin" were expensive and are probably hard to
find - if it can take PC100/PC133 type that should be easier).
You could also - from the point at which you could run scandisk after
booting from the boot disc (or _possibly_ from your C: prompt) try
dir c:\ /s
, which should give you some idea how much is on the disc (if it works,
it'll take a minute or two). If you want to actually examine what it
finds,
dir c:\ /s /p
will pause once a screenful for you to hit (IIRR) enter.
--
J. P. Gilliver. UMRA: 1960/<1985 MB++G.5AL-IS-P--Ch++(p)Ar@T0H+Sh0!:`)DNAf
** http://www.soft255.demon.co.uk/G6JPG-PC/JPGminPC.htm for ludicrously
outdated thoughts on PCs. **
No matter how beautiful a girl is, no matter how much you might love her,
squeeze her tight enough and she'll fart - Joe Barron, quoted by son Fred ("My
Family" creator), RT, 15-21 March 2003
Andrei Akhmetov
Make a boot diskette by using another Windows 95 computer, by right clicking
the drive, selecting format, and choosing to create an MSDOS boot diskette.
Put the floppy into the bad computer, type sys C: A:\
(EXACTLY)
then after it is done, turn the computer off, remove the floppy, and restart
the computer. It should work.
--
(1 __
)-1 v x
Even more complex(Imaginary and real at the same time) than ever
"Hot-text" <hot-...@hotmail.com> wrote in message
news:68B203D3-8C11-4A7B...@microsoft.com...
MEB
> MEB,
> Make a boot diskette by using another Windows 95 computer, by right clicking
> the drive, selecting format, and choosing to create an MSDOS boot diskette.
> Put the floppy into the bad computer, type sys C: A:\
>
> (EXACTLY)
> then after it is done, turn the computer off, remove the floppy, and restart
> the computer. It should work.
Presuming the party has a computer with a floppy drive, and knows how
to create a boot disk, and it happens to be a Win9X computer with the
tools, where we would direct to use the ERB/EBD tool to create the full
Emergency Recovery Disk or via the other methods available.
But we have this:
"but I wasn't given an installation or backup disk" and
"I get the message, "data error reading C drive" followed by the prompt
line:" "Abort, Retry, Fail?"".
Taking that into consideration, I thought it best to advise of a
downloaded EBDisk with the tools to perform some preliminary tests along
with the articles that might help explain some of the tools and
potential errors. This STILL requires the floppy drive availability [and
disk], but negates the attempted use of the hard drive during the
process. *IF* the party posts back with further information, we can then
proceed with such as:
fdisk /status
your suggestion
scandisk
or whatever else might be required, such as checking the BIOS settings
and other factors per:
"I was recently given a old computer. An IBM Aptiva, model 2176-C67",
keyword being *old*.
MEB
Forgot the other considerations:
I also thought that the computer had been "given" with Windows 95,
therefore likely had NOT been plugged in recently, hence again, the boot
disk for preliminary testing. And waiting for a response that had been
achieved and what might have been shown when run since there was this:
"When I start the computer it checks the memory, the diskette drive, CD
> drive, starts the antiviral program, and checks or starts some things
> relating to DOS that I don't really remember. ...", hence we have an
attempted start of Windows, but a disk failure, either code or actual.
Pyrus Torrel
laptop with windows 95 on it that yet another person gave me. I've been able
to start it in safe mode. It has a CD drive installed and I was given an
external floppy drive with it. I wasn't given a reboot disk with this one
either, but I believe you guys suggested I can make one?
Asside from you guys, everyone else I've shown this computer (the desktop
not the laptop) to is urging me to get rid of it either because it is an old
model with possibly too little RAM or because of the C drive error, they feel
it can no longer be of any use.
Currently, to keep the peace where I'm at, it's sitting on the porch until I
can get it to storage, as others feel it's a waste of space.
"MEB" wrote:
> .
>
MEB
> Thank you everyone for all the advice on what to do. I do have an old Toshiba
> laptop with windows 95 on it that yet another person gave me. I've been able
> to start it in safe mode. It has a CD drive installed and I was given an
> external floppy drive with it. I wasn't given a reboot disk with this one
> either, but I believe you guys suggested I can make one?
> Asside from you guys, everyone else I've shown this computer (the desktop
> not the laptop) to is urging me to get rid of it either because it is an old
> model with possibly too little RAM or because of the C drive error, they feel
> it can no longer be of any use.
> Currently, to keep the peace where I'm at, it's sitting on the porch until I
> can get it to storage, as others feel it's a waste of space.
>
Great,, I mean that you have another 95 laptop computer WITH an
external floppy drive in addition to the desktop. Use it to make a
Emergency Boot disk. Hopefully you can dredge up a usable floppy disk.
Lots of places to look, like:
http://www.computorcompanion.com/LPMArticle.asp?ID=93
or
http://www.computerhope.com/boot.htm
Do a "FIND" on the laptop for - ERU, it may be in the System/Options
Folder or within a manufacturer's section/folder. OR the manufacturer
may have a utility to make one included on the laptop computer. Look
around in the programs installed. Also can't hurt to TRY to make an
Emergency Boot disk using the above advise.
OR use that prior link to the boot disk and create one from the image
you will receive from there.
WHEN you get the boot disk made, put it in the desktop drive and
re-boot or boot the computer.
Do the scandisk from the boot disk, watching for excessive amounts of
errors. IF SO, then post back with exactly what type of errors. There
MAY be some tools you can try on the disk.
IF NOT or other system errors or issues, or even if successful, please
post back.
These partial load issues are some times caused by corrupted files or
Fats, and not a completely bad disk. OR as mentioned, the BIOS would
also be good to check prior to giving up should you have issues.
As for the limited memory and hard drive space; most people forget how
limited the world of Windows 95 was. It didn't require much memory until
you added all the junk for the Internet. The one issue I didn't like
with Win95 was it did have some memory handling issues though those
seemed related to adding in the Microsoft browser..
ANYWAY, these computers won't be "screamers", but they certainly are
likely functional and there was a WHOLE lot of games and applications
made for the Win95/98 OSs.
If necessary we might be able to advise how to correctly pull needed
files from the laptop to the desktop if the hard drive is salvageable,
or some other method.
Pyrus Torrel
"MEB" wrote:
> .
>
The laptop is capable of making a system startup disk & a system boot disk.
The startup disk requires only 1 floppy disk, but the boot disk requires 29!
I've made the startup disk, but I'm waiting for payday to purchase enough
disks to make the boot disk. The laptop is running Windows 95 version 4B.
J. P. Gilliver (John)
Torrel <Pyrus...@discussions.microsoft.com> writes:
[]
>The laptop is capable of making a system startup disk & a system boot disk.
>The startup disk requires only 1 floppy disk, but the boot disk requires 29!
>I've made the startup disk, but I'm waiting for payday to purchase enough
>disks to make the boot disk. The laptop is running Windows 95 version 4B.
Wow, I haven't seen W95 on floppies for ages!
http://cgi.ebay.co.uk/Floppy-Disks-Pack-50-1-44MB-Formatted_W0QQitemZ220549364445QQcmdZViewItemQQptZUK_Computing_ComputerComponents_BlankCDsDVDs
?hash=item3359c43add
(or just put 220549364445 into ebay's search box) - 50 for 6.70.
Possibly less at computer fairs (2.70 of the above is postage), but I
haven't looked for floppies for a while, don't know if the dealers bring
many (or any) these days.
--
J. P. Gilliver. UMRA: 1960/<1985 MB++G.5AL-IS-P--Ch++(p)Ar@T0H+Sh0!:`)DNAf
** http://www.soft255.demon.co.uk/G6JPG-PC/JPGminPC.htm for ludicrously
outdated thoughts on PCs. **
Very funny, Scotty. Now beam down my clothes
MEB
>>
> The laptop is capable of making a system startup disk & a system boot disk.
> The startup disk requires only 1 floppy disk, but the boot disk requires 29!
> I've made the startup disk, but I'm waiting for payday to purchase enough
> disks to make the boot disk. The laptop is running Windows 95 version 4B.
The "system startup disk" you are likely referring to is likely the
EBD, or at least that is all it takes for one; unless you are referring
to a floppy formatted with the JUST system files, as in
format A: /F:1.44M /s
or via the Windows interface.
Try typing in -
fdisk /status
- from the commend prompt. IF SO and it shows the partition
information, type in - scandisk c: - on the hard drive on the bad computer.
Your so called "boot disk" is likely the manufacturer's "system
restore" disks, e.g., the manufacturer's startup disks [installing
Win95] with a backup of some of the manufacturer's files for the
specific system.
Windows 95 on floppy was 12 [or maybe 15?, still have a set around here
somewhere] disks, IIRC.
Use the downloadable image from bootdisk.com if you can't figure out
how to make one [a 1 disk floppy with the tools on it] from the laptop.
Alan Edwards
Most of those are formatted to hold 1,7165,224 bytes.
The first set I had was not specially formatted and took 35 disks at
1.44Mb (I still have the labelled disks but the contents have been
overwritten years ago)
...Alan
--
Alan Edwards, MS MVP Windows - Internet Explorer
http://dts-l.com/index.htm
On Fri, 05 Feb 2010 05:01:39 -0500, in
microsoft.public.win95.general.discussion, MEB
Alan Edwards
Make that 1,716,224 bytes
On Fri, 05 Feb 2010 23:26:36 +1100, in
microsoft.public.win95.general.discussion, Alan Edwards
MEB
> FWIW, 29 floppies is what I have for Win95B.
> Most of those are formatted to hold 1,7165,224 bytes.
> The first set I had was not specially formatted and took 35 disks at
> 1.44Mb (I still have the labelled disks but the contents have been
> overwritten years ago)
>
> ...Alan
> --
Okay, so those were the backup off the hard drive of OEM Win95B. Or are
you saying as you received them?
Regretfully I can't find, in the numerous CDs still scattered about, my
WinImage folder backup with MSDOS3.2-6.22, Win3.1, Win3.11, Win95A, etc.
{probably on the foobarred tapes still out}; so I can't say otherwise.
Wikipedia says it was 13 floppies for the retail Win95A version which
coincides with what I remember.
"Windows 95 has been released on both floppy disks and on CD-ROM, as
some computer systems at the time did not include a CD-ROM drive. The
retail floppy disk version of Windows 95 came on 13 DMF formatted floppy
disks, while OSR 2.1 doubled the floppy count to 26. Both versions
exclude additional software that CD-ROM might have featured. Microsoft
Plus! for Windows 95 was also available on floppy disks."
SOURCE:
http://en.wikipedia.org/wiki/Windows_95
And yeah, Microsoft was using the non-standard DMF {1.8} format for its
install disks at the time.
Let's see what I did find; some additional offerings:
Win95A retail upgrade CD {required Win3(+)} - 732 items - 57.6 megs
Win95C CD IBM OEM - install/restore disk "just the OS" - 230 items -
101.1 megs
Win95 Plus CD - 327 items - 31.3 megs
> On Fri, 05 Feb 2010 05:01:39 -0500, in
> microsoft.public.win95.general.discussion, MEB
> <MEB-no...@hotmail.com> wrote:
>
>> Windows 95 on floppy was 12 [or maybe 15?, still have a set around here
>> somewhere] disks, IIRC.
>>
>>
Alan Edwards
Yes, 13 sounds familiar for Win95A. I don't have those any more as I
passed them on with the computer when sold.
Yes, the 29 disks were Win95B, OSR2, 4.000.1111 and I had the CD, not
the disks.
I have is the listing as below: (summary only shown)
Win95 version 4.00.1111 Cabinet File List
Cabinet(s): 30 files, 46,956,734 bytes
Dated: 08-24-96
mini.cab 441,905
precopy1.cab 480,768
precopy2.cab 1,237,083
win95_02.cab 464,896
win95_03.cab 1,716,224
win95_04.cab 1,716,224
win95_05.cab 1,716,224
win95_06.cab 1,716,224
win95_07.cab 1,716,224
win95_08.cab 1,716,224
win95_09.cab 1,716,224
win95_10.cab 1,716,224
win95_11.cab 1,716,224
win95_12.cab 1,716,224
win95_13.cab 1,716,224
win95_14.cab 1,716,224
win95_15.cab 1,716,224
win95_16.cab 1,716,224
win95_17.cab 1,716,224
win95_18.cab 1,716,224
win95_19.cab 1,716,224
win95_20.cab 1,716,224
win95_21.cab 1,716,224
win95_22.cab 1,716,224
win95_23.cab 1,716,224
win95_24.cab 1,716,224
win95_25.cab 1,716,224
win95_26.cab 1,716,224
win95_27.cab 1,716,224
win95_28.cab 1,426,482
Compressed contents: 2544 files, 130,539,134 bytes
I also have a listing on an old PC taken from a set of floppies that
shows win95_22.cab as being the last and that one looks like around 23
disks + bootdisk
Contents 2045 files, 99,312,503 bytes 08/24/96 11:11.10am so it looks
like the same Win95B as above.
It looks like the floppy set of Win95B did not have as much in the cab
files as the CD.
On Fri, 05 Feb 2010 15:42:30 -0500, in
MEB
Yeah, along time ago in the computer world. Heck it was a long time ago
in life...
So anyway, Pyrus still needs the Emergency Boot Disk right now, rather
than the install disk set. And I would burn the full install for the
Toshiba to CD if at all possible rather than floppies. 29 floppy disks
would take AGES to use for an install.
Pyrus Torrel
manuscript, and it's taking a looong time. It may take a while before I can
see if these start-up/reboot disks work. When I actually made the system
reboot disks, they actually took up 28 floppies rather than the 29 the laptop
computer indicated.
"MEB" wrote:
> .
>
MEB
> Sorry it's taking me so long to get back, I'm being kept busy proofreading a
> manuscript, and it's taking a looong time. It may take a while before I can
> see if these start-up/reboot disks work. When I actually made the system
> reboot disks, they actually took up 28 floppies rather than the 29 the laptop
> computer indicated.
>
Ah, good, then you are about to finish in some form. I did notice the
28 disk issue in some B versions. Perhaps the extra disk includes or
rather was to include drivers or INFS... hard to say.. though those ARE
the system install disks, not the ERB disk - the emergency startup/boot
disk.
Don't forget you MAY need to go into the BIOS to set the computer to
boot from the floppy disk, or choose its boot menu then the floppy
[usually via a func + some other key combination [laptop, was there one
for the desktop...hmm], else the initial cold boot screen usually shows
what key or keys need pressed.
Keep us informed as I have continued to monitor here "just in case" you
returned [though that may not have been necessary since Allen apparently
does].
IF you respond or we discuss further issues, a cut of some or all of
the below quoted ">" material may be in order since your issue
revolves/revolved around what might be a scan disk/defrag issue, which I
will include below for potential future reference:
"I was recently given a old computer. An IBM Aptiva, model 2176-C67 with
Windows 95 installed on it, but I wasn't given an installation or backup
disk.
When I start the computer it checks the memory, the diskette drive, CD
drive, starts the antiviral program, and checks or starts some things
relating to DOS that I don't really remember.
Then I get the message, "data error reading C drive" followed by the
prompt line: "Abort, Retry, Fail?" Choosing retry or fail results in the
prompt line repeating. Choosing Abort results in a different prompt:
"C:>//."
Is this a problem with the computer as a whole?
Is this a problem with the C drive or the data on it?
Is this a problem with the OS program?
What do I do about it?"
And where you got the disks you intend to use from:
"I do have an old Toshiba laptop with windows 95 on it that yet another
person gave me."
Pyrus Torrel
"Pyrus Torrel" wrote:
This past Sunday, I finally got a chance to try the system start-up disk and
system boot disks. The operating system is Windows 95 Plus, not just Windows
95. The processor is a Pentium operating at 166 MH.
The system memory is 80 MB.
When I used the start-up disk, the desktop checked memory, showed Windows 95
Plus title screen, checks drives, starts the antiviral program, loads DOS
key. I then got the error message: 'The compression driver can't be set up
correctly using the version on the start-up disk. Get a version compatible
with the version on the desktop from the vendor.' I then got the 'A:\>'
prompt. Turning the computer off & on and trying the start-up disk again got
this additional line with the above-mentioned error message: 'Type the name
of the command interpreter (e.g., C:\>Windows/Command.com)' and then the
afore-mentioned prompt.
When I turned on the computer and tried using the boot disks, I get:
'Invalid system disk. Replace the disk, then press any key.' Doing so gets
results I've already mentioned.
Trying the disks in safe mode didn't work either. Using the start-up disk
gets: 'Windows bypassing startup files. HIMEM testing extended
memory...done.' and then the 'C:\>' prompt. Using the boot disks gets the
'Invalid system disk' message.
I didn't see any options for a system restore or for using the boot disks to
load its version of Windows in place of the computer's version.
MEB
The indication of a "compression driver" should have been a distinct
indication to you. Potentially/Apparently, the disk has been setup with
compression to increase its storage capacity. Your problem now is
determining WHAT application (or IF there is one) was used for the
compression purpose.
There were two (2) versions of MS [actually licensed versions of
another manufacturer's - with minor version updates which were NOT
compatible with the previous - DriveSpace/Doublespace] compression
programs that MIGHT be involved, and several dozen others (including
from IBM) from the potential time period involved. There could
potentially be a hidden IBM SR partition involved as well.
To determine the issue(s) you will need to use a tool to look at the
actual partitions and their "ID" numbers [type of partitions whose
number indicates the potential manufacturers' driver used] by using
something like BootitNG, WinHex, Testdisk, MHDD, HDAT2, or a similar
partition/disk tool. FDisk will not be sufficient in this circumstance.
http://www.terabyteunlimited.com/ - most people in these forums are
familiar with BootitNG
http://hddguru.com/content/en/software/2005.10.02-MHDD/
http://www.hdat2.com/
http://www.cgsecurity.org/wiki/TestDisk_Download - more of a recover tool
Once the partition is identified then removal/handling advice can be
offered. See the ID numbers below:
http://www.win.tue.nl/~aeb/partitions/partition_types-1.html
And we may need you to look at/for a couple files using the command
prompt and/or run some other commands; how are you with the old DOS
methods/commands?
As for using the "Startup disk" and it starting an AV program, it
shouldn't be doing this as the Startup disk should contain NO references
to the ON HD config.sys and/or autoexec.bat. Check the BIOS to ensure
you are NOT still booting from the HD, OR hit the proper "function and
key combination" to boot ONLY from the floppy [should be shown when
system boots on an IBM]. Though it may be due to the creation of these
disks on your other computer [noted elsewhere in the thread]. Remember I
did previously supply you with the bootdisk link for "generic" startup
disks.
Just some general info:
http://ps-2.kev009.com:8081/pcpartnerinfo/ctstips/8522.htm
http://www.easyhelpguide.com/manual/IBM-Aptiva2176C67-Manual.html
> Turning the computer off & on and trying the start-up disk again got
> this additional line with the above-mentioned error message: 'Type the name
> of the command interpreter (e.g., C:\>Windows/Command.com)' and then the
> afore-mentioned prompt.
>
> When I turned on the computer and tried using the boot disks, I get:
> 'Invalid system disk. Replace the disk, then press any key.' Doing so gets
> results I've already mentioned.
>
> Trying the disks in safe mode didn't work either. Using the start-up disk
> gets: 'Windows bypassing startup files. HIMEM testing extended
> memory...done.' and then the 'C:\>' prompt. Using the boot disks gets the
> 'Invalid system disk' message.
>
> I didn't see any options for a system restore or for using the boot disks to
> load its version of Windows in place of the computer's version.
Depending upon the compression program or partitions involved, you will
likely need to FIRST decompress the drive BEFORE removing the
partition(s) {if compressed} involved as physical "jump" and other disk
instructions may have potentially been modified. This was one of the
problems generally associated with the usage of {early} disk compression
[including Microsoft's] and partitioning programs. Merely removing the
partition(s) and re-formatting could/may produce disk errors/failures
due, generally, to FDisk limitations.
Again though, we need to look at the actual partition info on the
computer before doing much more.
Pyrus Torrel
"MEB" wrote:
> .
>
Once again I must apologize for being so slow in replying. On top of being a
chronic procrastinator, the computer in question is in a storage facility
which I only have time on the weekends to visit.
At one point I understood compression, but now I’m reduced to just
knowing that binary data is re-coded to fit into fewer memory locations. By
partitioning, I can only assume that you mean that disk space gets divvied up
and the various portions are used for sets or types of programs or data. I’ve
obviously got lots of learning and re-learning to do on those points.
My knowledge of DOS period is non-existent. Back in the 90's I went to
one of those 3 to 6 month vocational schools that claimed to teach computer
programming, but all they taught was typing, data entry, and using
WordPerfect and Lotus (Using macros was as close to programming as it got!)
on a DOS computer. By the time I graduated, DOS was being phased out and what
I learned was no longer useful (A few years later, that school made the local
news by suddenly closing its doors without warning and leaving the students
of all its programs stuck with paying students loans for training that wasn’t
completed).
It seemed that whether or not I booted from a disk or from the hard
drive, the computer seemed to go through the same start-up sequence: checking
the memory and all the other stuff I mentioned.
I guess Windows as configured on a laptop is different than Windows as
configured on a desktop and that’s why you’re figuring a generic boot disk
might work?
You’ve definitely given my a lot of links to check out. I should’ve
already gone through them all after 2 months, but procrastination will do
that sadly. Being unable to connect the troubled computer to the internet
because I can’t even get as far as the welcome screen, will I be able to use
the tools those links lead to by loading them from a disk?
Thank you once again for your patience and help.