[WriteLog] Writelog & RITTY

[Don Hill AA5AU]

Chuck and others...

W1ZT is the only one I know of that has successfully used RITTY with WriteLog
in actual contest conditions (there may be others I just don't know of them).

I tried RITTY with WriteLog a few weeks ago.  My problem was that RITTY
would not work with either of the sound cards I had in my computers.  I was
able to successfully install it and have the appropriate small tuning window show
up in WriteLog.  It just didn't decode anything.  So I'm not sure what your
problem could be.  If it works in DOS it should work with WriteLog.

My opinion in all this is that it's really not worth it to have RITTY work with
WriteLog.  Why would you want to use a DOS program with an already capable
Windows program?  RTTYrite works great with any sound card in Windows.

I admit I have never used RITTY successfully.  But I can't possibly see where
it could be significantly better than RTTYrite in contest situations.  I run three
different combinations here, PK232, DXP38 and sound cards (2).  Under contest
conditions, either of them copy better than the other under certain situations.

Now that Wayne has added a split window for Wide Band Decode, you'd be
better off chucking RITTY altogether.  I have nothing against Brian, K6STI.
Many operators are using his software.  If you want to use it, perhaps you'd be
better off sticking with WF1B.

Please don't take this as an insult.  I look for you in every RTTY contest.  I'm normally
Low Power so it's always a great pleasure to get you in the log and I hope to see
you in the next RTTY contest.  Just my opinion.  DOS is out, Windows is in.

73, Don AA5AU


----- Original Message ----- 
From: "Chuck Kresge" <du3nxe@mozcom.com>
To: <writelog@contesting.com>
Sent: Thursday, April 12, 2001 10:03 PM
Subject: [WriteLog] Writelog & RITTY


> 
> For Writelog plus RITTY users-
> 
> I recently upgraded Writelog to version 10.25M and RITTY to version 4.5 so I
> could use them together. But I have not been able to do so.
> 
> In accordance with the Writelog help files I added the following line:
> "RITTY_LOCATION=C:\RITTY" to the WRITELOG.INI file just after [Rttyrite].
> 
> Then I go into Windows and click on the Writelog program shortcut. When the
> program opens I change the modem to "RITTY in a DOS window".
> 
> Then the Bill Gates "BLUE SCREEN" window pops up telling me "An exception 0E
> has occured at 0028, etc., etc.". After clearing this window I am back in
> Writelog and the RITTY tuning window is present but on top is a warning
> window saying-"RITTY This program requires more conventional memory. Unload
> drivers, etc, etc.". But when I reboot back into DOS and use the MEM /C
> command to check memory I find that there is 638,928 (624K). bytes available
> which seems to me should be more than adequate.
> 
> Then when I am back in Windows I click on the MSDOS prompt in the program
> list and the BLUE SCREEN warning pops up again. So something must be eating
> up conventional memory when I go into Windows. Checking AUTOEXEC.BAT AND
> CONFIG.SYS I find that I have everything loaded high. I even temporarily
> removed the CDROM commands by the REM command to try and free up more memory
> but it did not help.
> 
> My computer is an INTEL Celeron 366MHz PC with 32MB RAM and a big 4+GB
> harddrive. It has Windows 98 with the latest upgrades installed.
> 
> Can anyone give me some ideas about what is keeping me from opening the DOS
> RITTY tuning window with Writelog so I can use them together? I want to see
> if Writelog/RITTY is a better choice for RTTY contesting than my present
> WF1B/RITTY.
> 
> Many thanks in advance for your help-Chuck-DU3NXE du3nxe@mozcom.com
> 
> 
> 
> --
> WWW:                      http://www.writelog.com/
> Submissions:              writelog@contesting.com
> Administrative requests:  writelog-REQUEST@contesting.com
> Problems:                 owner-writelog@contesting.com
> 
> 


--
WWW:                      http://www.writelog.com/
Submissions:              writelog@contesting.com
Administrative requests:  writelog-REQUEST@contesting.com
Problems:                 owner-writelog@contesting.com