HDTenEightyP/NetNews huggingface dataset:
From: drudetb@infonode.ingr.com (Ted B. Drude)
Subject: For Sale: Commodore 64 Portable, Vic-20, Printer
Organization: Intergraph Corporation, Huntsville, AL.
Date: Mon, 5 Oct 1992 04:23:38 GMT

For Sale:

- Commodore C-64 Portable (SX-64)  Excellent condition  - $195

- Commodore 1525 printer   Works fine, ribbon needs re-inking  - $20

- Commodore VIC-20  w/ datasette - $15

Asking prices plus shipping. Trades possible,  especially PC hardware.

Reply to: Ted Drude (drudetb@infonode.ingr.com)
Newsgroups: comp.sys.cbm
From: zembrod@informatik.uni-freiburg.de (Philip Zembrod)
Subject: Re: Broken '81
Keywords: blake
Organization: Institut fuer Informatik der Universitaet Freiburg, Deutschland
Distribution: comp
Date: Tue, 6 Oct 92 15:34:09 GMT

blake@blkbox (Blake Scruggs) writes:


>oking for some Help with a Broken '81
> 
>Here's the specifics:
>1-It powers up, the Red light comes on. About 1 out of 10 times the
>  Self-Test/Activity light comes on.
>2-No intial Click Click when powered up, does'nt matter if a disk is
>  Inserted still no Click Click
>3-The insides: Compared to my 3 other '81's their are some differences.
>  The WD 1772 and 8520 are socketed.  As is the Kernal/Dos IC. which is
>  Normal.
>4-I've tried both my 128D and 64, but I can't access this '81's device #
>5-I have an xtra 1772 and have swapped it. No difference.
>6-My other '81's have J.Dos and so I've swapped  their Kernal/Dos IC's
>  With no difference .
> 
>My guess is it's the 6502 because of this '81's inability to be accessed
>By the serial buss. I'm not sure tho and it's not socketed. Another words
>I'd hate to de-solder it/replace it and not fix it.
>I'm not sure what IC actually controls the I/O / Device # ...
>Does anyone out here know ???

Try changing the 8520. That's the one doing the bus I/O (some kind of
mixture between 6520, 6522 and 6526, I suppose).

Philip


--
: whoisit?  ( -- )
 ." Philip Zembrod "  ( zembrod@informatik.uni-freiburg.de ) ;
Newsgroups: comp.sys.cbm
From: blake@blkbox (Blake Scruggs)
Subject: Help with 1581
Organization: The Black Box BBS (713) 480-2686 V32/V42bis/HST
Distribution: comp
Date: Mon, 05 Oct 1992 18:45:30 GMT
Summary: Need help ID'g an IC
Keywords: Help


oking for some Help with a Broken '81
 
Here's the specifics:
1-It powers up, the Red light comes on. About 1 out of 10 times the
  Self-Test/Activity light comes on.
2-No intial Click Click when powered up, does'nt matter if a disk is
  Inserted still no Click Click
3-The insides: Compared to my 3 other '81's their are some differences.
  The WD 1772 and 8520 are socketed.  As is the Kernal/Dos IC. which is
  Normal.
4-I've tried both my 128D and 64, but I can't access this '81's device #
5-I have an xtra 1772 and have swapped it. No difference.
6-My other '81's have J.Dos and so I've swapped  their Kernal/Dos IC's
  With no difference .
Does anyone have any thoughts on what IC may need to be replaced ??
Thanks for any help, blake@blkbox.com
From: rknop@cco.caltech.edu (Robert Andrew Knop)
Newsgroups: comp.sys.cbm
Subject: Re: GEOS (64) applications & compatibility with versions of GEOS
Date: 29 Sep 1992 15:15:00 GMT
Organization: California Institute of Technology, Pasadena
NNTP-Posting-Host: punisher.caltech.edu

ckunz@pdnfido.fidonet.org (Charles Kunz) writes:

>Currently I own GEOS64 v1.2, which came with geoWrite 1.1 and geoPaint 1.1,
>both of which I am content with. ...  ...I would like to upgrade to GEOS 2.0
>-however- I have many geoWrite documents that I would like to keep.  These doc
>files were created with geoWrite 1.1.  I also have many photo scraps in photo
>albums that I would like to keep, also.  Basically my question is this: Will
>geoWrite 1.1 work with GEOS versions higher than 1.2 or will there be
>problems?  Will my photo scraps work with versions higher than 1.2?  What
>about my photo albums?

