Archived from groups: microsoft.public.windowsme.general (
More info?)
SM wrote :-
> I had tried renaming, it is just ignored - any attempt to rename, delete,
> or
> overwrite is just ignored.
I meant for you to rename your 'new' copy of tahoma (the one you downloaded
and have to install) BEFORE you actually install it - but on hindsight
(Mikes post) maybe that is not a particularly useful option, your program
may still not recognise it even though you could access the 'new' font in
other applications (e.g. WordPad). But still, it IS an option <g>
> How do you start the computer in Safe Mode, or in DOS?
To get into Safe Mode :- There is an 'Official' (documented) MS method for
WinMe - as per a search for 'safe mode' in Help and Support Centre will
find - by holding down or 'stabbing at' the Ctrl or the F8 keys.
A further couple of 'Unofficial' methods are by using the Shift key as
above, or when your machine is running in Normal Mode, run msconfig.exe and
on the General tab, select Advanced and check the 'Enable Startup Menu' box.
(Not forgetting to disable it when you've finished <g>)
To get into (Real Mode) DOS :- Simply boot, using your WinMe Startup
(floppy) Disk inserted into the A: Drive.
> ... I wonder why
> the providers of the modified version of tahoma are not aware of the
> problem,
> and recommend something that is not implementable - if they are aware of
> the
> problem, why they do not offer a solution on how to overcome the problem,
> or
> develop an alternative method of accessing the necessary fonts.
Something you need to take up with the providers, but either way, I agree
with Noel's point :- "the software makers should not be attempting to
replace system fonts, in any case!".
The consensus is to leave well alone <g> but I suppose you could still try
my first suggestion, above and see if that works.. At least it won't
overwrite the 'official' MS version of tahoma.ttf. The theoretical solutions
are there - it's up to you if you want to implement them.
Mart
"SM" <SM@discussions.microsoft.com> wrote in message
news:F954BD21-B0FC-469E-9E3E-F53AAA9E0DFF@microsoft.com...
> Mart and Mike - Thanks for your response.
>
> I had tried renaming, it is just ignored - any attempt to rename, delete,
> or
> overwrite is just ignored.
>
> How do you start the computer in Safe Mode, or in DOS?
>
> In general, is tahoma protection a matter for Windows ME or is it also
> true
> in other versions of Windows? If it applies to other versions, I wonder
> why
> the providers of the modified version of tahoma are not aware of the
> problem,
> and recommend something that is not implementable - if they are aware of
> the
> problem, why they do not offer a solution on how to overcome the problem,
> or
> develop an alternative method of accessing the necessary fonts.
>
> Thanks again
> SM
>
>
>
> "Mike M" wrote:
>
>> Mart,
>>
>> I don't think renaming will help but Safe Mode may work. Failing that I
>> would boot to DOS as you suggest and replace the existing tahoma.ttf
>> files
>> with the required versions as the registry doesn't record the version and
>> the system should hopefully just use the new font when booted back into
>> Win Me.
>> --
>> Mike Maltby MS-MVP
>> mike.maltby@gmail.com
>>
>>
>> Mart <mart(NoSpam)@nospam.nospam> wrote:
>>
>> > 'Scuse my jumping in Mike <g>
>> >
>> > Two *possible* options :-
>> >
>> > Re-name the 'new' font as Tahoma2 and install it normally in the Font
>> > manager (Control Panel), then select that font in your application -
>> > if it will let you! (And it's a 'poor do' if it won't <g>)
>> >
>> > If you really must, try replacing the font in Safe Mode. It *may*
>> > allow you to do it there, rather than in Normal Mode. Or do it in
>> > (Real Mode) DOS, if necessary!
>>
>>
Facebook
Twitter
Instagram