Qtcurve toolbar icon size too large for GTK2

I'm using qtcurve for a unifed look of gtk and qt apps, however I have a small problem which seems to affect only thunar (which I use as a file manager)
The icons in the toolbar are way too large! Here is a screenshot:
How can I reduce their size ?
Last edited by moljac024 (2008-05-16 00:57:37)

Try Pressing and holding down the keyboard key Ctrl and then pressing 0 <br> the Control key is on the bottom left (& right) <br> 0 is the number Zero
Using Ctrl + 0 should reset the zoom, note it is set for each individual site.
* see [[how do i use zoom?]]
To get your toolbar back try pressing the keyboard Alt Key (that is probably next to the spacebar) and may temporarily cause the menu toolbar to display, pressing V then T should give you the options to set the toolbars you wish to display such as the bookmarks toolbar. Note your sone may well have been making use of the firefox button, that also give similar access to features
* see [[how do i get the firefox button?]] <-- clickable links (blue)
You may be in full screen viewing mode,that also causes the menu bars to disappear,try pressing keyboard key F11 (wait a few seconds for screen to redraw) that should toggle you in and out of full screen mode.
One thing you may considering in future is setting up on your Vista Operating System separate '''accounts''' for your self and your son, that way each can to some extent make changes the way they like without unduly affecting the other.
When setup like that each user has their own firefox [[profile|profiles]] and again changes can be made separately.
There could be other reasons for your problems, but I am presuming your son just forgot to return the setting to the ones you had been using.

Similar Messages

Compressed Video File Size Too Large for DVD?

I exported a one hour and 51 minute FCP Studio sequence to Compressor. I chose the 120 minute 4:3 best quality and Dolby for the audio. It took six hours and thirty five minutes to compress. When I bring the compressed "assets" into DVD Studio Pro, it indicates 5.9 gig. That won't fit on a standard DVD-R disk. Should I have used a different compression scheme when I made my choice in Compressor? Can I fit the movie on a standard DVD, or do I have to go back to FCP to shorten the sequence? What size must it be in FCP to fit on a standard DVD after Compressor and DVD Studio Pro?
Thanks

iDVD encodes (compresses) the video before burning
the DVD, so there's no problem. Your iMovie project
will fit.
The iDVD capacity is best expressed in time instead
of size. iMovie 4/5 can include up to 2 hours of
video. A little less, counting iDVD features.
Karl
Hi Karl
I have an iMovie file that is 3hr and 10min long. I have a dual layer burner and dual layer DVD's to burn onto. Will this file fit onto the 8.5GB disc? or do I have to compress it somehow? If there is some software that will do this could you let me know?
The dual layer DVD's say they will fit 215 min of video on them, so why does it reject my file when starting iDVD?
Thanks for your help

IMovie file size too large for one DVD

I've created my iMovie file and am ready to burn a DVD using iDVD to view on TV. Although my iMovie is only about 35 minutes, it is 7.73 GB. It is a simple movie. I only have a few titles, cross dissolves between clips and some audio.
How do I reduce my iMovie to fit on one DVD?
I don't have the option to "Export" under the "File" menu. And I've tried several of the "Share" formats which reduce the size, but none of them have given me TV viewing quality.
I am using iMovie HD 5 and the movie is widescreen.
Thanks!

iDVD encodes (compresses) the video before burning
the DVD, so there's no problem. Your iMovie project
will fit.
The iDVD capacity is best expressed in time instead
of size. iMovie 4/5 can include up to 2 hours of
video. A little less, counting iDVD features.
Karl
Hi Karl
I have an iMovie file that is 3hr and 10min long. I have a dual layer burner and dual layer DVD's to burn onto. Will this file fit onto the 8.5GB disc? or do I have to compress it somehow? If there is some software that will do this could you let me know?
The dual layer DVD's say they will fit 215 min of video on them, so why does it reject my file when starting iDVD?
Thanks for your help