Once you try out geoWrite 2.1, you will no longer be content with geoWrite 1.1
:) .  The deskTop has more major upgrades, including the essential enhancement
of multiple file operations.  GEOS 2.0 is well worth the upgrade.

As to file incompatability, you have no need to worry.  I think that geoWrite
1.1 probably would work with GEOS 2.0, but there is really no reason to do
that.  geoWrite 2.1, which comes with GEOS2.0, can read geoWrite 1.1 files.
The first time you open the file with geoWrite 2.1, you will get a dialog box
telling you that it is converting the file to geoWrite 2.1 format.
Thereafter, the file will be directly readable by geoWrite 2.1.  geoWrite 2.1
is MUCH nicer than geoWrite 1.1, and once you try it, you will never want (or
need) to go back.

geoPaint still uses the same file format, and, I believe, photo scraps still
have the same exact format as they did under GEOS 1.x.  The photo manager,
like geoWrite, has an enhanced file format, although I know less about it.  At
any rate, you will be able to continue to use your photo albums with the new
photo manager.

In summary, when upgrading from GEOS 1.x to 2.0, you have no need at all to
worry about compatability with "standard" GEOS applications and files.

-Rob
rknop@cco.caltech.edu
From: aschlie@uoft02.utoledo.edu (A.Schliesser)
Newsgroups: comp.sys.cbm
Subject: Help wanted
Date: 29 Sep 92 01:04:28 EST
Organization: University of Toledo, Computer Services

Greetigs: 
 
I am in need of 2 thing.  Firstly, my drive ate my LADS disk and of course
I did not make a backup.  Lads is a assembler compilier for the c128.  If
anyone has the source code and binary for LADS for the C128, could you uuencode
it and send it to me?  I will for ever be in your debt.
 
Secondly, Is there any way to make the 1571 in a C128d a drive number other 
the software method?? 
 
Which leads me to another question.  I need the 2 drive mechanisms for 1571.  I
will take any leads for new or used. Please reply directly or call me at:
 
1-513-484-3053    ask for Tony
 
 
Thanks,
 
Tony
 
 
-- 

+-------------------------------------------------------------------------+
|Tony Schliesser         			ASCHLIE@UOFT02.UTOLEDO.EDU|
|The University of Toledo			ASCHLIE@UOFT02.BITNET     |
|                   				FAC2966@UOFT01.UTOLEDO.EDU|
|						FAC2966@UOFT01.BITNET     |
|                                                                         |
|   									  |
+-------------------------------------------------------------------------+
From: bbs-artmoore@jwt.UUCP (arthur moore)
Newsgroups: comp.sys.cbm
Subject: Re: 64 using 128 goodies
Date: 1 Oct 92 04:08:46 GMT
Reply-To: bbs-artmoore@jwt.UUCP
Organization: The Matrix

nemanuel@encore.com (Nathan Emanuel) writes:

>  How about the 128 keypad? How can this be enabled in 64 mode? And what is a
>  good location to check to see if this is a 128 running in 64 mode?

Although you'll read this in next month's Gazette with my attached, the 
simplest way to check from BASIC is to test the value of DS$ at the start 
of your program.  If it is null, you are in 64 mode.
This approach is nearly flawless...if your drive is hung up for some 
reason, then it will stall in 128 mode.  If there is no drive on the 
system, it will crash in 128 mode. (NO DRIVE!?!?).
 

( ( Art Moore  | Usenet bbs-artmoore@jwt.uucp
 ) )           |  -or-  bbs-artmoore@jwt.oau.org
( (            | Fidonet CBM  -  Arthur Moore
 ) )__Ask me about the C64 qwk offline reader!__
Newsgroups: comp.sys.cbm
From: Frank.Prindle@bbs.oit.unc.edu (Frank Prindle)
Subject: C64 serial bus loading problem (3 drives and a printer)
Organization: Extended Bulletin Board Service
Distribution: na
Date: Tue, 29 Sep 1992 16:07:38 GMT

