Paul, I queried the modem and it has 2.03 on it.


> > 2nd question - how do I flash the modem?
>

> You'll need to have a Win ME or older machine to do that, the firmware
> either on this group or at Infoserves website wont work under XP or
> Windows 2000 machines.  Before you attempt to flash the firmware, how do
> you know you haven't already got the latest version?
> >
Paul, I queried the modem and it has 2.03 on it.  So do I just need
ME, W98 or other for the flash operation and then can use it in XP or
does XP rule out ever using 2.04?  If the former, I might try it from
a virtual machine using the Microsoft VM software downloaded and
installed the other day.

Thanks

John

--- In 56solo@yahoogroups.com, "John Kane" <jk2@...> wrote:
<snip>

> Paul, I queried the modem and it has 2.03 on it. So do I just need
> ME, W98 or other for the flash operation and then can use it in XP

Yes, that's exactly the case. I'm using my Solo with my inf on this site
on a Win XP Pro machine. I wouldn't risk flashing it using aVMware
machine, better to find the genuine artical. If a flashing operation is
interupted or goes wrong you may end up with a trashed modem. There's no
hurry so you can use the modem with 2.03 until the opportunity to borrow
a Windows 9.x machine comes along (my inf should still work with it).

Also, no reply to my email from that BVRP PhoneTools lot.  Anybody got
a spare copy lying around?

--- In 56solo@yahoogroups.com, "John Kane" <jk2@...> wrote:
>
>
> Thanks
>
> John
>

--- In 56solo@yahoogroups.com, "John Kane" <jk2@...> wrote:
>
> Also, no reply to my email from that BVRP PhoneTools lot. Anybody got
> a spare copy lying around?

It's not for me to give you a copy of their software but if you contact them through the PhoneTools OEM support forum here: http://support.bvrp.com/phpbb2/viewforum.php?f=14&sid=e8d5b3f18877924a7f1aac33831acb1b (watch the line wrap) there are plenty of cases where they've been providing updated versions for those who've updated their operating systems. If you only have PhoneTools 2 that came on floppy disk with the Pace Solo then it wont work under XP. I've purchased Classic PhoneTools 6 but I actually use PhoneTools 4.21 with Pace Solo specific internal drivers (part of their software). Make sure they get you a version with full support for the Pace Solo as they have many versions which dont properly support it and for example wont show caller id details. The setup I have works fine in that regard.

They will reply during the week if you post to that forum this weekend.

As well as the latest mdmsolo.inf (which is zipped), there's now also
a Windows XP compatible version of PhoneTools which works only
with 'newer' Pace 56 k modems (including the Solo - but I haven't
tested others) at the Infoserve drivers website (on the bottom of the
page) http://www.infoserve.com/drivers/ Complete with instructions.

Paul Murphy wrote:
> As well as the latest mdmsolo.inf (which is zipped), there's now also
> a Windows XP compatible version of PhoneTools which works only
> with 'newer' Pace 56 k modems (including the Solo - but I haven't
> tested others) at the Infoserve drivers website (on the bottom of the
> page) http://www.infoserve.com/drivers/ Complete with instructions.

This is going to be _very_ useful for me. Thanks.
___
Ade

--- In 56solo@yahoogroups.com, adrian@... wrote:
>
> Paul Murphy wrote:
> > As well as the latest mdmsolo.inf (which is zipped), there's now
also
> > a Windows XP compatible version of PhoneTools which works only
> > with 'newer' Pace 56 k modems (including the Solo - but I haven't
> > tested others) at the Infoserve drivers website (on the bottom of
the
> > page) http://www.infoserve.com/drivers/ Complete with instructions.
>
> This is going to be _very_ useful for me. Thanks.
> ___
> Ade

Let me know if you encounter any problems with it. Its' been working
perfectly fine for me under XP but it's nice to receive feedback. It
was good of Infoserve to add it to their downloadable files for Pace
products.

Paul

Hi,

Does anyone have their phone line with TalkTalk, instead of BT?  Just
wondering how well the 56 Solo performs for others using TalkTalk, because
here the caller id function doesn't work most of the time :-(.  Was fine when
the line was with BT.