This backup is too large for the backup volume - ridiculous Size!!!

Hi .. i own a macbook 13" aluminium, I have Snow Leopard 10.6.2 , and i change my internal hard drive to a 500Gb.
I bought 1Tb Western Digital My Book USB External Drive to use it for back ups using Time machine.. at the beginning worked great, when i changed my hard drive i restore everything in lest than 2 hours.
Then one time, it said that the hard drive where going out of space, and i said to delete the oldest backups, it erase everything and kept the last back up. Since then, it came a message
*_+This backup is too large for the backup volume. The backup requires 2.73EB but only 995 Gb are available.*+_
its ridiculous, when i go to the time machine preference, it said that the full size back up it would take 83Gb only.
I tried everything, formatting the unit, taking out the partition , and making it out again, it makes the first full back up, but then the same message...
Please anyone... i am desperate
Thanks Again
Daniel

DanielFaour wrote:
*_+This backup is too large for the backup volume. The backup requires 2.73EB but only 995 Gb are available.*+_
Hi, and welcome to the forums.
That message seems to indicate that something is corrupted on your internal HD. Do a +*Verify Disk+* on it, per #A5 in the Time Machine - Troubleshooting *User Tip,* also at the top of this forum.
If that finds errors, you'll have to use the procedure in the yellow box there to Repair them.
If that does not find errors, Restart your Mac and do a "full reset" of Time Machine, per #A4 there.
I tried everything, formatting the unit, taking out the partition , and making it out again, it makes the first full back up, but then the same message...
What partition? Are there multiple partitions on your TM drive? How large is the one for Time Machine? Check the setup per #C1 of the Troubleshooting Tip.

Imp-00020 long column too large for column buffer size (22)

Hi friends,
I have exported (through Conventional path) a complete schema from Oracle 7 (Sco unix patform).
Then transferred the export file to a laptop(window platform) from unix server.
And tried to import this file into Oracle10.2. on windows XP.
(Database Configuration of Oracle 10g is
User tablespace 2 GB
Temp tablespace 30 Mb
The rollback segment of 15 mb each
undo tablespace of 200 MB
SGA 160MB
PAGA 16MB)
All the tables imported success fully except 3 tables which are having AROUND 1 million rows each.
The error message comes during import are as following for these 3 tables
imp-00020 long column too large for column buffer size (22)
imp-00020 long column too large for column buffer size(7)
The main point here is in all the 3 tables there is no long column/timestamp column (only varchar/number columns are there).
For solving the problem I tried following options
1.Incresed the buffer size upto 20480000/30720000.
2.Commit=Y Indexes=N (in this case does not import complete tables).
3.first export table structures only and then Data.
4.Created table manually and tried to import the tables.
but all efforts got failed.
still getting the same errors.
Can some one help me on this issue ?
I will be grateful to all of you.
Regards,
Harvinder Singh
[email protected]
Edited by: user462250 on Oct 14, 2009 1:57 AM

Thanks, but this note is for older releases, 7.3 to 8.0...
In my case both export and import were made on a 11.2 database.
I didn't use datapump because we use the same processes for different releases of Oracle, some of them do not comtemplate datapump. By the way, shouldn't EXP / IMP work anyway?

What can I do for "File size too large"?

Spent 9 hrs creating a slideshow that I saved. Closed PSE 11 and reopened and can no longer find the slideshow. When I select Find, Media type, Project, nothing appears, but there is a gray box in my grid that says "File size too large". Is this my slideshow and if so how can I recover it? I am sick as this was a large time investment for my daughter's wedding which is very soon! Please help if you can.

I don't know anything about slide shows but if a picture is too large this is just a warning message, if I click a pic with this message it does show up. Have you tried clicking the thumbnail?

This backup is too large for the backup volume - ridiculous backup size