Hi,
I'm looking for advice on a serial bus problem.  I have a C64, two 1541 clones,
a 1581, and a PPI printer interface (in that order) on my serial bus.  The two
cables which interconnect the three drives are only about 9 inches long because
when I used the stock cables, the 1581 drive would not read reliably; shortening
the cables fixed that.  Now I notice that the printer turns up "Device not
present" from time to time during printing unless I turn off the 1581, in which
case it prints ok.  I've been tempted to shorten the other two cables (64-drive,
and 1581-PPI) to attempt to solve this problem, but would rather not because
I can't believe the C64 serial bus is that sensitive to cable length, and I'm
not sure why turning off the 1581 fixes the problem if it's just cable length.
Has anyone else had this problem and found a solution?
Sincerely,
Frank Prindle
Frank.Prindle@bbs.oit.unc.edu
--
   The opinions expressed are not necessarily those of the University of
     North Carolina at Chapel Hill, the Campus Office for Information
        Technology, or the Experimental Bulletin Board Service.
           internet:  bbs.oit.unc.edu or 152.2.22.80
From: ppugliese@pimacc.pima.edu
Newsgroups: comp.sys.cbm
Subject: Re: cpm cartridge wanted for c64
Date: 3 Oct 92 10:19:04 GMT
 <1992Oct2.021737.3344@infonode.ingr.com> <1992Oct2.210711.10754@cs.umb.edu>
Distribution: comp

In article <1992Oct2.210711.10754@cs.umb.edu>, edwardp@ra.cs.umb.edu (Edward P. Piecewicz) writes:
> In article <1992Oct2.021737.3344@infonode.ingr.com> drudetb@infonode.ingr.com (Ted B. Drude) writes:
>>In article <5842@ucsbcsl.ucsb.edu> 6500hage@ucsbuxa.ucsb.edu (William F. Hagen) writes:
>>>
>>>I understand the [C-64] cpm was the biggest disaster for the CBM 
>>>this side of the +4.
>>
>>Actually,  it was on THAT side of the Plus 4.  ;-)
>> But you're right,  it was a messy situation.  Commodore had promised 
>>CP/M compatibility in its earliest C-64 ads.  When the thing was finally
>>finished,  it was virtually useless for anything other than to say
>>SOMEKIND of CP/M was available for the 64.  
> 
> 
> I believe the big sticking point with CP/M on the 64 was due to the slow
> disk access.
> 
>  - Ed
> 

There was also the fact that the 1541 couldn't read standard CP/M disks.
Most people I knew that tried it had to d/l stuff from a BBS or some-
thing similar.

PHIL
Newsgroups: comp.sys.cbm
From: dudley@cebaf4.cebaf.gov (John Dudley)
Subject:  C65??
Keywords: c65
Reply-To: dudley@cebaf4.cebaf.gov (John Dudley)
Organization: CEBAF
Date: Fri, 2 Oct 1992 19:40:00 GMT

I remember a very FEW rumors back in the late 80's (88?) about a new
version of the 8 bit line... (C64, C65, C64gs, etc.)... now I here Fred
Bowen from Commodore mentioning little tidbits about the machine.  Since
you have admitted to its existance, could you tell us all what we MIGHT
have been looking forward to?  What was the new machine going to be
like?  What processor/os/languages/speed/case/color?
 
Thanks!
From: fred@cbmvax.commodore.com (Fred Bowen)
Newsgroups: comp.sys.cbm
Subject: Re: Help identify computer
Date: 29 Sep 92 16:30:25 GMT
Reply-To: fred@cbmvax.commodore.com (Fred Bowen)
Organization: Commodore, West Chester, PA

In article <199ti7INNd4g@usenet.INS.CWRU.Edu> bv593@cleveland.Freenet.Edu (Stephen S. Clark) writes:
>
>I have just got hold of a CBM computer but it had no manuals.
>I need help in identifying what it is .
>
>Its a Commodore p500 (no not an Amiga 500)
>
>Its a similiar size to an Amiga 500 but a bit chunkier.
>The back is very similiar to a C64(i.e serial port ,cassette port etc).
>
>Is this a version of a C64?
>Any help appreciated.

The P500 was also called the C128-40, PET-II, or P-series.  It was a
B-series computer (6509, 6551, IEEE, BASIC 4.0) with a VIC chip (replacing
the 6845) and SID chip.  It did not have a 1541-type serial interface, tho.

