Page 10 of 23
Posted: Tue Feb 13, 2007 3:53 pm
by gnozal
10 Reasons You Don’t Need Vista Today
1. Vista Requires a Fairly Powerful Machine
2. Application Incompatibilities
3. Vista is Crazy Expensive
4. No Hardware Audio
5. Vista Doesn’t Work With a Lot of Bleeding-Edge Hardware
6. Vista Doesn’t Work Well With Some Games
7. Vista Includes Consumer-Unfriendly DRM
8. Poor Driver Support
9. Vista is Kind of Annoying
10. You Can Wait
http://maximumpc.com/2007/01/10_reasons_you.html
10 reasons not to get Vista
1. You don't actually need it
2. Cost $$
3. On that note, it's outrageously overpriced
4. Upgrading hardware
5. Driver support
6. Applications that don't work
7. It's a big fat target
8. UAC
9. DRM
10. The draconian license
http://apcmag.com/5049/10_reasons_not_to_get_vista
etc...

Posted: Tue Feb 13, 2007 4:12 pm
by DoubleDutch
I don't really want to enter into a Vista debate.
But...
I also thought that upgrading to Vista was a waste of time and would be a lot of hastle.
But I was wrong. I don't personally know of ANYONE who has had any problems at all, the drivers that were not present on the installation disc - were on the first online update.
I have heard of a lot of scare stories, but from my experience thats all they are turning out to be - stories.
If you like, you can download Vista from Microsoft, try it out for 30 days. If you don't like it then go back you don't want to update or think that its got compatibility problems.
One thing is fo sure, Vista is here now. If you want your libraries to maintain their credibility and reputation, I suggest you try figure out whats gone wrong - rather than an "I'm alright Jack" response...
The only problem I have found with some of my own PureBasic code is that I didn't code by some of the rules anyway. It was just a coincidence that they didn't crash on XP or below. I am glad that they have made the OS stricter on memory access, etc. This makes it less likely that a bad program will interfere with others and we will have less false bugs and more chance of finding out where problems really are.
My offer of helping you to make your libraries work with Vista still stands, I'd prefer that to writing my own.
I know you want to hide your source code, but there must be a way for us to fix the problem that will protect your source?
Posted: Wed Mar 21, 2007 12:39 am
by Joakim Christiansen
I tested this POP3 library on windows vista, works fine for some emails but some emails returns a NULL at PurePOP3_GetMessageTextInMemory().
But I am able to get the content reading from PurePOP3_GetMessageBufferAddress(). Would you be able to fix this if I send you the content maybe?
Posted: Wed Mar 21, 2007 8:27 am
by gnozal
Joakim Christiansen wrote:I tested this POP3 library on windows vista, works fine for some emails but some emails returns a NULL at PurePOP3_GetMessageTextInMemory().
But I am able to get the content reading from PurePOP3_GetMessageBufferAddress(). Would you be able to fix this if I send you the content maybe?
Maybe. If it's a boundary problem or something like that.
Posted: Wed Mar 21, 2007 8:48 am
by Joakim Christiansen
You got PM!

Posted: Wed Mar 21, 2007 12:06 pm
by gnozal
Joakim Christiansen wrote:You got PM!

I have uploaded
http://freenet-homepage.de/gnozal/PurePOP3_BETA.zip (standard ANSI lib), to be placed in the userlibraries folder.
Please test it (with messages that did not work [to see if it fixes the problem] and with messages that did work [to check that nothing is broken])
Posted: Wed Mar 21, 2007 5:07 pm
by Joakim Christiansen
Looks like it works now gnozal!
Thanks, great work!
Posted: Wed Mar 21, 2007 5:18 pm
by gnozal
Joakim Christiansen wrote:Looks like it works now gnozal!
Thanks, great work!
Ok, I will update the PB3.94/PB4.0x librairies with the new code when I get some free time.
Thanks.
Posted: Wed Mar 21, 2007 7:07 pm
by DoubleDutch
gnozal: Do you think there maybe a similar problem with PureSMTP?
Posted: Fri Mar 23, 2007 9:59 am
by gnozal
DoubleDutch wrote:gnozal: Do you think there maybe a similar problem with PureSMTP?
No.
It was just a message structure problem ('Content-Type:' / 'Content-Transfer-Encoding:' unusual order)
Posted: Fri Mar 23, 2007 1:53 pm
by gnozal
Update (Both libs)
Changes :
- fix for messages with inverted 'Content-Type:' / 'Content-Transfer-Encoding:' order
Posted: Tue Apr 03, 2007 4:48 pm
by gnozal
Update (Both libs)
Changes :
- fixed attachment base64 decoding problem
- fixed seldom but critical invalid memory error
Posted: Mon Apr 23, 2007 8:01 pm
by Frontier
gnozal wrote:Update (Both libs)
Changes :
- fixed attachment base64 decoding problem
- fixed seldom but critical invalid memory error
Hello gnozal,
After this last update, code that used to work with PurePOP3, does no longer works. In particular, it seems that PurePOP3_SaveAttachementsToFile() is broken; the attachment is saved, but it's corrupt.
Here's a link to download what PurePOP3_Trace() returns for the session.
No AV or any other e-mail/internet scanning software is running. The program runs under Windows XP SP2 with the latest Windows Updates.
http://www.sendspace.com/file/xb0j52
Thank you very much in advance for your help.
Posted: Tue Apr 24, 2007 8:18 am
by gnozal
Frontier wrote:After this last update, code that used to work with PurePOP3, does no longer works. In particular, it seems that PurePOP3_SaveAttachementsToFile() is broken; the attachment is saved, but it's corrupt.
Some stupid typo ...
I have uploaded
http://freenet-homepage.de/gnozal/PurePOP3_BETA.zip (standard ANSI lib), to be placed in the userlibraries folder.
Please test it (with messages that did not work [to see if it fixes the problem] and with messages that did work [to check that nothing is broken])
Thanks
Posted: Tue Apr 24, 2007 12:05 pm
by Frontier
gnozal wrote:Frontier wrote:After this last update, code that used to work with PurePOP3, does no longer works. In particular, it seems that PurePOP3_SaveAttachementsToFile() is broken; the attachment is saved, but it's corrupt.
Some stupid typo ...
I have uploaded
http://freenet-homepage.de/gnozal/PurePOP3_BETA.zip (standard ANSI lib), to be placed in the userlibraries folder.
Please test it (with messages that did not work [to see if it fixes the problem] and with messages that did work [to check that nothing is broken])
Thanks
Hello,
The new version does indeed work with the broken messages. With the correct messages I'll know tomorrow.