Humph, just at supper-time too. Bully for you, Noel. And I
was hoping to do my first right and proper re-install!
I may just ignore the whole thing since the only problem I
seem too have is the display.sys admonishion just as
Windows boots. 2 or 3 secs. delay. All things considered
(the 'poor' advice g etc) Me has taken everything I had
to give it and still comes up trumpeting. Fast as I like.
BTW Noel there is a typo on your/Koldbear's page:
"for instructions on how to used".
Cheers,
Ben.
-----Original Message-----
Ben's been avoiding a reinstall for almost as long as I
can remember! - I
got around providing an 'idiot's guide' for him by
publishing that pageg
--
Noel Paton (MS-MVP 2002-2004, Win9x)
Nil Carborundum Illegitemi
http://www.btinternet.com/~winnoel/millsrpch.htm
Please read http://dts-l.org/goodpost.htm on how to post
messages to NG's
or
http://www.microsoft.com/presspass/f...2001/Mar01/Mar
27pmvp.asp
"Mart" wrote in message
...
Good luck Ben and be sure to follow the late Koldbear's
advice on Noel's
pages if necessary, for a (reasonably) painless re-
install. If you need to
do a 'clean' install, use the link to Jim Eshelman's
site (aumha) at the
top
of Noel's page.
Mart
"Ben B" wrote in
message
...
Hello Mart,
I note the info on scanreg /restore with interest.
So much was happening with the EBD difficulty that I
am
somewhat confused about when the DISPLAY.SYS first
aappeared, however since I had come across that
particular
file whilst trying to create the EBD I recall thinking
that was the root of the problem. I may have used the
28th. rb.cab restore point. Will try it again and
then if
that doesn't work then I shall use the 12th.May one
and,
in consequence, have some re-installing of freeware
to do.
Will post back when the hair has settled on the floor.
Thanks, Mart.
Ben.
-Original Message-----
It doesn't matter whether you run scanreg /restore in
either Windows or DOS
although there are times when, if you can't get into
Windows - even in Safe
Mode - then the DOS method may be the only solution.
Regarding the dates, don't worry too much about the
order
of rb00X suffix,
they just update until rb005 then start over again.
I was
more concerned
about the dates themselves. The fact that they are
reasonably recent shows
that 'something' is working OK g. Although it is
odd
that you still have
one dated 12th May (unless it is a faulty one)
You didn't say when the windows.sys error started -
again, if only recently
then choose the last one BEFORE that date.
If you do decide to consider re-installing WinMe (but
note Rick's comment
regarding the boot disk only - ...Then you can just
forget about it until it
comes time to reinstall the OS), then I suggest you
take
a look at Noel's
site:
http://www.btinternet.com/~winnoel/reinME.htm
and think through your strategy.
Re-installing will automatically ask if you want to
make
a boot disk and
should also reset the path statements.
It's up to you to decide whether the effort will be
worth
it g
Good luck
Mart
"Ben B" wrote
in
message
...
Hello Mart,
That is very clear. I think? I may have used a too
recent
date on a scanreg /restore AND I did it with
Windows
running! Will give it another go your way - and
post
back.
(Sorry about the dual posts. I wasn't exactly sure
that
was the case.)
I just had a look at the rb* and I have the five
but the
dates are odd. .000 is 29th.May. .001 the 29th.
(later
on). .002 the 30th. .003 missing. .400 the 12th
May!
And .005 the 28th May. I would prefer to wait for
your
response as to which one I might best use. And I
have
just
begun using (29th.early) Delindex 5.0. This
compacts
(amongst many other features) the Registry using
the
command ScanReg.exe /opt. A possible problem?
Thanks, Mart.
Ben.
-----Original Message-----
Ben, for the moment please keep to the one
thread, it's
getting complicated
enough g. Your other (later) topic is related
and is
best continued in
this one.
From what you are reporting, you not only have
lost the
path settings but
you also 'appear' to have a corrupted windows.sys
file
(and others too
perhaps!)
Under the circumstances - and assuming this issue
(the
windows.sys report)
is only recent - try the following with
your 'new' boot
disk (from
bootdisk.com).
Boot, using your Windows Startup (floppy) Disk and
choose
4) Minimal Boot.
At the A:\ prompt, type "scanreg /restore" (no
quotes
and note the space
between the g and /) then press Enter.
Follow the screen prompts and when asked, select
the
LAST 'good' date before
you had problems, continuing with the
instructions.
Don't forget to remove the floppy disk BEFORE you
tell
the machine to
reboot.
See if that helps to get rid of the 'windows.sys'
error
report.
BTW - what dates were offered, i.e how recent were
they? -
They *should* be
five, consecutive (very) recent dates.
If you have got 'corrupted' or damaged (registry)
files,
then you *may* well
have to re-install BUT DON'T GO THERE YET!!
Mart
"Ben B"
wrote in
message
...
Hello Rick,
Good to hear from you. I took that hike and got
the
EBD
program. Easy yes. And from what else you
say 'my'
condition will remain more or less the same
until I
do
that format and install. Time is passing, Rick,
that
might
just be the challenge too far!
Oh and I forgot. In the beginning the word was
update
your
EBD from time to time. Why?
And see my post above for a real snooker!
Cheers,
Ben.
-----Original Message-----
Ben B wrote:
Hello Mart,
Thanks for responding. In the beginning
making an
EBD
was
simple. These days, after I have 'messed
about'
with
my
computer for some years, it is not.
heheh I know that tune.
I am using the same disk each time I try for
the
EBD.
And
each time different files cannot be found. I
find
them
in
BASE2.CAB or WIN9_.CAB or WIN_16.CAB or in
WIN19_.CAB,
and
the EBD is created, I repeat the making and
still
have
to
look for and point at paths. I have all of
the
CABS
involved in C:\WINDOWS\OPTIONS\INSTALL and
still
the
required files cannot all be found.
I have had to copy these four CAB files from
Win9x on
my F
drive. They and others like them! were and
are
not,
on
C.
Any thoughts about my recovering the
innocence of
the
total newbie in this particular regard?
Thanks.
Ben.
well the easy way in this case would be to hike
over to
www.bootdisk.com
and download an EBD-making program (pick their
WinME-
OEM
version). Then
you can just forget about it until it comes
time to
reinstall the OS.
Rick
-----Original Message-----
Search for BASE2.CAB on your hard drive and
make a
note
of its location.
(Probably in the C:\Windows\Options\Install
or
\Cabs
folder)
Then try and create the EBD again, but this
time
when
the
error message
appears, navigate to the location of the
BASE2.CAB
file.
The process should
now continue and complete the WinMe Startup
Disk.
HTH
Mart
"Ben B"
wrote
in
message
news:1532601c445d9$02a4efc0
...
Hello,
I encounter this message when attempting to
make
an
EBD: "Error Details. The following error
occurred: "The
file was not found(error #2). Setup could
not
finish
opening a file on the source disk.
Source file: A:\Autoexec.ebd
Destination file: C:\WINEBD0.400
\EBD\autoexec.bat=
BASE2.CAB"
All the EBD files are subject to the same
error
message.
What are the implications behind the
message?
Help appreciated.
.
.
.
.
.