I did some work on adding graphic commands (and new garbage collect) to
its BASIC (VSP), but that never got out the door (the graphic commands
did make it into the Plus-4, so it wasn't a total waste of time).  After
the Plus-4 'fiasco', the project was revived, and that machine became
the C128 most of you know and, I presume, love.
-- 
Fred Bowen			uucp:	{uunet|rutgers|pyramid}!cbmvax!fred
				domain:	fred@cbmvax.commodore.com
				tele:	215 431-9100

Commodore Electronics, Ltd.,  1200 Wilson Drive,  West Chester,  PA,  19380
From: ab245@cleveland.Freenet.Edu (Sam Latonia)
Newsgroups: comp.sys.cbm
Subject: For Sale
Date: 30 Sep 92 06:04:56 GMT
Organization: Case Western Reserve University, Cleveland, Ohio (USA)
NNTP-Posting-Host: thor.ins.cwru.edu


                 BRAND NEW & USED EQUIPMENT PRICE LIST

(2) COMMODORE C128 COMPUTERS - USED BUT LIKE NEW CONDITION - POWER SUPPLY

    $75 EACH - WITH OWNERS MANUAL - TUTORIAL & CPM DISK

(1) COMMODORE C64C COMPUTER BRAND NEW IN THE BOX - WITH POWER SUPPLY

    $100 WITH OWNERS MANUAL AND SEALED GEO'S PACKAGE FROM COMMODORE

(2) COMMODORE 1581 DISK DRIVES - BRAND NEW IN THE BOX WITH ALL CABLES

    $125 EACH - WITH OWNERS MANUAL AND UTILITY DISK

(3) COMMODORE 1571 DSDD DISK DRIVE - BRAND NEW IN THE BOX

    $125 EACH - WITH SERIAL CABLE & UTILITY DISK

(1) COMMODORE/AMIGA 1084SD STEREO MONITOR - BRAND NEW IN THE BOX

    $250 WITH ALL CABLES & BOOKS - MADE BY TOSHIBA NOT MAGNAVOX!

(1) RS232 INTERFACE FOR COMMODORE TO ANY HAYES MODEM OR SERIAL PRINTER

    $10 WITH A PURCHASE OF ANY OF THE MODEMS LISTED HEREIN

(1) SWIFT LINK CARTRIDGE - WITH THE EXTRA $6 TECH MANUAL FOR $35

(2) C64 POWER SUPPLIES - USED BUT LIKE NEW CONDITION $20 EACH

(1) COMMODORE C64 - USED BUT IN LIKE NEW CONDITION - WITH POWER SUPPLY

    $75 WITH OWNERS MANUAL & HINGED KEYBOARD COVER & TENIX C64C WHITE CASE

(1) AVATEX 1200HC EXTERNAL RS232 MODEMS - USED BUT IN LIKE NEW CONDITION

    $35 EACH WITH BOOKS BOX & CABLE

(2) AVATEX 2400HC EXTERNAL RS232 MODEMS - USED BUT IN LIKE NEW CONDITION

    $75 EACH WITH BOOKS BOX & CABLES

(2) PPI 2400SA EXTERNAL RS232 MODEMS NEW - NEVER USED

    $75 EACH - BOOKS - BOX & CABLES - FULL 1 YEAR WARRANTY

(2) OKIDATA OKITEL 9600 EXTERNAL RS232 MODEM - V.32 V.42 V.42BIS

    $250 EACH - WITH 5 FULL YEARS FACTORY WARRANTY - THROUGHPUT TO 38.4 BPS

ALL PRICES ARE ROCK SOLID- PLUSS SHIPPING COST IF NEEDED:
From: j_thiem@pavo.concordia.ca (THIEMANN, JOACHIM)
Newsgroups: comp.sys.cbm
Subject: SuperPET circuit description
Date: 26 Sep 92 17:43:00 GMT
Organization: Concordia University
News-Software: VAX/VMS VNEWS 1.41

Hello, everybody...

I have a CBM SuperPET, and for the purpose of repair/modification I would like 
to get the circuit description, either for the whole SuperPET, or just the 
CBM 8032 part of it...
Can anyone tell me where I can obtain those?

Thanks,
	Joachim Thiemann  Ugrad Concordia, Canada

PS. If a message like this appeared before, but screwd up... soory, but I
    had trouble with the editor...
From: gobeski8618@iscsvax.uni.edu (Steve 'Gobes' Gobeski)
Newsgroups: comp.sys.cbm
Subject: Re: uudecoding long files
Date: 30 Sep 92 12:30:14 -0500
Organization: University of Northern Iowa

In article <717539140.1@mailbox.bison.mb>, George.Frizzell@mailbox.bison.mb.ca (George Frizzell) writes:
>  
> Quoting Brent Busby:
> ====================>
> 
> Does anybody have any tips on how to go about capturing very long uuencoded  
> files on a Commodore-128?  Hardly any terminal program I know of will let you
                             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> capture more than 60000 characters, and many ftped files are published in
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> UseNet and mailed from ftpmail sites in chunks larger than that.  At an ftp  
> =====================
>   

Any terminal program with a buffer->disk dump (such as NovaTerm) will also
solve this problem, at least until you run out of disk space.

-- Steve 'Gobes' Gobeski // GOBESKI8618@iscsvax.uni.edu

Newsgroups: comp.sys.cbm
From: Edgar.Estrada@bbs.oit.unc.edu (Edgar Estrada)
Subject: Re: cpm cartridge wanted for c64
Keywords: wanted, cpm
Organization: Extended Bulletin Board Service
Distribution: comp
Date: Mon, 5 Oct 1992 04:50:22 GMT

In article <1992Oct2.210711.10754@cs.umb.edu> edwardp@ra.cs.umb.edu (Edward P. Piecewicz) writes:
>In article <1992Oct2.021737.3344@infonode.ingr.com> drudetb@infonode.ingr.com (Ted B. Drude) writes:
>>In article <5842@ucsbcsl.ucsb.edu> 6500hage@ucsbuxa.ucsb.edu (William F. Hagen) writes:
>>>
>>>I understand the [C-64] cpm was the biggest disaster for the CBM 
>>>this side of the +4.
>>
>>Actually,  it was on THAT side of the Plus 4.  ;-)
>> But you're right,  it was a messy situation.  Commodore had promised 
>>CP/M compatibility in its earliest C-64 ads.  When the thing was finally
>>finished,  it was virtually useless for anything other than to say
>>SOMEKIND of CP/M was available for the 64.  
>
>
>I believe the big sticking point with CP/M on the 64 was due to the slow
>disk access.
>
> - Ed
>
>
>
>-- 
>Internet:  edwardp@cs.umb.edu                                  - guest user -
>Member and Activist:  The Boston Computer Society

