how to actually sync my livepc from USB stick with the one on my pc

one addition though:

there are 2 issues I tried addressing her:

a) referring to the changes I made to the livepc
a) 1) changes if I have a livepc that I want to maintain myselfm having allow local changes enabled
a) 2) changes that I make as a user, aka resolution, links, maybe installed software?
b) referring to my shared files

how are this too being synched

1a. When local changes are enabled, the changes goes to the [LivePC Name]\activation folder. Refer to "LivePC instances" on FAQ

2a. user, resolution changes, shortcuts (linkas) and any software that is installed in the LivePC will also be stored in the {LivePC Name]\activation folder as stated above.

2b. Shared Files are stored outside of the LivePC.
To quickly getting the path, in the User Interface, select the "LivePC documents" and/or "My Shared LivePC Documents" at the bootom of the UI.

"LivePC documents" and are stored in "%userprofile%\My Documents\My LivePC Documents"\[LivePC Name]\. Refer to section for Desktop User Files/USB User Files similarly for Desktop/USB Shared LivePC Documents on the FAQ

Kevin

thx for the detailed answer, I have reread the faq part you indicated but:

- is manually synching my livepc on the stick with the one on my pc the only method to have two identical livepcs? Do you think such a feature to have them automatically synched over to the pc could be incorporated or would even be useful to the general public?
- I know that the other method would be to modify it until I am happy with how it looks like, then publish it as my own livepc and untick "allow local changes" thus both livepcs (on stick and pc) would always be in synch via the internet, right?

Also reagarding the manual synching there is one problem I see (correct me if I am wrong):

on my pc I have vista, ubuntu and a debian live pc that I am currently configuring for later publishing. on my stick I only have vista and debian so to synch these I would have to have the same cache size allocated to both and I could never copy from usb to pc because that would overwrite my local debian livepc - right?

another possible suggestion: couldn't the cache be dynamically allocated? is there really a need to preallocate that space and have this complicated method of cache resizing?

Synchronizing LivePCs to/from USB and Host would be an interesting feature. I'm not sure how many users would want this feature. Can you provide some background as to what this feature would help resolve?

- You're correct that published LivePC will ensure that both LivePC instances are always updated (Excludes user files or user state disks).

- Copying LivePCs from USB to Host when the LivePC exists?
Sample:
1. Host has a locally create debian.
2. Publish it to the LivePC Library.
3. Download debian using USB Engine(Debian is actually in the cache on the USB and of course you could download the same debian instance to the Host version as well. The downloaded version will go into the host cache. Just make sure you keep track of the one you're working on.

Copying the cache to/from host/USB would not be recommended as you can "lose" some portitions of a downloaded LivePC and will need to wait for the LivePC to be downloaded again. There are also other dependencies of the LivePC to the cache data which may makes it more complicated.

- dynamically allocate cache??? We need to deal with NTFS and FAT32 so FAT32 will not allocate the space until it is needed.

Kevin

quote:
Synchronizing LivePCs to/from USB and Host would be an interesting feature. I'm not sure how many users would want this feature. Can you provide some background as to what this feature would help resolve?
quote-end

I have subscribed to the vista livepc and would like to modify it to my needs but I have not thought about publishing it again online as I would make changes as I need them - not really suited for anybody else. So I would like to work with this pc constantly - be it at home or somewhere else. And if I am at home there is no need to work from the slower USB stick and unnecessary shorten its lifecycle.
Or imagine I am working on a new livepc for publishing - I would love to get home, plug my usb stick in, wait 1-2 minute, unplug and continue working on it on my pc.

quote:
- Copying LivePCs from USB to Host when the LivePC exists?
Sample:
1. Host has a locally create debian.
2. Publish it to the LivePC Library.
3. Download debian using USB Engine(Debian is actually in the cache on the USB and of course you could download the same debian instance to the Host version as well. The downloaded version will go into the host cache. Just make sure you keep track of the one you're working on.

Copying the cache to/from host/USB would not be recommended as you can "lose" some portitions of a downloaded LivePC and will need to wait for the LivePC to be downloaded again. There are also other dependencies of the LivePC to the cache data which may makes it more complicated.

- dynamically allocate cache??? We need to deal with NTFS and FAT32 so FAT32 will not allocate the space until it is needed.
quote-end

All of this could pe partially eliminated if we could have a separate cache file for each livepc right? I mean if dynamically allocating cache as needed does not work, what about separating it into separate files like vista.cache debian_ubuntu.cache whatever, this would let me easily "synch" my livepcs by copying exactly those livepcs that have changed :-)

Great suggestions and use cases...keep it coming. I'll submit the enhancement requests and we'll see where it fits into the roadmap. I can't promise anything.

Kevin