--
  Oliver Roberts  -  http://www.futaura.co.uk/  -  ICQ: 34640231

  Amiga Formula One site  ==>  http://www.amigaf1.co.uk/

--- In 56solo@yahoogroups.com, Oliver Roberts <oliver@...> wrote:
> Does anyone have their phone line with TalkTalk, instead of BT?

As no body with Talktalk has replied (yet), my line is with Plusnet
and it's performing the same as when it was with BT in terms of CID on
my Solo (works almost all the time apart from some internatioal
calls). What do Talktalk have to say about it?

On Wed, 16 Jul 2008 11:34:54 +0000, Paul Murphy wrote:

> --- In 56solo@yahoogroups.com, Oliver Roberts <oliver@...> wrote:
>> Does anyone have their phone line with TalkTalk, instead of BT?
>
> As no body with Talktalk has replied (yet), my line is with Plusnet
> and it's performing the same as when it was with BT in terms of CID on
> my Solo (works almost all the time apart from some internatioal
> calls). What do Talktalk have to say about it?

I guess I should really have said TalkTalk LLU - i.e. they've completely taken
over the line, unlike Plusnet (IIRC) where your line is probably still
connected to BT's hardware at the exchange.

I am in contact with TalkTalk about it, who are looking into it - it's not a
line issue, since they've done a line test.  I figured that if I knew
somebody else had no problems with the Solo on TalkTalk LLU, that'd give me a
bit more ammunition to tell them it must be a fault on their equipment and
not the Solo :).  Apparently, TalkTalk's Caller ID system is supposed to be
identical to BT's, but there are some minor differences (not just the problem
that I'm having).

It's a strange problem because it works about 50% of the time on average with
the Solo, and 90% of the time on a BT Freestyle handset.  Probably everybody
here knows the tell-tale "click...click"  that the Solo makes directly before
the phone starts to ring, and before it starts to announce the phone number.
With my BT line, this was always a fixed "click...click", but with TT
sometimes it doesn't click at all and as a result picks up no Caller ID at
all (yet, the BT Freestyle does still display the Caller ID most of the time
when this happens).

--
  Oliver Roberts  -  http://www.futaura.co.uk/  -  ICQ: 34640231

  Amiga Formula One site  ==>  http://www.amigaf1.co.uk/

On Wed, 16 Jul 2008 13:12:59 +0100, Gerald wrote:

> I'll chip in and state that Caller ID works with BT and Tescos Homephone
> but not with Virgin Cable.

Yeah, I had virtually no problems with it when I had a BT line.  I remember
people's comments here regarding Virgin Cable, or NTL as it was back then (or
maybe it was even back in the C&W days) - IIRC, they use a different Caller
ID standard - can't remember which, but probably a more widespread
implementation (not BT's own custom "standard").

--
  Oliver Roberts  -  http://www.futaura.co.uk/  -  ICQ: 34640231

  Amiga Formula One site  ==>  http://www.amigaf1.co.uk/

--- In 56solo@yahoogroups.com, Oliver Roberts <oliver@...> wrote:
>
> On Wed, 16 Jul 2008 11:34:54 +0000, Paul Murphy wrote:
>
> > --- In 56solo@yahoogroups.com, Oliver Roberts oliver@ wrote:
> >> Does anyone have their phone line with TalkTalk, instead of BT?
> >
> > As no body with Talktalk has replied (yet), my line is with Plusnet
> > and it's performing the same as when it was with BT in terms of CID on
> > my Solo (works almost all the time apart from some internatioal
> > calls). What do Talktalk have to say about it?
>
> I guess I should really have said TalkTalk LLU - i.e. they've completely taken
> over the line, unlike Plusnet (IIRC) where your line is probably still
> connected to BT's hardware at the exchange.

That's exactly the case with my Plusnet homephone line. Recently my broadband connection started playing up (it was slow and intermittently going out of sync) and they needed to get BT to fix it. Now I'm back to 7616 Kbps downstream and 448 Kbps upstream.

> I am in contact with TalkTalk about it, who are looking into it - it's not a
> line issue, since they've done a line test. I figured that if I knew
> somebody else had no problems with the Solo on TalkTalk LLU, that'd give me a
> bit more ammunition to tell them it must be a fault on their equipment and
> not the Solo :). Apparently, TalkTalk's Caller ID system is supposed to be
> identical to BT's, but there are some minor differences (not just the problem
> that I'm having).

