CSB Publishing Settings · Using FTP · Search engines: Spiders & Robots · Meta Tag, Keywords, Page Properties · Frames or No-Frames? · Subdirectory · Working Window · Design file image errors · Design file will not save · Publishing Errors · Page Layout · CSB3 & CSB4 Known Issues (Problems) · CSB5 NOTES · Upgrade to CSB5
Design file image errors
The design file refuses to open or allow you to insert photos!
A few people have reported a very strange situation dealing with images and CSB: Some comments:
- CSB is not reading images
- Any image I try to add to site CSB gives me the error that the image is corrupt although I can open images in other software like photoshop no problem.
- Whenever I open a CSB document I get pop ups for every image number saying I have a critical error.
- No matter what CSB document I open I get these pop ups showing image this and image that can't be opened because CSB has found a problem with the image. I keep clicking ok but they keep popping up and you can't work. You can't even edit text. All you can do is click ok on these pop ups.. finally you have to cntrl>alt>delete to get out of CSB.
The images that you see were provided by Fred (Lake Pirate) a long-time user of CSB who suddenly had this problem.
After testing so many things, checking files, rolling back (system restore), reinstalling, running in safe mode, and more the problem persisted.
GreenAcresJan on the Globalscape forum had the issue happen to her back in 2006.
Wanda, the SafariWoman, came up with the answer.
And when Fred had the issue, Jan reminded us all of Wanda's answer.
This page now documents it all for long-term reference!
Wanda's post 12/1/2006 - I found the solution!
DEP Data Execution Prevention had been turned on for all programs and it apparently was causing the software not to execute for some reason. I switched it Windows system only, restarted and now it works perfectly fine just like it ever did.
On Xp search help for DEP and the screen for selecting settings should be one of the options you get - check it there and if all programs is selected change to windows only.
If this works for you too please let us know.
greenacresjan responded: 12/1/2006
UREKA! IT WORKS!!!! I was getting warm and was hunting up how a person sets permissions when I checked my mail and found your solution. I'd just about driven myself NUTS ruling out all the possibilities... and here I did it to myself! (I vaguely remember seeing something about it being suggested that you uncheck that box if you use a different firewall, which I do. Otherwise, I'd never have messed with it. So much for believing everything you read, huh?!) So thankyou, thankyou, thankyou for hunting it down and passing it along immediately.
Rickasaurus...I wouldn't have had the impetus to keep at it had you not proven that it had nothing to do with my actual file(s).
Can't thank everybody enough for their input and help with this one!
To look up the instructions in XP help:
- Click START
- Click Help and Support.
- In the search field near the top, type in DEP and press the green > arrow.
- In your left side of the window you get search results, and you can click the TURN DATA EXECUTION PREVENTION ON OR OFF FOR A PROGRAM answer. This is the instruction in XP help:
Here are screenprints to walk you through step by step:
What is DEP and why can it interfere with CSB? Pruned from the free content in Wikipedia:
Data Execution Prevention (DEP) is a security feature included in more modern Microsoft Windows operating systems that is intended to prevent an application or service from executing code from a non-executable memory region. This helps prevent certain exploits that store code via a buffer overflow, for example. DEP runs in two modes: hardware-enforced DEP for CPUs that can mark memory pages as nonexecutable, and software-enforced DEP with a limited prevention for CPUs that do not have hardware support. Software-enforced DEP does not protect from execution of code in data pages, but instead from another type of attack (SEH overwrite).
In some instances, Data Execution Prevention can have the unintended consequence of preventing legitimate software from executing. In these cases, the affected software needs to be flagged as being allowed to execute code in those parts of memory, but this itself leads to a possible attack if the application isn't rigorous in validating data that is passed into a region of memory that is marked as being executable.
DEP is occasionally the cause of software problems. In most cases, these problems may be solved by disabling the DEP features. DEP can be turned off on a per-application basis, or turned off entirely for all non-essential Windows programs and services.
DEP configuration for the system is controlled through switches in the Boot.ini file. DEP can be configured by using the System dialog box in Control Panel.
The Boot.ini file settings are as follows: /noexecute= policy_level Note policy_level is defined as AlwaysOn, AlwaysOff, OptIn, or OptOut.
OptIn: This setting is the default configuration for Windows XP. On systems with processors that can implement hardware-enforced DEP, DEP is enabled by default for limited system binaries and programs that "opt-in." With this option, only Windows system binaries are covered by DEP by default.
OptOut: This setting is the default configuration for Windows 2003 SP1. DEP is enabled by default for all processes. A list of specific programs that should not have DEP applied can be entered using the System dialog box in Control Panel. Network administrators can use the Application Compatibility Toolkit to "opt-out" one or more programs from DEP protection. System compatibility fixes, or shims, for DEP do take effect. Also note that Windows silently disables DEP for certain executables, such as those packaged with ASPack.
AlwaysOn: This setting provides full DEP coverage for the whole system. All processes always run with DEP applied. The exceptions list to exempt specific programs from DEP protection is not available. System compatibility fixes for DEP do not take effect. Programs that have been opted-out by using the Application Compatibility Toolkit run with DEP applied.
AlwaysOff: This setting does not provide any DEP coverage for any part of the system, regardless of hardware DEP support. (except in Windows Vista Ultimate