MobileRead Forums - View Single Post

Khan-Dam · 09-02-2014, 01:36 PM

My Experience about XP and Calibre 2.1.0

I Use XP for 10 Years on a XP Server, with a lot of process which run 24h a day 7 day a week 52 week by year without any trouble. Can't have to migrate to vista 7 or 8 ( my second server work fine with NT 5 ).

I use calibre to integrate ebook in database, change metadata and eventualy convert format and use calibre_server to obtain internaly the book i want.

My network is private network not on the internet just intranet. I use calibre for long time and very happy for all thing i can made with it.

i load and use calibre 2.0 without any bug or trouble.

So as i can't try or use the calibre v 2.1, i decide to follow the way of modify sources, there is my experence about that :

- Try to obtain git sources -> more than 12 hours to get source ( add 2 try before, the first one, i break it after 5 hours think the process was in infinite loop, the second try was break by an internet shutdown ).
- because process very long i Try to obtain archive -> it's ok a obtain it rapidly but untar it was long process about 3 or 4 hours.

- According this thread i change source, fix ifxp and try to start manualy calibre, every thing ok it's work perfectly if i use calibre_debug -g after defining %CALIBRE_DEVELOP_FROM%.

so the question is why you make solution for using version 2.1 with source way and don't allow normal way eventualy with some warning or with an environement variable to unlock xp test ?

i understand you don't want to support xp version, but don't understand the difference between the to methods.

What you do if i find a bug with my xp version 2.1 runing with source. And what you do if i find a bug in version 1.48 ?

The Migration of XP to other version is not my question i dont want to change OS ( my hardware certainly don't support that ). So if release of calibre is the same as before one version a week the time to obtain and make calibre running increase considerably the time spend to change version.

I think it's very domagable for calibre to leave all calibre user on xp alone

i don't think user chage os just for 1 programme that don't run !

You tell to stay on version 1.48 is very strange if this version so stable and unbuggy why release to version 2.x.

So there are my reflections, not agressive message and i respect the decision of the kovidgoyal. But in this way i use an older version without have the chance to use new things.

The last thing is can i use version 2.x working with another machine running on Win7 to chnge a network database and use calibre server 1.48 on server machine on XP ?

sorry for my poor english but it's not my native language.

09-02-2014, 01:36 PM	#169
Khan-Dam Enthusiast Posts: 40 Karma: 10 Join Date: Jul 2011 Location: France Device: iPad, Kindle 3, Kobo Glo, Kobo Aura	My Experience about XP and Calibre 2.1.0 I Use XP for 10 Years on a XP Server, with a lot of process which run 24h a day 7 day a week 52 week by year without any trouble. Can't have to migrate to vista 7 or 8 ( my second server work fine with NT 5 ). I use calibre to integrate ebook in database, change metadata and eventualy convert format and use calibre_server to obtain internaly the book i want. My network is private network not on the internet just intranet. I use calibre for long time and very happy for all thing i can made with it. i load and use calibre 2.0 without any bug or trouble. So as i can't try or use the calibre v 2.1, i decide to follow the way of modify sources, there is my experence about that : - Try to obtain git sources -> more than 12 hours to get source ( add 2 try before, the first one, i break it after 5 hours think the process was in infinite loop, the second try was break by an internet shutdown ). - because process very long i Try to obtain archive -> it's ok a obtain it rapidly but untar it was long process about 3 or 4 hours. - According this thread i change source, fix ifxp and try to start manualy calibre, every thing ok it's work perfectly if i use calibre_debug -g after defining %CALIBRE_DEVELOP_FROM%. so the question is why you make solution for using version 2.1 with source way and don't allow normal way eventualy with some warning or with an environement variable to unlock xp test ? i understand you don't want to support xp version, but don't understand the difference between the to methods. What you do if i find a bug with my xp version 2.1 runing with source. And what you do if i find a bug in version 1.48 ? The Migration of XP to other version is not my question i dont want to change OS ( my hardware certainly don't support that ). So if release of calibre is the same as before one version a week the time to obtain and make calibre running increase considerably the time spend to change version. I think it's very domagable for calibre to leave all calibre user on xp alone i don't think user chage os just for 1 programme that don't run ! You tell to stay on version 1.48 is very strange if this version so stable and unbuggy why release to version 2.x. So there are my reflections, not agressive message and i respect the decision of the kovidgoyal. But in this way i use an older version without have the chance to use new things. The last thing is can i use version 2.x working with another machine running on Win7 to chnge a network database and use calibre server 1.48 on server machine on XP ? sorry for my poor english but it's not my native language. Last edited by Khan-Dam; 09-02-2014 at 01:39 PM.