This may be of some help: http://www.ainslie.org.uk/callerid/cli_faq.htm#Q_6 it's a bit old but there's allot of good stuff there.

> It's a strange problem because it works about 50% of the time on average with
> the Solo, and 90% of the time on a BT Freestyle handset. Probably everybody
> here knows the tell-tale "click...click" that the Solo makes directly before
> the phone starts to ring, and before it starts to announce the phone number.
> With my BT line, this was always a fixed "click...click", but with TT
> sometimes it doesn't click at all and as a result picks up no Caller ID at
> all (yet, the BT Freestyle does still display the Caller ID most of the time
> when this happens).

Sounds like there is indeed some sort of different standard (or improper configuration of their system to work to that standard). Maybe the CID data isn't being sent through on a strong enough signal - hence sometimes it's doesn't pass the threshold to activate the old Solo but it's enough to activate a 'lighter weight' CID box? Does unplugging all other devices/loads from the line make it more likely that the Solo will talk to you again?  :-)

If they don't fix it, as Caller ID clearly isn't functioning as it should, I think you should have grounds to get out of any contract and go to another telco. Have you been able to test the Solo on another line, just to make sure it's not the culprit?

By the way, I'm now using Classic PhoneTools 9 retail with the Terminal app add-in, in conjunction with Avanquests special revised tab file (to fix the purple bar on the GUI) and my inf that's listed under files in this group and it's all working together very well. Multi-page faxes even get through to machines where my setup previously had problems after the first page. It's definitely worth the £10 or so it cost me to upgrade to this latest version! The only problem I'm now experiencing is it's very slow to start up now there are more voicemails and faxes stored in the history - it was lightning fast by comparison when I first installed it.

--- In 56solo@yahoogroups.com, Oliver Roberts <oliver@...> wrote:
>
> . . .  Apparently, TalkTalk's Caller ID system is supposed to be
> identical to BT's, but there are some minor differences (not just the problem
> that I'm having).
>
> It's a strange problem because it works about 50% of the time on average with
> the Solo, and 90% of the time on a BT Freestyle handset.  Probably everybody
> here knows the tell-tale "click...click"  that the Solo makes directly before
> the phone starts to ring, and before it starts to announce the phone number.
> With my BT line, this was always a fixed "click...click", but with TT
> sometimes it doesn't click at all and as a result picks up no Caller ID at
> all (yet, the BT Freestyle does still display the Caller ID most of the time
> when this happens). . . .

A guess is that Solos click on BT lines because of either the line reversal that
heads the
calling line identification presentation (CLIP) signal or some other big change
in line
voltage. Often my Solo clicks when I take my handset off hook; sometimes it
clicks
without any call coming, perhaps when a neighbour takes their phone off hook.
The CLIP
data stream after the line reversal should not cause the clicks.

IIRC BT uses line reversals as part of the signalling to switch lines from idle
to loop states
at the start of a call. This is part of the prompt to our kit (e.g., Solos) to
receive CLIP data.
The CLIP data arrive before the rings. Our kit must have programmed delays to
pass the
CLIP data to our software between the first and second rings, when most comms
software
expects. Call Waiting signals seem very similar, but there is no line reversal
or switching
out of loop state.

Maybe TalkTalk does without line reversals along its local loop unbundled lines
to signal
an imminent CLIP, instead working rather like Call Waiting: hence lack of
clicks. TalkTalk
may even send the CLIP between the first and second rings, as happens over most
of the
world, even if the CLIP otherwise follows BT protocols. This may make TalkTalk
Caller ID
unreliable with a Solo, while other kit may be more tolerant, perhaps if it can
also receive
Call Waiting signals.

Sources:

Caller ID FAQ
<http://www.ainslie.org.uk/callerid/cli_faq.htm>

Wikipedia
<http://en.wikipedia.org/wiki/Caller_ID>

BT Supplier Information Notes 227 and 242 (PDFs, each 34 pp., available via
search)
<http://www.sinet.bt.com/>

£0.02

--

Laurence Taylor

On Wed, 16 Jul 2008 19:08:37 +0000, Paul Murphy wrote:

> This may be of some help:
> http://www.ainslie.org.uk/callerid/cli_faq.htm#Q_6
> <http://www.ainslie.org.uk/callerid/cli_faq.htm#Q_6>  it's a bit old but
> there's allot of good stuff there.

Have already been there :)

>> It's a strange problem because it works about 50% of the time on
> average with
>> the Solo, and 90% of the time on a BT Freestyle handset. Probably
> everybody
>> here knows the tell-tale "click...click" that the Solo makes directly
> before
>> the phone starts to ring, and before it starts to announce the phone
> number.
>> With my BT line, this was always a fixed "click...click", but with TT
>> sometimes it doesn't click at all and as a result picks up no Caller
> ID at
>> all (yet, the BT Freestyle does still display the Caller ID most of
> the time
>> when this happens).
>
> Sounds like there is indeed some sort of different standard (or improper
> configuration of their system to work to that standard). Maybe the CID
> data isn't being sent through on a strong enough signal - hence
> sometimes it's doesn't pass the threshold to activate the old Solo but
> it's enough to activate a 'lighter weight' CID box? Does unplugging all
> other devices/loads from the line make it more likely that the Solo will
> talk to you again?  :-)

Nope.  Have tried all that.

> If they don't fix it, as Caller ID clearly isn't functioning as it
> should, I think you should have grounds to get out of any contract and
> go to another telco. Have you been able to test the Solo on another
> line, just to make sure it's not the culprit?

Trouble is, I left BT because I'd had enough of their stealth price increases,
and although I viewed switching to TT a risk at first, I have been very
surprised with how good they are generally.  I've no complaints with
broadband or the voice line in general - it's just Caller ID, and I can maybe
live with the Solo not working always as I'm saving a lot of money being with
TalkTalk :-).  I've not been able to test the Solo on another TT line as I
don't know anybody else who is with TT, but I have tried my spare Solo on my
line and that has the same trouble.

> By the way, I'm now using Classic PhoneTools 9 retail with the Terminal
> app add-in, in conjunction with Avanquests special revised tab file (to
> fix the purple bar on the GUI) and my inf that's listed under files
> in this group and it's all working together very well. Multi-page faxes
> even get through to machines where my setup previously had problems
> after the first page. It's definitely worth the £10 or so it cost me
> to upgrade to this latest version! The only problem I'm now experiencing
> is it's very slow to start up now there are more voicemails and faxes
> stored in the history - it was lightning fast by comparison when I first
> installed it.

Glad to hear my Solo isn't the only one still in active use.

--
  Oliver Roberts  -  http://www.futaura.co.uk/  -  ICQ: 34640231

On Fri, 18 Jul 2008 16:31:28 +0000, laurence_taylor2001 wrote:

> --- In 56solo@yahoogroups.com, Oliver Roberts <oliver@...> wrote:
>>
>> . . .  Apparently, TalkTalk's Caller ID system is supposed to be
>> identical to BT's, but there are some minor differences (not just the
>> problem that I'm having).
>>
>> It's a strange problem because it works about 50% of the time on average
>> with the Solo, and 90% of the time on a BT Freestyle handset.  Probably
>> everybody here knows the tell-tale "click...click"  that the Solo makes
>> directly before the phone starts to ring, and before it starts to
>> announce the phone number. With my BT line, this was always a fixed
>> "click...click", but with TT sometimes it doesn't click at all and as a
>> result picks up no Caller ID at all (yet, the BT Freestyle does still
>> display the Caller ID most of the time when this happens). . . .
>
> A guess is that Solos click on BT lines because of either the line
> reversal that heads the calling line identification presentation (CLIP)
> signal or some other big change in line voltage. Often my Solo clicks
> when I take my handset off hook; sometimes it clicks without any call
> coming, perhaps when a neighbour takes their phone off hook. The CLIP data
> stream after the line reversal should not cause the clicks.

Yes, I get the clicks too when taking the handset off hook, most of the time.
Happened when I was with BT and still now I'm with TT.  Regarding clicks
without any call coming, it only seems to happen here if there are storms in
the area or late at night (12am or so) which I had assumed was BT tests.

