Win 98 Bootup Problem

In message <4A7C5AA6.7744A61F.DeleteThis@uslink.net>, Scott <golden.DeleteThis@uslink.net>
writes:
[]
>> UPDATE: Today when I booted up, it came up in the lowest video
>>resolution and the

Did it say "Safe mode" in all four corners?

>> desktop wouldn't load. When I rebooted, it said it needed to run
>>Scanreg to fix a
>> problem in the registry. It did and then rebooted in just 40-seconds,

Did Scanreg say it had found anything?

>>instead of
>> the usual 60-seconds. It hasn't booted that fast in a long time.
>>
>> The only thing different is that the "C" drive shows as: "Tlog txt@
>>(C)". It won't
>> let me rename it when I right click and hit Properties.

Hmm. I think the volume name is kept in a sector very near the beginning
of the disc; if that's getting corrupted, definitely time to think about
a new drive, though I think you've said you've done the manufacturer's
thorough diagnostic and it showed all is well, so it might not be the
drive. You could try renaming it in DOS (IIRR the command is "label",
and it might also be possible to do it from the "format" command - type

label /?

(and similar with format) in DOS to find out. (Also try

help label

etc. - the help text is generally better than the "/?" text, but isn't
there for all commands.)
>>
>> Otherwise, everything is working well.
>>
>> Here's the autoexec.bat:
>>
>> SET MSINPUT=C:\MSINPUT

Something is looking - or was once - for an environment variable called
"MSINPUT", which contained the location of a certain directory. If you
don't have the directory C:\msinput, you can delete that line.

>> SET BLASTER=A220 I5 D1 T4

Sets the base address, IRQ number, and I forget the other two, of your
SoundBlaster (or equivalent) audio card (or built-in audio circuitry),
for any DOS application that needs it. If you use any DOS applications
that use sound and it's working OK, this line is correct. If you don't,
it's still probably not doing any harm; it might be of mild interest to
see if the parameters are the same as in Windows in the Properties of
the sound hardware in Device Manager.

>> rem - By Windows Setup - C:\WINDOWS\COMMAND\mscdex /d:mscd001

This machine has been upgraded from pre-Windows 9x, I think. For DOS to
be able to use a CD-ROM drive, there needs to be an mscdex line in
autoexec.bat, and a driver line in config.sys, both with the same bit
after d: (which here I think stands for Drive, rather than signifying
that it is drive d:, though it usually is. Windows '9x doesn't need them
(except in very unusual circumstances), since it has intrinsic CD-ROM
drive support, so REMs out the line when you install it.

>> \L

I'm assuming that was on the end of the mscdex line; IIRR, it specifies
that the CD-ROM drive be drive Letter D.

>> echo Type D: (ENTER)to access the drive

That would have put that line (after the word echo) onto the screen.
>>
>> REM @IF ERORRLEVEL 1 PAUSE

That line, originally, would have put "press any key to continue" on the
screen, and then paused until you did, in the event of a certain error
having occurred; however, with the REM at the beginning, it doesn't do
anything. (REM is short for remark - any line starting with REM is
considered just a comment and ignored. Similarly any line starting with
; [i. e. a semicolon].)
>>
>> And the config sys (which, for some reason is labeled: "config.syd"):
>>
>> device=C:\cdrom\mtmcdai.sys /d:mscd001

The partner line to the mscdex line in autoexec.bat, to do with CD-ROM
drives.

>> device=C:\WINDOWS\himem.sys

Makes DOS use memory better (within the 640K/1M that DOS can use). (This
is quite complex; I can't remember the details!)

>> device=C:\WINDOWS\cwdinit.exe /A

I don't recognise that one! Sounds like it is initialising cwd, which
rings a faint bell, but can't remember why.
>>
>> Also, in MSDOS, when I type in MSD, it says there is no such file.

Try - in DOS -

c:
cd \
dir /s /p msd*.*

(which means: make sure I'm on drive C:; make sure I'm in the root
directory; see if there's a file whose name begins with msd anywhere
below that directory [i. e. anywhere on drive C:], and pause every
screenful.) It might conceivably be in some folder that isn't in the
path; since I don't see a PATH statement in any of what you've given us,
that seems likely. If it shows up that there is an msd.exe file in, for
example, a directory called DOS, then typing \DOS\MSD should run it.

>>
>> Any thoughts?
>>
>> Scott
>
>
>How can I rename the "C" drive?
>
>Thanks!
>Scott

I think the LABEL command (in DOS) is worth a try. Though why you can't
rename it from within Windows I don't know, and it is slightly worrying.
--
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. **

I didn't get the documentation for the manuals.

"Scott" <golden.DeleteThis@uslink.net> wrote in message
news:4A7CA910.F37B1C78@uslink.net
> "J. P. Gilliver (John)" wrote:
>>
>> In message <4A7C5AA6.7744A61F.DeleteThis@uslink.net>, Scott <golden.DeleteThis@uslink.net>
>> writes:
>> []
>> >> UPDATE: Today when I booted up, it came up in the lowest video
>> >>resolution and the
>>
>> Did it say "Safe mode" in all four corners?
>>
>> >> desktop wouldn't load. When I rebooted, it said it needed to run
>> >>Scanreg to fix a
>> >> problem in the registry. It did and then rebooted in just 40-seconds,
>>
>> Did Scanreg say it had found anything?
>>
>> >>instead of
>> >> the usual 60-seconds. It hasn't booted that fast in a long time.
>> >>
>> >> The only thing different is that the "C" drive shows as: "Tlog txt@
>> >>(C)". It won't
>> >> let me rename it when I right click and hit Properties.
>>
>> Hmm. I think the volume name is kept in a sector very near the beginning
>> of the disc; if that's getting corrupted, definitely time to think about
>> a new drive, though I think you've said you've done the manufacturer's
>> thorough diagnostic and it showed all is well, so it might not be the
>> drive. You could try renaming it in DOS (IIRR the command is "label",
>> and it might also be possible to do it from the "format" command - type
>>
>> label /?
>>
>> (and similar with format) in DOS to find out. (Also try
>>
>> help label
>>
>> etc. - the help text is generally better than the "/?" text, but isn't
>> there for all commands.)
>> >>
>> >> Otherwise, everything is working well.
>> >>
>> >> Here's the autoexec.bat:
>> >>
>> >> SET MSINPUT=C:\MSINPUT
>>
>> Something is looking - or was once - for an environment variable called
>> "MSINPUT", which contained the location of a certain directory. If you
>> don't have the directory C:\msinput, you can delete that line.
>>
>> >> SET BLASTER=A220 I5 D1 T4
>>
>> Sets the base address, IRQ number, and I forget the other two, of your
>> SoundBlaster (or equivalent) audio card (or built-in audio circuitry),
>> for any DOS application that needs it. If you use any DOS applications
>> that use sound and it's working OK, this line is correct. If you don't,
>> it's still probably not doing any harm; it might be of mild interest to
>> see if the parameters are the same as in Windows in the Properties of
>> the sound hardware in Device Manager.
>>
>> >> rem - By Windows Setup - C:\WINDOWS\COMMAND\mscdex /d:mscd001
>>
>> This machine has been upgraded from pre-Windows 9x, I think. For DOS to
>> be able to use a CD-ROM drive, there needs to be an mscdex line in
>> autoexec.bat, and a driver line in config.sys, both with the same bit
>> after d: (which here I think stands for Drive, rather than signifying
>> that it is drive d:, though it usually is. Windows '9x doesn't need them
>> (except in very unusual circumstances), since it has intrinsic CD-ROM
>> drive support, so REMs out the line when you install it.
>>
>> >> \L
>>
>> I'm assuming that was on the end of the mscdex line; IIRR, it specifies
>> that the CD-ROM drive be drive Letter D.
>>
>> >> echo Type D: (ENTER)to access the drive
>>
>> That would have put that line (after the word echo) onto the screen.
>> >>
>> >> REM @IF ERORRLEVEL 1 PAUSE
>>
>> That line, originally, would have put "press any key to continue" on the
>> screen, and then paused until you did, in the event of a certain error
>> having occurred; however, with the REM at the beginning, it doesn't do
>> anything. (REM is short for remark - any line starting with REM is
>> considered just a comment and ignored. Similarly any line starting with
>> ; [i. e. a semicolon].)
>> >>
>> >> And the config sys (which, for some reason is labeled: "config.syd"):
>> >>
>> >> device=C:\cdrom\mtmcdai.sys /d:mscd001
>>
>> The partner line to the mscdex line in autoexec.bat, to do with CD-ROM
>> drives.
>>
>> >> device=C:\WINDOWS\himem.sys
>>
>> Makes DOS use memory better (within the 640K/1M that DOS can use). (This
>> is quite complex; I can't remember the details!)
>>
>> >> device=C:\WINDOWS\cwdinit.exe /A
>>
>> I don't recognise that one! Sounds like it is initialising cwd, which
>> rings a faint bell, but can't remember why.
>> >>
>> >> Also, in MSDOS, when I type in MSD, it says there is no such file.
>>
>> Try - in DOS -
>>
>> c:
>> cd \
>> dir /s /p msd*.*
>>
>> (which means: make sure I'm on drive C:; make sure I'm in the root
>> directory; see if there's a file whose name begins with msd anywhere
>> below that directory [i. e. anywhere on drive C:], and pause every
>> screenful.) It might conceivably be in some folder that isn't in the
>> path; since I don't see a PATH statement in any of what you've given us,
>> that seems likely. If it shows up that there is an msd.exe file in, for
>> example, a directory called DOS, then typing \DOS\MSD should run it.
>>
>> >>
>> >> Any thoughts?
>> >>
>> >> Scott
>> >
>> >
>> >How can I rename the "C" drive?
>> >
>> >Thanks!
>> >Scott
>>
>> I think the LABEL command (in DOS) is worth a try. Though why you can't
>> rename it from within Windows I don't know, and it is slightly worrying.
>> --
>> 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. **
>>
>> I didn't get the documentation for the manuals.
>
> J.P.
>
> Great advice! I went into DOS and typed "Label". I hit enter for "no
> label", booted up, and the "c" drive is labeled "c" as it should be...so
> all is well there.
>
> I'll try typing "MSD" when in DOS next time.
>
> Thanks for the info on autoexec.bat and config.sys. My inclination is
> that since everything's
> working fine, I would be best served by leaving well enough alone.
>
> Bootup is now faster than before (just 40-seconds)...which is the way it
> used to be. Bootups have been normal since doing the SCANREG today and
> letting it load the last good configuration.
>
> As I recall, the bootup became 20-sec longer when I installed Acronis
> Image sofware a few years back. It's still installed. I do an image
> backup from the Acronis rescue boot disk, which installs at
> bootup...since it can't seem to find the USB external drive when in
> Windows.
>
> So, now I have a normal bootup...and a faster bootup. So, everything is
> working okay.
>
> Thanks for all your excellent help and advice!
>
> Scott

As J.P. stated, you should be able to remove the command SET
MSINPUT=C:\MSINPUT in autoexec.bat. Instead of deleting the command, type
REM and press the spacebar once in front of the command. A command line
that has the REM command (aka REMARK) preceeding it will be bypassed and not
read/used. If you later find somthing is not properly working, remove the
REM to enable that command line to be read/used again.

Now for the reason why I think the command SET MSINPUT=C:\MSINPUT isn't
needed.
IIRC that command is used to load specific .ini or other file(s) for a
device used in the DOS environment, such as the mouse or keyboard.
Still IIRC, there should be another command line below the SET
MSINPUT=C:\MSINPUT command such as:

C:\MSINPUT
or
C:\MSINPUT\MOUSE\MOUSE.EXE /Q

Now if that directory isn't present in Explorer there's not any purpose
for it. If it is present you may want to take a look at any .ini file
that's in it to see what it's used for. Although I think otherwise, who
knows, it may be possible ATI added it so the mouse and/or kb can be used
for it in DOS.


--

Brian A. Sesko
Conflicts start where information lacks.
http://basconotw.mvps.org/

Suggested posting do's/don'ts: http://www.dts-l.org/goodpost.htm
How to ask a question: http://support.microsoft.com/kb/555375

Scott wrote:
> Scott wrote:
>>
>> My Win98 desktop has had a problem booting up twice recently. After
>> recognizing
>> the CD ROM, it starts displaying lines and lines of drivers, plus
>> MSD, MSD MSD
>> MSD, etc. After shutting it down a few times, it reboots normally.
>>
>> Is this a registry problem?
>>
>> Other than entering "scanrag /restore" the next time this happens,
>> is there something I can do to prevent this from happening again?
>>
>> Thanks!
>> Scott
>
> UPDATE: Today when I booted up, it came up in the lowest video
> resolution and the desktop wouldn't load. When I rebooted, it said it
> needed to run Scanreg to fix a problem in the registry. It did and
> then rebooted in just 40-seconds, instead of the usual 60-seconds. It
> hasn't booted that fast in a long time.

When Windows detects a problem with the Registry during boot, it will
revert to an older copy if one exists. Otherwise, it runs "ScanReg
/Fix". Let us see your Registry backups...

"START button, Programs, MS-DOS Prompt". Then...
(a) CD C:\Windows\Sysbckup
(b) DIR RB???.cab /od
(c) Use the "Mark" button, outline text with mouse, "Copy" & post for
inspection.

Here was mine on 09-22-05...

C:\>CD C:\Windows\Sysbckup
C:\WINDOWS\SYSBCKUP>dir rb???.cab /od /a
Directory of C:\WINDOWS\SYSBCKUP
RBBAD CAB 1,593,319 09-08-05 5:22p rbbad.cab
RB001 CAB 1,590,251 09-18-05 3:34p rb001.cab
RB002 CAB 1,589,811 09-19-05 9:15a rb002.cab
RB003 CAB 1,583,534 09-20-05 8:53a rb003.cab
RB004 CAB 1,583,487 09-21-05 10:01a rb004.cab
RB005 CAB 1,583,477 09-22-05 11:54a rb005.cab
6 file(s) 9,523,879 bytes

Note, on 9/8 I did a Scanreg /Fix, which created the RBbad. It is also
created when Windows decides on it's own to replace a Registry with one
of the backups. Then, the Registry that was replaced ends up in RBbad.

> The only thing different is that the "C" drive shows as: "Tlog txt@
> (C)". It won't let me rename it when I right click and hit
> Properties.

That's troubling to contemplate, but I see Gilliver had a fix.

> Otherwise, everything is working well.

You should make a full system backup immediately! Do you have software
for that? Backup the whole thing preferably to a separate hard drive or
to CD-ROM or DVD-ROM. You've been having scary problems!

> Here's the autoexec.bat:
>
> SET MSINPUT=C:\MSINPUT
> SET BLASTER=A220 I5 D1 T4
> rem - By Windows Setup - C:\WINDOWS\COMMAND\mscdex /d:mscd001
> \L
> echo Type D: (ENTER)to access the drive
>
> REM @IF ERORRLEVEL 1 PAUSE

I think Gilliver explained all that fairly well. One way to use your
CD-ROM after a direct boot to DOS, is to activate the mscdex line by
removing the REM a words before...

C:\WINDOWS\COMMAND\mscdex /d:mscd001 \L

Or put that line into DOSStart.bat (in C:\Windows) & type DOSStart at a
True DOS prompt, if you boot there directly. (DOSStart.bat executes
automatically upon a Restart in MS-DOS Mode from the Shut Down menu.)
That's the way I do it. Here is my full DOSStart.bat...

.......Quote C:\Windows\DOSStart.bat..........
@echo off
LH C:\WINDOWS\COMMAND\MSCDEX.EXE /D:IDECD001 /M:12
LH C:\WINDOWS\SmartDrv
LH C:\WINDOWS\Command\DOSKey

mode con lines=50
c:\mouse\mouse.exe
REM C:\ESSAUDIO.COM
......EOQ C:\Windows\DOSStart.bat.............

Also, you must activate Config.sys with its mtmcdai line-- not
Config.syd.

> And the config sys (which, for some reason is labeled: "config.syd"):
>
> device=C:\cdrom\mtmcdai.sys /d:mscd001
> device=C:\WINDOWS\himem.sys
> device=C:\WINDOWS\cwdinit.exe /A

Config.syd is a backup of Config.sys made by SysEdit...
http://support.microsoft.com/kb/130517
How to Modify Config.sys in Windows 95

Here is a fit/proper C:\Config.sys for you...

DEVICE=C:\Windows\HIMEM.sys /V
DEVICE=C:\Windows\EMM386.exe NOEMS V
DOS=HIGH,UMB,AUTO
DEVICE=C:\cdrom\mtmcdai.sys /d:mscd001
DEVICE=C:\WINDOWS\cwdinit.exe /A
FILESHIGH=80
BUFFERSHIGH=40,4
SHELL=C:\Command.com /P /E:2048

But ensure you do have a file named mtmcdai.sys in C:\cdrom. (I have a
different file than that & in a different folder.)

Also, ensure you have a cwdinit.exe in C:\Windows. Here is a Google
search on that...
http://www.google.com/search?hl=en&q=cwdinit.exe&btnG=Google+Search
It comes up with about 1,190 hits, & it seems to relate to a Yamaha
sound card & will give you sound in True DOS.

> Also, in MSDOS, when I type in MSD, it says there is no such file.
>
> Any thoughts?

Search for MSD.exe as Gilliver said. But nothing in Autoexec.bat seems
to be invoking it. Maybe look in the rest of the Startup Group...

"START button, Run, MSInfo32, Software Environment, Startup Programs"

Use the Edit menu to copy & post the Startup Group.

> Scott

--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
Should things get worse after this,
PCR
pcrrcp DeleteThis @netzero.net

In message <emGCJw7FKHA.1336.DeleteThis@TK2MSFTNGP05.phx.gbl>, Brian A.
<gonefish'n@afarawaylake.?.invalid> writes:
>"Scott" <golden.DeleteThis@uslink.net> wrote in message
>news:4A7CA910.F37B1C78@uslink.net
>> "J. P. Gilliver (John)" wrote:

(Note the bit it brackets; nobody seems to see that for some reason!)
[]
>>> >> device=C:\WINDOWS\cwdinit.exe /A
>>>
>>> I don't recognise that one! Sounds like it is initialising cwd, which
>>> rings a faint bell, but can't remember why.

PCR suggests it's something to do with a Yamaha sound card. If you have
the .exe file it mentions, you probably have the relevant sound card.
(Doesn't make the BLASTER line earlier invalid though - that enables any
DOS prog./game that expects to find a Soundblaster card to work; most
sound cards can emulate a Soundblaster, as it was the default at one
time.)
[]
>> J.P.

[See above comment (-:]
>>
>> Great advice! I went into DOS and typed "Label". I hit enter for "no
>> label", booted up, and the "c" drive is labeled "c" as it should be...so
>> all is well there.

You could always label it "Scott's"!
[]
>> Thanks for the info on autoexec.bat and config.sys. My inclination is
>> that since everything's
>> working fine, I would be best served by leaving well enough alone.

I forgot to say that if it's called config.syd, or whatever it was,
it'll be being ignored; lots of things which, on installation, modified
the config.sys and/or autoexec.bat file(s), used to do so by copying
it/them, renaming one of them (often to .000, .001 etc., or .bak, but
sometimes just by changing the last letter of the extension), and
editing the remaining copy. I presume something has at some time done
this in your system, and then something else has removed config.sys
completely. A Win9x system will (usually) work quite happily without one
or both being present at all. However, you might as well remove at least
the mscdex line from autoexec.bat, since it won't work at all (i. e.
give you CD-ROM drive access in DOS) without its matching line in
config.sys (which does have to be called config.sys, not anything
similar). On the other hand, I think - I've deleted it now - that line
was REMmed out anyway, so won't cause anything other than an
unmeasurable extra delay during booting, so you might as well leave it
in case you ever need it. (If you actually need CD-ROM access in true
DOS ever, booting from a '98 boot floppy [I think not a '95 one] will
give you it anyway.)
[]
>> So, now I have a normal bootup...and a faster bootup. So, everything is
>> working okay.

I'd strongly recommend running ERU; this provides a reasonable backup of
about a dozen files, into a directory of _your_ choice and which won't
be overwritten, along with a (DOS-runnable) utility that restores them,
should you ever need to. I've used it to get me out of a hole (i. e.
back to a working system, even when Windows won't load) more than once.
>>
>> Thanks for all your excellent help and advice!

Yr wlcm.
>>
>> Scott
>
> As J.P. stated, you should be able to remove the command SET
>MSINPUT=C:\MSINPUT in autoexec.bat. Instead of deleting the command,
>type REM and press the spacebar once in front of the command. A
>command line that has the REM command (aka REMARK) preceeding it will
>be bypassed and not read/used. If you later find somthing is not
>properly working, remove the REM to enable that command line to be
>read/used again.

I'd agree with that. (As I said, looking to see if the mentioned
directory exists is an easy first step; if it doesn't, then deleting the
line is definitely on, as it just sets something to point to something
that isn't there anyway.)
[]
--
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. **

I didn't get the documentation for the manuals.

"J. P. Gilliver (John)" <G6JPG.DeleteThis@soft255.demon.co.uk> wrote in message
news:oI+xNaoUEYfKFwuT@soft255.demon.co.uk
>
> (Note the bit it brackets; nobody seems to see that for some reason!)
> []
>>>> >> device=C:\WINDOWS\cwdinit.exe /A
>>>>
>>>> I don't recognise that one! Sounds like it is initialising cwd, which
>>>> rings a faint bell, but can't remember why.
>
> PCR suggests it's something to do with a Yamaha sound card. If you have
> the .exe file it mentions, you probably have the relevant sound card.
> (Doesn't make the BLASTER line earlier invalid though - that enables any
> DOS prog./game that expects to find a Soundblaster card to work; most
> sound cards can emulate a Soundblaster, as it was the default at one
> time.)
> []

The cwdinit.exe file is CrystalWare Device Initialization software used on
a DOS boot disk.for a CrystalWare Audio Device. Thinking on it, should'nt
there be a command like - DEVICEHIGH=C:\WINDOWS\CWDINIT.exe /A - in the
autoexec.bat for it?

<snipped>
--

Brian A. Sesko
Conflicts start where information lacks.
http://basconotw.mvps.org/

Suggested posting do's/don'ts: http://www.dts-l.org/goodpost.htm
How to ask a question: http://support.microsoft.com/kb/555375


..

A corrupted volume label is a good sign of a faulty disk, or perhaps flaky
memory. But since it is now working well, or even better than before, then
I would guess it is a start up or warmup problem, and since the disk has
passed diagnostics OK then I would tend towards suspecting faulty memory.

The existence or otherwise of MSD is not relevant - the question is why is
somehow appeared during those boots. If it is flaky memory, then it's even
possible that the actual message is accidental. I have seen a memory fault
where it was possible to translate the message back to what it should have
been by looking at the bitcode for the letters and working out which bit was
stuck on or off. Same thing for the volume label - if you know what it was
before it got corrupted, it might be interesting to compare the bits.
--
Jeff Richards
MS MVP (Windows - Shell/User)
"Scott" <golden RemoveThis @uslink.net> wrote in message
news:4A7CA910.F37B1C78@uslink.net...
>
>
> snip <
>
> Great advice! I went into DOS and typed "Label". I hit enter for "no
> label", booted
> up, and the "c" drive is labeled "c" as it should be...so all is well
> there.
>
> I'll try typing "MSD" when in DOS next time.
>
> Thanks for the info on autoexec.bat and config.sys. My inclination is that
> since
> everything's
> working fine, I would be best served by leaving well enough alone.
>
> Bootup is now faster than before (just 40-seconds)...which is the way it
> used to be.
> Bootups have been normal since doing the SCANREG today and letting it load
> the last
> good configuration.
>
> As I recall, the bootup became 20-sec longer when I installed Acronis
> Image sofware
> a few years back. It's still installed. I do an image backup from the
> Acronis rescue
> boot disk, which installs at bootup...since it can't seem to find the USB
> external
> drive when in Windows.
>
> So, now I have a normal bootup...and a faster bootup. So, everything is
> working okay.
>
> Thanks for all your excellent help and advice!
>
> Scott