I have had big problems with Time Machine today. I have been successfully using it for 2 months now. I have about 30Gb spare on my iMac hard drive (out of 233Gb) and my Time Machine uses 195Gb out of 466Gb available.
However, today I have lost all my Time Machine history except for one backup made this morning, and I am now getting an error message saying:
"Time Machine Error
This backup is too large for the backup volume. The backup requires 161061280.0 GB but only 270.4 GB are available.
To select a larger volume, or make backup smaller by excluding files, open System Preferences and choose Time Machine"
Clearly the required backup volume is wrong - that's 161,000.0TB!!!
The same message has come up 3 times now.
Can anyone help/advise on what to do next?

Thanks Peggy,
I re-indexed Spotlight and ran Time Machine again, but got exactly the same error message and the same massive storage required.
I've opened Console as you suggested and these are a set of the messages from one back-up attempt yesterday (Console doesn' show anything earlier than 17.32 yesterday - but the problem started earlier than that I believe):
"16/01/2008 17:32:52 /System/Library/CoreServices/backupd[326] Backup requested by automatic scheduler
16/01/2008 17:32:52 /System/Library/CoreServices/backupd[326] Starting standard backup
16/01/2008 17:32:52 /System/Library/CoreServices/backupd[326] Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
16/01/2008 17:32:53 /System/Library/CoreServices/backupd[326] Event store UUIDs don't match for volume iMac Hard Drive
16/01/2008 17:32:53 /System/Library/CoreServices/backupd[326] Node requires deep traversal:/ reason:kFSEDBEventFlagMustScanSubDirs|kFSEDBEventFlagReasonEventDBUntrustable|
16/01/2008 17:44:48 /System/Library/CoreServices/backupd[326] Starting pre-backup thinning: 157286.40 TB requested (including padding), 270.35 GB available
16/01/2008 17:44:48 /System/Library/CoreServices/backupd[326] No expired backups exist - deleting oldest backups to make room
16/01/2008 17:44:48 /System/Library/CoreServices/backupd[326] Error: backup disk is full - all 0 possible backups were removed, but space is still needed.
16/01/2008 17:44:48 /System/Library/CoreServices/backupd[326] Backup Failed: unable to free 157286.40 TB needed space
16/01/2008 17:44:49 /System/Library/CoreServices/backupd[326] Backup failed with error: Not enough available disk space on the target volume."

"Backup is too large for the backup volume" error

I've been backing up with TM for a while now, and finally it seems as though the hard drive is full, since I'm down to 4.2GB available of 114.4GB.
Whenever TM tries to do a backup, it gives me the error "This backup is too large for the backup volume. The backup requires 10.8 GB but only 4.2GB are available. To select a larger volume, or make the backup smaller by excluding files, open System Preferences and choose Time Machine."
I understand that I have those two options, but why can't TM just erase the oldest backup and use that free space to make the new backup? I know a 120GB drive is pretty small, but if I have to just keep accumulating backups infinitely, I'm afraid I'll end up with 10 years of backups and a 890-zettabyte drive taking up my garage. I'm hoping there's a more practical solution.