> IIRC BT uses line reversals as part of the signalling to switch lines
> from idle to loop states at the start of a call. This is part of the
> prompt to our kit (e.g., Solos) to receive CLIP data. The CLIP data
> arrive before the rings. Our kit must have programmed delays to pass the
CLIP
> data to our software between the first and second rings, when most comms
> software expects. Call Waiting signals seem very similar, but there is no
> line reversal or switching out of loop state.
>
> Maybe TalkTalk does without line reversals along its local loop unbundled
> lines to signal an imminent CLIP, instead working rather like Call
> Waiting: hence lack of clicks. TalkTalk may even send the CLIP between
> the first and second rings, as happens over most of the world, even if
> the CLIP otherwise follows BT protocols. This may make TalkTalk Caller ID
unreliable
> with a Solo, while other kit may be more tolerant, perhaps if it can also
> receive Call Waiting signals.

Maybe.  It seems inconsistent.  Sometimes it clicks, sometimes it doesn't.
Likewise, with the BT Freestyle handsets, sometimes there display the Caller
ID immediately, sometimes it doesn't show up until after 2-3 rings, or more
rarely it doesn't show up at all.  It could just be a timing issue or
something.  Then again, TT aren't exactly unknown for having Caller ID issues
if their forums are anything to go by - earlier this year exchanges were
given Caller ID updates.

--
  Oliver Roberts  -  http://www.futaura.co.uk/  -  ICQ: 34640231

Hopefully the clicks are not anything to do with these guys.

http://www.indymedia.org.uk/en/2008/06/400602.html

http://news.bbc.co.uk/1/hi/uk/1310985.stm

On Fri, 18 Jul 2008 21:28:02 +0100, you wrote:

>On Fri, 18 Jul 2008 16:31:28 +0000, laurence_taylor2001 wrote:
>
>> --- In 56solo@yahoogroups.com, Oliver Roberts <oliver@...> wrote:
>>>
>>> . . .  Apparently, TalkTalk's Caller ID system is supposed to be
>>> identical to BT's, but there are some minor differences (not just the
>>> problem that I'm having).
>>>
>>> It's a strange problem because it works about 50% of the time on average
>>> with the Solo, and 90% of the time on a BT Freestyle handset.  Probably
>>> everybody here knows the tell-tale "click...click"  that the Solo makes
>>> directly before the phone starts to ring, and before it starts to
>>> announce the phone number. With my BT line, this was always a fixed
>>> "click...click", but with TT sometimes it doesn't click at all and as a
>>> result picks up no Caller ID at all (yet, the BT Freestyle does still
>>> display the Caller ID most of the time when this happens). . . .
>>
>> A guess is that Solos click on BT lines because of either the line
>> reversal that heads the calling line identification presentation (CLIP)
>> signal or some other big change in line voltage. Often my Solo clicks
>> when I take my handset off hook; sometimes it clicks without any call
>> coming, perhaps when a neighbour takes their phone off hook. The CLIP data
>> stream after the line reversal should not cause the clicks.
>
>Yes, I get the clicks too when taking the handset off hook, most of the time.
>Happened when I was with BT and still now I'm with TT.  Regarding clicks
>without any call coming, it only seems to happen here if there are storms in
>the area or late at night (12am or so) which I had assumed was BT tests.
>
>> IIRC BT uses line reversals as part of the signalling to switch lines
>> from idle to loop states at the start of a call. This is part of the
>> prompt to our kit (e.g., Solos) to receive CLIP data. The CLIP data
>> arrive before the rings. Our kit must have programmed delays to pass the
>CLIP
>> data to our software between the first and second rings, when most comms
>> software expects. Call Waiting signals seem very similar, but there is no
>> line reversal or switching out of loop state.
>>
>> Maybe TalkTalk does without line reversals along its local loop unbundled
>> lines to signal an imminent CLIP, instead working rather like Call
>> Waiting: hence lack of clicks. TalkTalk may even send the CLIP between
>> the first and second rings, as happens over most of the world, even if
>> the CLIP otherwise follows BT protocols. This may make TalkTalk Caller ID
>unreliable
>> with a Solo, while other kit may be more tolerant, perhaps if it can also
>> receive Call Waiting signals.
>
>Maybe.  It seems inconsistent.  Sometimes it clicks, sometimes it doesn't.
>Likewise, with the BT Freestyle handsets, sometimes there display the Caller
>ID immediately, sometimes it doesn't show up until after 2-3 rings, or more
>rarely it doesn't show up at all.  It could just be a timing issue or
>something.  Then again, TT aren't exactly unknown for having Caller ID issues
>if their forums are anything to go by - earlier this year exchanges were
>given Caller ID updates.