That was a problem but... 

The biggest problem was that the 1541 could not read the CP/M disks which
made it almost impossible to take advantage of all the CP/M software
available.

Edgar

--
   The opinions expressed are not necessarily those of the University of
     North Carolina at Chapel Hill, the Campus Office for Information
        Technology, or the Experimental Bulletin Board Service.
           internet:  bbs.oit.unc.edu or 152.2.22.80
Newsgroups: comp.sys.cbm
From: ad945@yfn.ysu.edu (Brent Busby)
Subject: Re: cpm cartridge wanted for c64
Reply-To: ad945@yfn.ysu.edu (Brent Busby)
Organization: St. Elizabeth Hospital, Youngstown, OH
Date: Wed, 30 Sep 1992 11:44:44 GMT


In a previous article, 6500hage@ucsbuxa.ucsb.edu (William F. Hagen) says:

>Wanted, CPM cartridge for c64, I will pay any reasonable amount.
>email to 6500hage@ucsbuxa.ucsb.edu
>thanks,
>William F. Hagen

I'll give you mine which includes the manual, original box, and CP/M v2.2 disk
for $15.  Where are you?  I'm in the United States; Pekin, Illinois.
Newsgroups: comp.sys.cbm
From: fuzzy@netcom.com (Fuzzy Fox)
Subject: Re: C-64 gives Out of Memory errors on power up - ideas?
Organization: Foxes 'R' Us - Seven locations to serve you
Date: Mon, 5 Oct 1992 05:33:51 GMT

fred@cbmvax.commodore.com (Fred Bowen) writes:

>When you turn on a C64, you know how it takes 2-3 seconds for the screen
>to appear?  All of that time is due to the RAMTAS routine checking memory.

It's a good thing, too -- Otherwise the 1541 wouldn't have time to
initialize properly, and someone too quick on the keys might crash it.
This is a fun problem with utility cartridges such as Super Snapshot
which bypass RAMTAS to get the machine started faster.  If you hit the
directory function key too quickly, you kill the machine because the
1541 hasn't finished resetting yet.  :)