John,
Please review the following article as it might explain what you are encountering.
*_“This Backup is Too Large for the Backup Volume”_*
First, much depends on the size of your Mac’s internal hard disk, the quantity of data it contains, and the size of the hard disk designated for Time Machine backups. It is recommended that any hard disk designated for Time Machine backups be +at least+ twice as large as the hard disk it is backing up from. You see, the more space it has to grow, the greater the history it can preserve.
*Disk Management*
Time Machine is designed to use the space it is given as economically as possible. When backups reach the limit of expansion, Time Machine will begin to delete old backups to make way for newer data. The less space you provide for backups the sooner older data will be discarded. [http://docs.info.apple.com/article.html?path=Mac/10.5/en/15137.html]
However, Time Machine will only delete what it considers “expired”. Within the Console Logs this process is referred to as “thinning”. It appears that many of these “expired” backups are deleted when hourly backups are consolidated into daily backups and daily backups are consolidated into weekly backups. This consolidation takes place once hourly backups reach 24 hours old and daily backups reach about 30 days old. Weekly backups will only be deleted, or ‘thinned’, once the backup drive nears full capacity.
One thing seems for sure, though; If a new incremental backup happens to be larger than what Time Machine currently considers “expired” then you will get the message “This backup is too large for the backup volume.” In other words, Time Machine believes it would have to sacrifice to much to accommodate the latest incremental backup. This is probably why Time Machine always overestimates incremental backups by 2 to 10 times the actual size of the data currently being backed up. Within the Console logs this is referred to as “padding”. This is so that backup files never actually reach the physically limits of the backup disk itself.
*Recovering Backup Space*
If you have discovered that large unwanted files have been backed up, you can use the Time Machine “time travel” interface to recovered some of that space. Do NOT, however, delete files from a Time Machine backup disk by manually mounting the disk and dragging files to the trash. You can damage or destroy your original backups by this means.
Additionally, deleting files you no longer wish to keep on your Mac does not immediately remove such files from Time Machine backups. Once data has been removed from your Macs' hard disk it will remain in backups for some time until Time Machine determines that it has "expired". That's one of its’ benefits - it retains data you may have unintentionally deleted. But eventually that data is expunged. If, however, you need to remove backed up files immediately, do this:
Launch Time Machine from the Dock icon.
Initially, you are presented with a window labeled “Today (Now)”. This window represents the state of your Mac as it exists now. +DO NOT+ delete or make changes to files while you see “Today (Now)” at the bottom of the screen. Otherwise, you will be deleting files that exist "today" - not yesterday or last week.
Click on the window just behind “Today (Now)”. This represents the last successful backup and should display the date and time of this backup at the bottom of the screen.
Now, navigate to where the unwanted file resides. If it has been some time since you deleted the file from your Mac, you may need to go farther back in time to see the unwanted file. In that case, use the time scale on the right to choose a date prior to when you actually deleted the file from your Mac.
Highlight the file and click the Actions menu (Gear icon) from the toolbar.
Select “Delete all backups of <this file>”.
*Full Backup After Restore*
If you are running out of disk space sooner than expected it may be that Time Machine is ignoring previous backups and is trying to perform another full backup of your system? This will happen if you have reinstalled the System Software (Mac OS), or replaced your computer with a new one, or hard significant repair work done on your exisitng Mac. Time Machine will perform a new full backup. This is normal. [http://support.apple.com/kb/TS1338]
You have several options if Time Machine is unable to perform the new full backup:
A. Delete the old backups, and let Time Machine begin a fresh.
B. Attach another external hard disk and begin backups there, while keeping this current hard disk. After you are satisfied with the new backup set, you can later reformat the old hard disk and use it for other storage.
C. Ctrl-Click the Time Machine Dock icon and select "Browse Other Time Machine disks...". Then select the old backup set. Navigate to files/folders you don't really need backups of and go up to the Action menu ("Gear" icon) and select "Delete all backups of this file." If you delete enough useless stuff, you may be able to free up enough space for the new backup to take place. However, this method is not assured as it may not free up enough "contiguous space" for the new backup to take place.
*Outgrown Your Backup Disk?*
On the other hand, your computers drive contents may very well have outgrown the capacity of the Time Machine backup disk. It may be time to purchase a larger capacity hard drive for Time Machine backups. Alternatively, you can begin using the Time Machine Preferences exclusion list to prevent Time Machine from backing up unneeded files/folders.
Consider as well: Do you really need ALL that data on your primary hard disk? It sounds like you might need to Archive to a different hard disk anything that's is not of immediate importance. You see, Time Machine is not designed for archiving purposes, just as a backup of your local drive(s). In the event of disaster, it can get your system back to its' current state without having to reinstall everything. But if you need LONG TERM storage, then you need another drive that is removed from your normal everyday working environment.
This KB article discusses this scenario with some suggestions including Archiving the old backups and starting fresh [http://docs.info.apple.com/article.html?path=Mac/10.5/en/15137.html]
Let us know if this clarifies things.
Cheers!

OS10.3.1 a disaster! Among other things, the dsplay is too large for screen

I do not like OS 10.3 ! After my Z10 was updated to 10.3.1.1779 about a month ago, I access it because the password entry keyboard displayed for about 1/10 sec leaving a black screen.
After a device reset the device the keyboard remained visible but did not respond to touches (actually it did respond randomly to some). Finally another reset gave me a usable keyboard.
But the device always opens with an icon display about 20% too large for my screen and requires several shrink attempts before the proper size displays. Each attempt simply bounces back to the oversize state.
Unfortunately, this also happens with every app (including "Settings") opened. Yesterday, I couldn't return to the main of Settings because the sub-page wouldn't shrink to expose the "<' button - a close and re-open was the only way to get back to the main page.
Other points I hate about the OS: I've noticed my active wallpaper (not custom but from 10.2) is not listed in the the new 10.3 wallpaper list and since I don't know where its stored I can't try one of the newer ones without giving up on the present wallpaper.
The date displayed on the home screen is too faint to be read with my wallpaper. I know there are some people who think black on black is cool; they obviously have great eyesight. The new 10.3 compass is now totally useless and the new clock is not much better but is at least still usable by a change to a digital display.
I recently tried to check the time on a sunny afternoon and gave up because I couldn't make out the white lines on the black background. I find the stupidity of black on black unfathomable and in over 40 years of software development I have never seen something as wasteful of engineering time as products with poor user interfaces (i.e. black on black). Why can't these apps offer the user the ability to change the colour?
The calculator has also regressed. Again all black (cool!), though that's not the issue here. For the longest time I thought it no longer supported scientific operations until I accidentally got a lucky swipe to bring it into view.
However, the requirement of a half-dozen swipe attempts for each display change reduces this app to a space waster or only to be only useful for simple operations and units conversion. I'm going to try a reload of the OS but unfortunately that won't improve the apps.
Is this standard procedure that Blackberry destroys all (blackberry) apps of the previous version with new ones at each update and offers no way to get back or protect against such changes?

Hi All,
I have already checked below configuration T-Code Value :
T-Code : OBA0 :
Tolerance for Groups of G/L Accounts in Local Curre :
Debit posting : 0 TWD, Percentage 0 %
Credit posting : 0 TWD, Percentage 0 %
T-Code : OBA4 :
Upper limits for posting procedures :
Amount per document : 9,999,999,999,999
Amount per open item account item : 999,999,999,999
cash discount per line item : 1%
Permitted payment differences :
Revenue : Amount 100, Percent 1%, Cash discnt adj. to : 100
Expense : Amount 100, Percent 1%, Cash discnt adj. to : 100
I don't understand when AR open item amount is USD 100.3, and incoming payment 101.12, The system can auto clearing by current configuration, but change the AR open item amount to USD 0.3 and change incoming payment amount to 1.12, The system alert error message "The difference is too large for clearing". The same system configuration and the same "Not assigned" value in choosing open item screen, but produce different results!
How should i change the configuration?
Best regards,
Eric
Edited by: Eric Yang on Sep 12, 2008 2:12 AM

Backup too large for volume

I have 2 macbook pro's (120GB & 160GB) backing up to a 500GB TM.
both were backing up just fine, however in the past month the 160GB
macbook pro keeps getting this message.....
"backup too large for volume?"
and subsequently the backup fails?
the size of the backup is less than the free space on the TM drive...
any help?

dave,
*_Incremental Backups Seem Too Large!_*
Open the Time Machine Prefs on the Mac in question. How much space does it report you have "Available"? When a backup is initiated how much space does it report you need?
Now, consider the following, it might give you some ideas:
Time Machine performs backups at the file level. If a single bit in a large file is changed, the WHOLE file is backed up again. This is a problem for programs that save data to monolithic virtual disk files that are modified frequently. These include Parallels, VMware Fusion, Aperture vaults, or the databases that Entourage and Thunderbird create. These should be excluded from backup using the Time Machine Preference Exclusion list. You will, however, need to backup these files manually to another external disk.
One poster observed regarding Photoshop: “If you find yourself working with large files, you may discover that TM is suddenly backing up your scratch disk's temp files. This is useless, find out how to exclude these (I'm not actually sure here). Alternatively, turn off TM whilst you work in Photoshop.” [http://discussions.apple.com/thread.jspa?threadID=1209412]
If you do a lot of movie editing, unless these files are excluded, expect Time Machine to treat revised versions of a single movie as entirely new files.
If you frequently download software or video files that you only expect to keep for a short time, consider excluding the folder these are stored in from Time Machine backups.
If you have recently created a new disk image or burned a DVD, Time Machine will target these files for backup unless they are deleted or excluded from backup.
*Events-Based Backups*
Time Machine does not compare file for file to see if changes have been made. If it had to rescan every file on your drive before each backup, it would not be able to perform backups as often as it does. Rather, it looks for EVENTS (fseventsd) that take place involving your files and folders. Moving/copying/deleting/saving files and folders creates events that Time Machine looks for. [http://arstechnica.com/reviews/os/mac-os-x-10-5.ars/14]
Installing new software, upgrading existing software, or updating Mac OS X system software can create major changes in the structure of your directories. Every one of these changes is recorded by the OS as an event. Time Machine will backup every file that has an event associated with it since the installation.
Files or folders that are simply moved or renamed are counted as NEW files or folders. If you rename any file or folder, Time Machine will back up the ENTIRE file or folder again no matter how big or small it is.
George Schreyer describes this behavior: “If you should want to do some massive rearrangement of your disk, Time Machine will interpret the rearranged files as new files and back them up again in their new locations. Just renaming a folder will cause this to happen. This is OK if you've got lots of room on your backup disk. Eventually, Time Machine will thin those backups and the space consumed will be recovered. However, if you really want recover the space in the backup volume immediately, you can. To do this, bring a Finder window to the front and then click the Time Machine icon on the dock. This will activate the Time Machine user interface. Navigate back in time to where the old stuff exists and select it. Then pull down the "action" menu (the gear thing) and select "delete all backups" and the older stuff vanishes.” (http://www.girr.org/mac_stuff/backups.html)
*TechTool Pro Directory Protection*
This disk utility feature creates backup copies of your system directories. Obviously these directories are changing all the time. So, depending on how it is configured, these backup files will be changing as well which is interpreted by Time Machine as new data to backup. Excluding the folder these backups are stored in will eliminate this effect.
*Backups WAY Too Large*
If an initial full backup or subsequent incremental backup is tens or hundreds of Gigs larger than expected, check to see that all unwanted external hard disks are still excluded from Time Machine backups.
This includes the Time Machine backup drive ITSELF. Normally, Time Machine is set to exclude itself by default. But on rare occasions it can forget. When your backup begins, Time Machine mounts the backup on your desktop. (For Time Capsule users it appears as a white drive icon labeled something like “Backup of (your computer)”.) If, while it is mounted, it does not show up in the Time Machine Prefs “Do not back up” list, then Time Machine will attempt to back ITSELF up. If it is not listed while the drive is mounted, then you need to add it to the list.
*FileVault / Boot Camp / iDisk Syncing*
Note: Leopard has changed the way it deals with FileVault disk images, so it is not necessary to exclude your Home folder if you have FileVault activated. Additionally, Time Machine ignores Boot Camp partitions as the manner in which they are formatted is incompatible. Finally, if you have your iDisk Synced to your desktop, it is not necessary to exclude the disk image file it creates as that has been changed to a sparsebundle as well in Leopard.
If none of the above seem to apply to your case, then you may need to attempt to compress the disk image in question. We'll consider that if the above fails to explain your circumstance.
Cheers!

Cannot decrypt RSA encrypted text : due to : input too large for RSA cipher

Hi,
I am in a fix trying to decrypt this RSA encrypted String ... plzz help
I have the encrypted text as a String.
This is what I do to decrypt it using the Private key
- Determine the block size of the Cipher object
- Get the array of bytes from the String
- Find out how many block sized partitions I have in the array
- Encrypt the exact block sized partitions using update() method
- Ok, now its easy to find out how many bytes remain (using % operator)
- If the remaining bytes is 0 then simply call the 'doFinal()'
i.e. the one which returns an array of bytes and takes no args
- If the remaining bytes is not zero then call the
'doFinal(byte [] input, int offset, in inputLen)' method for the
bytes which actually remained
However, this doesnt work. This is making me go really crazy.
Can anyone point out whats wrong ? Plzz
Here is the (childish) code
Cipher rsaDecipher = null;
//The initialization stuff for rsaDecipher
//The rsaDecipher Cipher is using 256 bit keys
//I havent specified anything regarding padding
//And, I am using BouncyCastle
String encryptedString;
// read in the string from the network
// this string is encrypted using an RSA public key generated earlier
// I have to decrypt this string using the corresponding Private key
byte [] input = encryptedString.getBytes();
int blockSize = rsaDecipher.getBlockSize();
int outputSize = rsaDecipher.getOutputSize(blockSize);
byte [] output = new byte[outputSize];
int numBlockSizedPartitions = input.length / blockSize;
int numRemainingBytes = input.length % blockSize;
boolean hasRemainingBytes = false;
if (numRemainingBytes > 0)
hasRemainingBytes = true;
int offset = 0;
int inputLen = blockSize;
StringBuffer buf = new StringBuffer();
for (int i = 0; i < numBlockSizedPartitions; i++) {
output = rsaDecipher.update(input, offset, blockSize);
offset += blockSize;
buf.append(new String(output));
if (hasRemainingBytes) {
//This is excatly where I get the "input too large for RSA cipher"
//Which is suffixed with ArrayIndexOutofBounds
output = rsaDecipher.doFinal(input,offset,numRemainingBytes);
} else {
output = rsaDecipher.doFinal();
buf.append(new String(output));
//After having reached till here, will it be wrong if I assumed that I
//have the properly decrypted string ???

Hi,
I am in a fix trying to decrypt this RSA encrypted
String ... plzz helpYou're already broken at this point.
Repeat after me: ciphertext CANNOT be safely represented as a String. Strings have internal structure - if you hand ciphertext to the new String(byte[]) constructor, it will eat your ciphertext and leave you with garbage. Said garbage will fail to decrypt in a variety of puzzling fashions.
If you want to transmit ciphertext as a String, you need to use something like Base64 to encode the raw bytes. Then, on the receiving side, you must Base64-DEcode back into bytes, and then decrypt the resulting byte[].
Second - using RSA as a general-purpose cipher is a bad idea. Don't do that. It's slow (on the order of 100x slower than the slowest symmetric cipher). It has a HUGE block size (governed by the keysize). And it's subject to attack if used as a stream-cipher (IIRC - I can no longer find the reference for that, so take it with a grain of salt...) Standard practice is to use RSA only to encrypt a generated key for some symmetric algorithm (like, say, AES), and use that key as a session-key.
At any rate - the code you posted is broken before you get to this line:byte [] input = encryptedString.getBytes();Go back to the encrypting and and make it stop treating your ciphertext as a String.
Grant

ERROR : OpenDoc CR to PDF - File is too large for attachment.

We are getting the following error in 3.1 using an OpenDoc call when we call a large Crystal Report to PDF format...
Error : 52cf6f8f4bbb6d3.pdf File is too large for attachment.
It runs OK from BOE when given parameters that returned 44 pages. (PDF = 139 KB)
We get the error on a parameter-set that returns 174 pages when run via CR Desktop or as a SCHEDULED Instance. (PDF = 446 KB).
Client application can't use the SDKs to SCHEDULE Instances - only configured for OpenDoc calls.....
The BOE server is running on SOLARIS - and it's is a 2 Server CMS-Cluster.
The problem is SPORADIC, so I am thinking the issue is related to a specific setting on one of the servers.
Any thoughts on where to start looking...?

Problem is _not _with the number of Rows returned - it is an issue with the size of the PDF file that it is trying to move.
Found a possible WINDOWS solution on BOB - need to find if there is an equivalent for SOLARIS...
Check the dsws.properties on web server D:\Program Files\Business Objects\Tomcat55\webapps\dswsbobje\WEB-INF\classes
See if you can change any parameter to remove size limitation.
#Security measure to limit total upload file size
maximumUploadFileSize = 10485760

ReportExportControl -- File is too large for attachment

Hi all,
Back with a exception again.
Few reports deployed on BOXIR2 SP4 comes with an error as following
com.crystaldecisions.report.web.viewer.ReportExportControl
15bf5ea9377e1c1.rtf File is too large for attachment.
Few reports take date range as input and generates result based on that. When date range is small report is generated without any problem. If is large and has large set of records(approx above 10K records) then comes up with the above error.
Another set of reports whatever be the case throws this error.
But when the parameters are set in CMS console and run in console report is generated without any problem what ever be the date range.
After searching a lot no solutions in hand!!
Please suggest solutions/possible scenarios / checklist to solve this issue.
Thanks & Regards
lnarayanan

It turns out the report was so large it was basically overloading everything (disk space, cache sizes, timeouts, etc.) ... Here's the solution from the case:
1) For page server and cache server
Make sure location of Temp Files/Cache files has enough free space (more than 500 MB)
2) For page server and cache server
Minutes Before an Idle Connection is Closed = 90
3) For page server
Minutes Before an Idle Report Job is Closed = 90
4) For cache server
Maximum Simultaneous Processing Threads = automatic
5) In the command line of page server and cache server, add
"-requestTimeout 5400000" [without " "]
6) Maximum Cache Size Allowed (KBytes) = set it to an appropriate value (for e.g. for 500 Mb, value should be 500*1024 = 512000)
(This setting limits the amount of hard disk space used to store cached pages. If we need to handle large reports, a large cache size is needed. Maximum allowed is 2048 GB)
After all this, an "Error 500 - Java heap space" happened. The amount of memory allocated to a JVM application can be set using the options -Xms (the initial size) and -Xmx (the maximum size).
Regards,
Bryan

