3GP and Rapiz problems - PSP-Forum.com

ZeLdAfReAk · 03-13-2005, 06:58 PM

I've tried converting tons of stuff with both of them, many times, and I've only sucessefully converted one thing. I've looked at 5 different guides to use the converters, and done exactly what they say, but I keep getting errors. With 3GP I keep getting the error "2048", does anyone know what that error means? And is anyone else having tons of problems with these converters? ALso is there any other converters (prefferably free) that work better than these 2?

ehandlr · 03-14-2005, 01:20 PM

Open up Quicktime and choose the "update" function. I downloaded the newest (or so I thought) Quicktime from www.apple.com/downloads however I still had to use the "update" function. I don't understand why they don't just make the newest version available right off the bat. But I had the same exact problem. Once I updated, it worked great.

03-13-2005, 06:58 PM	#1 (permalink)
ZeLdAfReAk Hi! I'm new around here... Join Date: Mar 2005 Posts: 4	3GP and Rapiz problems I've tried converting tons of stuff with both of them, many times, and I've only sucessefully converted one thing. I've looked at 5 different guides to use the converters, and done exactly what they say, but I keep getting errors. With 3GP I keep getting the error "2048", does anyone know what that error means? And is anyone else having tons of problems with these converters? ALso is there any other converters (prefferably free) that work better than these 2?

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

03-14-2005, 01:20 PM	#2 (permalink)
ehandlr PSP-Forum Member Join Date: Mar 2005 Location: Newark, DE Posts: 174	Open up Quicktime and choose the "update" function. I downloaded the newest (or so I thought) Quicktime from www.apple.com/downloads however I still had to use the "update" function. I don't understand why they don't just make the newest version available right off the bat. But I had the same exact problem. Once I updated, it worked great.