-- 
#ifdef TRUE         | Fuzzy Fox                  fuzzy@netcom.com
#define  TRUE   0   | a.k.a. David DeSimone      an207@cleveland.freenet.edu
#define  FALSE  1   |   "Verily, thou art indeed a fool."   -- Chuckles the
#endif              |         Jester, moments before his untimely death.
From: gobeski8618@iscsvax.uni.edu (Steve 'Gobes' Gobeski)
Newsgroups: comp.sys.cbm
Subject: Re: 64 Gif Viewer?
Date: 30 Sep 92 19:17:27 -0500
Organization: University of Northern Iowa

> GEOGIF.SDA is a nice GIF converter for GEOS.
> It converts GIF files to GEOPaint files.  VGIF2.1.sda will view
> many GIF files on a C64.  Both programs are available
> on Qlink, or Light Of Day (see my signature).
> -- 
> Basic Bits Commodore Group, No. Ridgeville, Ohio
> Quantumlink - RidgeRunr
> Light Of Day Commodore Sysop (216) 327-1603, 9600 baud

Funny, GEOGIF, at least, doesn't seem to be on TLOD (I just checked. Tho I don't
have privilege to d/l it even if it was, it didn't even appear in the file
list!).  Mayhap I missed something?

-- Steve 'Gobes' Gobeski // GOBESKI8618@iscsvax.uni.edu

Newsgroups: comp.sys.cbm
From: nrossi@jarthur.claremont.edu (Nick Rossi)
Subject: Re: relative file format
Organization: Harvey Mudd College, Claremont, CA 91711
Date: Tue, 29 Sep 1992 19:32:51 GMT

In article <35464@cbmvax.commodore.com> fred@cbmvax.commodore.com (Fred Bowen) writes:
>In article <217NRB2w164w@jwt.UUCP> bbs-artmoore@jwt.UUCP writes:
>>What is the proper DOS command for setting the pointer in a relative 
>>file?
>> 
>>print#15,"p"chr$(channelnumber)chr$(reclowbyte)chr$(rechibyte)chr$(pos)
>> 
>>or do you add 96 to the channel number?  In the Gazette I've seen both.. 
>>they seem to work well with the 1541, but which is "proper" ?
>
>It's explained in the manual- the only reason to add 96 to the channel
>number is to be compatible with the DOS in the older PET/CBM IEEE drives.
>
>BTW, on the same page of the manual is the following warning:
>"To avoid the remote possibility of corrupting relative file data, it is
>necessary to give record pointer commands twice- once before a record is
>read or written, and again immediately afterwards".  It's good advice.


I once wrote a BBS program which used relative files heavily - both for
storing messages and for keeping track of file transfers.  I never released
the program because I never figured out why messages got corrupted every now
and then.  I only sent record pointer commands before each read or write,
never after.

What exactly can happen if the advice is not followed?


***************************************************************************
* Nick Rossi, '93                   Harvey Mudd (not HARVARD MED) College *
* nrossi@jarthur.claremont.edu      "Believing is seeing..."              *
* "Yes, there actually is a town in Washington called `Snohomish'"        *
***************************************************************************
From: ckunz@pdnfido.fidonet.org (Charles Kunz)
Newsgroups: comp.sys.cbm
Subject: GEOS (64) applications & compatibility with versions of GEOS
Date: 29 Sep 92 03:12:22 GMT
Organization: The Source for Source Pub Access Unix

Currently I own GEOS64 v1.2, which came with geoWrite 1.1 and geoPaint 1.1, both
of which I am content with.  However, I feel I am falling behind when it comes
to the deskTop and kernal, and I am reluctant to get any new applications for
fear that they are incompatible with 1.2 (ie., most of these applications or
desk accessories say "for 1.3 and higher").  I would like to upgrade to GEOS 2.0
-however- I have many geoWrite documents that I would like to keep.  These 
doc files were created with geoWrite 1.1.  I also have many photo scraps in
photo albums that I would like to keep, also.  Basically my question is this:
Will geoWrite 1.1 work with GEOS versions higher than 1.2 or will there be
problems?  Will my photo scraps work with versions higher than 1.2?  What
about my photo albums?

Many thanx in advance,
Chuck
-- 
E-mail: ckunz@pdnfido.fidonet.org, aq084@cleveland.freenet.edu
My girlfriend thinks I'm weird.  She's right.