jonnosan wrote:
commodoregeek wrote:
we've got a website (
http://www.commodorelive.com) that will have some extra cool things to help enhance your user experience with Pilot
This looks like a really interesting concept. There seems to be quite a lot of overlap in ideas with
http://www.commodoreserver.com/ & the Comet 64 (although interfacing via IEC instead of userport like the Comet 64 did has a lot of advantages i.e. speed, compatability with a wider range of CBM machines, and easy to make remote disk access completely transparent; I assume with the appropriate "device 2" driver installed you could even make this device work with BBS software)
The obvious next step (to me at least) is to use a central web site as a hub to enable multiplayer gaming on the c64 (I assume your site name is a referrence to that potential). Which I think is a great idea, but I think developers will be more inclined to build such games, and customers inclined to purchase a device, if they don't have to worry they are backing the wrong horse in what seems to be a 2 horse race. In a small market, fragementation hurts everyone

Is there any possibility if you and the commoderserver team working together? Even if there ends up being 2 separate devices with unique web servers behind, it would be great if you could come up with unified interface, such that a developer could build an online game that worked with either system (and potentially even with other as-yet-unthought-of)
Thank you. We feel Pilot is indeed an interesting concept and a really fun project to work on.
About product overlap...
Comet64 and our device (Pilot) are quite different devices. Comet64 appears to be a simple serial-to-ethernet device interfaced via the user port, and requires driver software (v-1541) to extend the kernel to support most of its functionality.
Pilot is an intelligent IEC based device which provides two peripherals in one - an internet modem and a basic drive emulator. A primary goal was to provide an easy to use, plug-and-play device which is fully functional even without the companion website we've developed (commodorelive.com). In addition, the host machine will be completely "clean", as no drivers, kernel hacks, or any other software is required to use Pilot.
When loading disks from the internet, the Pilot caches one or more disks in local non-volatile (flash) memory, then serves the disk data to the computer via the disk drive device. The final Pilot hardware will have approx. 3MB available for cache memory, enough to hold quite a few disks for offline use. Disk image compression is planned for future firmware updates, allowing you to store many more disk locally (however any compressed disks will be read-only).
In contrast, all disk activity for the Comet64 is streamed live over the internet. Without an internet connection, the device appears to be useless.
This is a very fundamental difference between the two devices and websites that makes unification almost impossible. As I touched on earlier, the Pilot can even be commanded to download disk images from individual websites with a simple LOAD command in BASIC.
As the Pilot is an intelligent device, we have decided to provide a high level networking interface initially supporting TCP and UDP protocols. The current goal is to extend this over time to support additional established protocols such as FTP and SMTP (thanks to gsteemso for the suggestion) with the Pilot doing the "heavy lifting". This should one day provide rich internet capabilities to even an unexpanded VIC-20

Once again, since it seems impossible for Comet64 to provide this same level of functionality, we don't see how the programming interfaces between the two can be standardized.