| Re: geoPublish file "contents" [message #411861] |
Wed, 13 October 2021 14:52  |
Bruce Thomas
Messages: 89
Registered: November 2012
Karma: 0
|
Member |
|
|
I use geoBeap all the time in Wheels to create D64's and to unpack them.
On Wed, Oct 13, 2021 at 11:36 AM xy3951 <xy3951@epix.net> wrote:
> Gateway would be another option to use native partitions. While I don't
> hate wheels, there are times where certain apps work with Gateway and don't
> in Wheels. A good example that comes to mind is GeoBeep. Also I have
> found, in general, Gateway is faster. But I admit, it is not as easy to
> switch from say 1581 partitions to native in Gateway. The best way I think
> in your case is to make boot disk for Gateway and have the HD as drive 9/B
> With 8/a booting from whatever device you prefer (41,81,Ramlink, etc). The
> other way is once in Gateway, swap the HD A or B, then double click the
> native HD driver if you booted with the HD1581 partitions (the driver
> doesn't have to be on your bootdisk but that is the easiest way). It will
> then grab the first Native partition from the HD and allow you to switch
> between partitions from the Gateway menu. The only downside is Gateway
> will often put a GWINFO file on any GEOS disk it uses. Usually though this
> is when you make certain altera
> tions to the disk such as preferences, or moving files around on the disk
> (but not always). BUT it shouldn't if you press the write protect button
> on the HD, which I would do before booting Gateway.
>
>>
>> On Tue, Oct 12, 2021 at 5:31 PM Glenn Holmer wrote:
>>
>>> I recently acquired Dale Sidebottom's CMD Zip drive (a modified CMD-HD
>>> with a Zip Drive inside) from Jim Peters, and I'm trying to make sense
>>> of the contents of about a dozen 100M Zip disks. Much of what's on them
>>> appears to be geoPublish files, but in many cases, multiple projects are
>>> all smooshed together on 16M native partitions (I'm guessing these may
>>> have been backup disks rather than production disks). I've tried to view
>>> some of the geoPublish files, but get the dreaded "disk full, please
>>> move files", even in cases where the native partition has megabytes of
>>> free space. And since there are numerous native partition subdirectories
>>> with slashes in the filename, the only way I could even view this stuff
>>> is in Wheels (which I hate using)... but at least it has support for
>>> native partitions.
> *snip*
> -----------------------------------------------------
> HOMESTEAD
> -----------------------------------------------------
> List Admin: Robert Bernardo
> rbernardo@iglou.com
>
> List Help rbernardo@iglou.com
> Add 'help' in the subject or message body.
> _______________________________________________
> Homestead mailing list -- homestead@robertbernardo.com
> To unsubscribe send an email to homestead-leave@robertbernardo.com
>
-----------------------------------------------------
HOMESTEAD
-----------------------------------------------------
List Admin: Robert Bernardo
rbernardo@iglou.com
List Help rbernardo@iglou.com
Add 'help' in the subject or message body. _______________________________________________
Homestead mailing list -- homestead@robertbernardo.com
To unsubscribe send an email to homestead-leave@robertbernardo.com
|
|
|
|
| Re: geoPublish file 'contents' [message #411894 is a reply to message #411861] |
Fri, 15 October 2021 20:00  |
RobertB
Messages: 4993
Registered: December 2011
Karma: 0
|
Senior Member |
|
|
Here are responses, courtesy of the GEOS-Wheels-Megapatch group of
Facebook --
From: Bo Zimmerman
Hi, Robert Bernardo
Did you make sure you were running geoPublish from a different drive than
the data files? Preferably a real floppy...
P.S. This post was very timely for me. Yesterday I watched a video you
posted from the 2005 LUCKI expo, and spent time looking through your
photos. Thank you SO SO much for keeping that stuff. Those memories mean a
lot to me.
It was that particular expo that inspired Jeri and me to plan out a web
site in tribute to Jim Butterfield for staying up late to party with us
kids after the show. Jeri got busy, and I lost interest over time, but
recently picked it all up again. "IPartiedWithJimButterfield.org" WILL
come to life!
From: David Witmer
I would think the easiest option would be to look at creation dates of the
documents. Copy the similar dates over to a 1581 an launch the geo publish
document and see if anything is missing. Photo scraps most likely would be
my guess.
-----------------------------------------------------
HOMESTEAD
-----------------------------------------------------
List Admin: Robert Bernardo
rbernardo@iglou.com
List Help rbernardo@iglou.com
Add 'help' in the subject or message body. _______________________________________________
Homestead mailing list -- homestead@robertbernardo.com
To unsubscribe send an email to homestead-leave@robertbernardo.com
|
|
|
|
| Re: geoPublish file "contents" [message #411923 is a reply to message #411861] |
Wed, 20 October 2021 02:43 |
xy3951
Messages: 21
Registered: February 2013
Karma: 0
|
Junior Member |
|
|
The problem I encountered is when switching drives when inside geoBeap. Often a drive wouldn't appear. And would freeze the system when trying to switch between the drives on source or destination. It might be a VICE issue instead of Wheels, but it seems like the same issue would happen in Gateway, or the original desktop when it doesn't. Perhaps I am using a older version of geoBeap, I will double check that.
On 10/13/2021 2:52 PM, Bruce Thomas wrote:
> I use geoBeap all the time in Wheels to create D64's and to unpack them.
>
> On Wed, Oct 13, 2021 at 11:36 AM xy3951 <xy3951@epix.net> wrote:
>
>> Gateway would be another option to use native partitions. While I don't
>> hate wheels, there are times where certain apps work with Gateway and don't
>> in Wheels. A good example that comes to mind is GeoBeep. Also I have
>> found, in general, Gateway is faster. But I admit, it is not as easy to
>> switch from say 1581 partitions to native in Gateway. The best way I think
>> in your case is to make boot disk for Gateway and have the HD as drive 9/B
>> With 8/a booting from whatever device you prefer (41,81,Ramlink, etc). The
>> other way is once in Gateway, swap the HD A or B, then double click the
>> native HD driver if you booted with the HD1581 partitions (the driver
>> doesn't have to be on your bootdisk but that is the easiest way). It will
>> then grab the first Native partition from the HD and allow you to switch
>> between partitions from the Gateway menu. The only downside is Gateway
>> will often put a GWINFO file on any GEOS disk it uses. Usually though this
>> is when you make certain altera
>> tions to the disk such as preferences, or moving files around on the disk
>> (but not always). BUT it shouldn't if you press the write protect button
>> on the HD, which I would do before booting Gateway.
-----------------------------------------------------
HOMESTEAD
-----------------------------------------------------
List Admin: Robert Bernardo
rbernardo@iglou.com
List Help rbernardo@iglou.com
Add 'help' in the subject or message body. _______________________________________________
Homestead mailing list -- homestead@robertbernardo.com
To unsubscribe send an email to homestead-leave@robertbernardo.com
|
|
|
|
Members
Search
Help
Register
Login
Home