On Sat, 19 Jul 2008 16:06:34 +0100, jgxhs@... wrote:

> Hopefully the clicks are not anything to do with these guys.
>
> http://www.indymedia.org.uk/en/2008/06/400602.html
>
> http://news.bbc.co.uk/1/hi/uk/1310985.stm

Hehe... It had crossed my mind, but I guess it must be pretty boring listening
in to conversations on our line :-).

--
  Oliver Roberts  -  http://www.futaura.co.uk/  -  ICQ: 34640231

--- In 56solo@yahoogroups.com, "night_owl_qp <night_owl_qp@...>"
<night_owl_qp@...> wrote:
>
> Does anyone know, or have, the original outgoing greetings message
> for the solo in windows audio format (*.wav, etc) or know where to
> find one as mine was deleted by phonetools! Have tried re-flashing
> without success. Any help appreciated.
>


Hi. The same thing has just happened to me! I did it once before, years ago, in
Phonetools, and I got it back by running the firmware update. I cannot do that
now though as it will not run under Windows 7. Did you ever manage to get hold
of the original greeting message?

On Tue, 23 Feb 2010 20:42:01 +0000, pbar100 wrote:

> --- In 56solo@yahoogroups.com, "night_owl_qp <night_owl_qp@...>"
> <night_owl_qp@...> wrote:
>>
>> Does anyone know, or have, the original outgoing greetings message
>> for the solo in windows audio format (*.wav, etc) or know where to
>> find one as mine was deleted by phonetools! Have tried re-flashing
>> without success. Any help appreciated.
>>
>
> Hi. The same thing has just happened to me! I did it once before, years
> ago, in Phonetools, and I got it back by running the firmware update. I
> cannot do that now though as it will not run under Windows 7. Did you
> ever manage to get hold of the original greeting message?

The PC upgrader is still available via
http://www.infoserve.com/ftp/56soloup.exe - if you unzip that file you'll
find all the built-in voice prompts in the "fr" directory.  These are not in
WAV format, IIRC, but the Solo's custom raw audio format.  Normally the
upgrader will read those files and store them as-is on the Solo - I forget
how the PC upgrader worked, but I know the Amiga upgrader did allowed the
messaged to be rewritten without flashing the firmware.

I'm not familiar with Phonetools at all - can it transfer these files to the
Solo like the upgrade utility can, I wonder?

--
  Oliver Roberts  -  http://www.futaura.co.uk/  -  ICQ: 34640231