Inserted value too large for column error while scheduling a job

Hi Everyone,
I am trying to schedule a PL SQL script as a job in my Oracle 10g installed and running on Windows XP.
While trying to Submit the job I get the error as "Inserted value too large for column:" followed by my entire code. The code is correct - complies and runs in Oracle ApEx's SQL Workshop.
The size of my code is 4136 character, 4348 bytes and 107 lines long. It is a code that sends an e-mail and has a +utl_smtp.write_data([Lots of HTML])+
There is no insert statement in the code whatsoever, the code only queries the database for data...
Any idea as to why I might be getting this error??
Thanks in advance
Sid

The size of my code is 4136 character, 4348 bytes and 107 lines long. It is a code that sends an e-mail and has a utl_smtp.write_data(Lots of HTML)SQL variable has maximum size of 4000

How can I put my recently purchased iTunes movies on to my thumb drive and WD My Passport external hard drive. My Mac keeps saying "can't be copy because it is too large for the volumes format

How can I put my recently purchased iTunes movies onto my thumb drive and WD my passport external hard drive.My Mac is saying that can't be copied because it is too large for volumes format

[file] is too large for the volumes format
That is usually an indication that the Volume was never Erased or Partitioned for GUID partition table and Mac OS, and is still in a Windows format.
Mac OS X Extended (journaled) has no such file-size limitations

Qtcurve toolbar icon size too large for GTK2

Similar Messages

Maybe you are looking for