Thanks for your reply.
I have already extracted the English greeting from the firmware which I have,
but the format is IMA (I think, I'm not at that pc right now), and I'm unable to
open it in anything or convert it. If I could convert it to WAV then I could
upload it back into the modem using Phonetools and life will be sweet again.
I've spent an age looking around for standard answer phone messages on the net,
as I can convert any audio format to WAV and upload it to the Solo, but all I
can find ever, are joke one's! Looks like my only option might be to find a
Windows 98 machine and run the firmware upgrade, I did this once before years
ago as I am the same issue then. I'd rather not though, there's always a risk of
disaster. Must be some way of using/converting the greeting file that I
extracted from the firmware. Or they must be another way to get it back?

On Wed, 24 Feb 2010 07:14:50 +0000, pbar100 wrote:

> I have already extracted the English greeting from the firmware which I
> have, but the format is IMA (I think, I'm not at that pc right now), and
> I'm unable to open it in anything or convert it. If I could convert it to

Yes, IIRC, it's a custom format used by Konnex - the french company who made
the Solo.  Obviously, Phonetools must be able to convert from WAV to this
format if you can upload the greeting message using that.  I guess it won't
let you upload the IMA file directly?

> WAV then I could upload it back into the modem using Phonetools and life
> will be sweet again. I've spent an age looking around for standard answer
> phone messages on the net, as I can convert any audio format to WAV and
> upload it to the Solo, but all I can find ever, are joke one's! Looks
> like my only option might be to find a Windows 98 machine and run the
> firmware upgrade, I did this once before years ago as I am the same issue
> then. I'd rather not though, there's always a risk of disaster. Must be
> some way of using/converting the greeting file that I extracted from the
> firmware. Or they must be another way to get it back?

Depends how adventureous you feel?  The only existing way, AFAIK, is to use
the upgrade utility which hopefully has the option to skip touching the
firmware and just upload the sound files.  Unless you can find something
that'll convert the file to WAV, the only other way would be to write you own
program to do the job.  It's possible via the Solo's pipe commands (listed in
the files section on the yahoogroups site for this list) - AT|CREATE would
allow you to upload the IMA greeting message, for example, which is how
Phonetools does it. Maybe it could be done manually using a terminal program,
although probably Hyperterminal wouldn't be up to the job,

--
  Oliver Roberts  -  http://www.futaura.co.uk/  -  ICQ: 34640231

--- In 56solo@yahoogroups.com, Oliver Roberts <oliver@...> wrote:
>
> On Wed, 24 Feb 2010 07:14:50 +0000, pbar100 wrote:
>
> > I have already extracted the English greeting from the firmware
which I
> > have, but the format is IMA (I think, I'm not at that pc right now),
and
> > I'm unable to open it in anything or convert it. If I could convert
it to
>
> Yes, IIRC, it's a custom format used by Konnex - the french company
who made
> the Solo. Obviously, Phonetools must be able to convert from WAV to
this
> format if you can upload the greeting message using that. I guess it
won't
> let you upload the IMA file directly?

Kortex did several non-standard things with the Solo and it's French
equivalents you only have to look at the raw output format when Caller
ID is up and running - date and time come out on the same line in
terminal mode. A product I was introduced to many years ago which is the
Swiss Army knife of audio format conversion programs is called A-Wave
(now with an Audio at the end). Anyone wanting to convert audio files
for modem greetings would be worth trying this - a shareware version is
available. Otherwise running the firmware update on a Win 98 machine
with the actual firmware update part de-selected, has always resulted in
the original voices going back onto the Solo for me. If you already have
the latest firmware installed then unless the firmware update part is
deseleted, the updater won't run. The only problem is that the next time
PhoneTools sees it, the software overwrites the English rose with it's
own not so English sounding greetings. So you'd need to modify the
greeting files in the software as well.

Well, I decided to forget about the English Rose message, though I'd love to
have it back. Perhaps one day, someone will have it and I could then transfer it
back via Phonetools, as you can do with any .wav file. I live in hope!


--- In 56solo@yahoogroups.com, "Paul" <dualathlonuser@...> wrote:
>
>
>
> --- In 56solo@yahoogroups.com, Oliver Roberts <oliver@> wrote:
> >
> > On Wed, 24 Feb 2010 07:14:50 +0000, pbar100 wrote:
> >
> > > I have already extracted the English greeting from the firmware
> which I
> > > have, but the format is IMA (I think, I'm not at that pc right now),
> and
> > > I'm unable to open it in anything or convert it. If I could convert
> it to
> >
> > Yes, IIRC, it's a custom format used by Konnex - the french company
> who made
> > the Solo. Obviously, Phonetools must be able to convert from WAV to
> this
> > format if you can upload the greeting message using that. I guess it
> won't
> > let you upload the IMA file directly?
>
> Kortex did several non-standard things with the Solo and it's French
> equivalents you only have to look at the raw output format when Caller
> ID is up and running - date and time come out on the same line in
> terminal mode. A product I was introduced to many years ago which is the
> Swiss Army knife of audio format conversion programs is called A-Wave
> (now with an Audio at the end). Anyone wanting to convert audio files
> for modem greetings would be worth trying this - a shareware version is
> available. Otherwise running the firmware update on a Win 98 machine
> with the actual firmware update part de-selected, has always resulted in
> the original voices going back onto the Solo for me. If you already have
> the latest firmware installed then unless the firmware update part is
> deseleted, the updater won't run. The only problem is that the next time
> PhoneTools sees it, the software overwrites the English rose with it's
> own not so English sounding greetings. So you'd need to modify the
> greeting files in the software as well.
>

Hi. Can anyone remember please, how to check the recorded greeting message on
the Solo. I've forgotten! There are a couple of buttons which you press at the
same time I think, and then the current greeting will play. Thanks.

On Thu, 18 Aug 2011 19:49:22 +0000, pbar100 wrote:

> Hi. Can anyone remember please, how to check the recorded greeting
> message on the Solo. I've forgotten! There are a couple of buttons which
> you press at the same time I think, and then the current greeting will
> play. Thanks.

How about just pressing the ANN button, or have I misunderstood?  IIRC, two
buttons are required to record a custom greeting message.  I still have the
manual somewhere.

Isn't it amazing these still work?!?!  It must be around 13 years since I
bought mine, although it's hard to believe it's that long.  I don't use it as
an answerphone anymore, but I still do use it for Caller Display announcing
and to log incoming call numbers which are in turn downloaded to my computer.

--
  Oliver Roberts  -  http://www.futaura.co.uk/  -  ICQ: 34640231

In article <j2jqc2+n8mo@eGroups.com>,
    pbar100 <paul@...> wrote:
> Hi. Can anyone remember please, how to check the recorded greeting
> message on the Solo. I've forgotten! There are a couple of buttons which
> you press at the same time I think, and then the current greeting will
> play. Thanks.

Right, from the User Guide:
With your Solo On, the ANS button light should be lit (the answer phone is
enabled). Press this button once, the ANS light will go out, and the
function will be disabled.
It then says Press the flashing ANN key, this plays the default greeting
message that callers will hear.
Hope this helps.

--
____________________________________________________

Ray Twort               rwt@...
____________________________________________________

10 PRINT "Waiter, There's a bug in my LOOP": GOTO 10

--- In 56solo@yahoogroups.com, Oliver Roberts <oliver@...> wrote:
>
> On Thu, 18 Aug 2011 19:49:22 +0000, pbar100 wrote:
>
> > Hi. Can anyone remember please, how to check the recorded greeting
> > message on the Solo. I've forgotten! There are a couple of buttons which
> > you press at the same time I think, and then the current greeting will
> > play. Thanks.
>
> How about just pressing the ANN button, or have I misunderstood?  IIRC, two
> buttons are required to record a custom greeting message.  I still have the
> manual somewhere.
>
> Isn't it amazing these still work?!?!  It must be around 13 years since I
> bought mine, although it's hard to believe it's that long.  I don't use it as
> an answerphone anymore, but I still do use it for Caller Display announcing
> and to log incoming call numbers which are in turn downloaded to my computer.
>
> --
>  Oliver Roberts  -  http://www.futaura.co.uk/  -  ICQ: 34640231
>

Thanks for your reply. Yes, that was it, just the ANN button, don't know why, or
how I forgot that, but I did. I know what you mean about the lifespan of the
Solo, I've had mine for a long time, from when it was in production, and it's
still used every day now, it's our only answerphone, and I also use it to
send/receive faxes still. I dread the day when any new upgraded pc won't be it's
friend anymore!

--- In 56solo@yahoogroups.com, R W Twort <rwt@...> wrote:
>
> In article <j2jqc2+n8mo@...>,
>    pbar100 <paul@...> wrote:
> > Hi. Can anyone remember please, how to check the recorded greeting
> > message on the Solo. I've forgotten! There are a couple of buttons which
> > you press at the same time I think, and then the current greeting will
> > play. Thanks.
>
> Right, from the User Guide:
> With your Solo On, the ANS button light should be lit (the answer phone is
> enabled). Press this button once, the ANS light will go out, and the
> function will be disabled.
> It then says Press the flashing ANN key, this plays the default greeting
> message that callers will hear.
> Hope this helps.
>
> --
> ____________________________________________________
>
> Ray Twort               rwt@...
> ____________________________________________________
>
> 10 PRINT "Waiter, There's a bug in my LOOP": GOTO 10
>

Thanks for your response. That's it, just the ANN button. Though it can be done
with the answerphone on or off, I've discovered. Thanks again.

Hi
Might be of use to someone here I'm selling my old 56 Solo on Ebay £0.99 reserve
+ postage. Item number: 320797474278.

Regards

Tim