DTR toggle wonky on Sol8-04/01 x86
I have been working with a few applications that toggle off and on DTR on /dev/ttyb very quickly. (specifically flipit & bottlerocket for X-10 home automation)
I have compiled successfully with linux (RH 7.0 on i386) , Solaris on an SS5 (Solaris 8 -01/01) - after modifying my running kernel with adb with a patch for the ZS driver, to allow rapid toggle of DTR)
The problem is, the system does not respond to DTR toggle like it should(quickly), but operation of a modem is fine with tip.
I have turned off the getty for /dev/ttyb with admintool.
There is many threads regarding the ZS & SE drivers with this type of behaviour, but there is no mention of contemporary Solaris X86 exhibiting the same problem.
I have a compiled this code on the sparcstation/x86 with different results.
#include <fcntl.h>
#include <termio.h>
#include <sys/time.h>
#define L 13
#define H 14
/* Global variable (just for this test) */
int port;
void outport(unsigned char x)
int bitset;
switch (x)
case L:
bitset = TIOCM_DTR;
ioctl(port, TIOCMBIS, &bitset);
break;
case H:
bitset = TIOCM_DTR;
ioctl(port, TIOCMBIC, &bitset);
break;
default :
printf("Invalid Status ...\n");
int main(int argc, char **argv)
struct timeval time;
int i;
if ((port = open("/dev/ttyb", O_RDWR | O_NDELAY | O_NOCTTY)) == -1)
printf("Unable to open /dev/ttyb/n");
exit(1);
/* NOTE: output to ttyb is inverted (H->L, L->H) */
for (i=0; i<1000; i++)
outport(H); /* init */
gettimeofday(&time, NULL); printf("H: %ld.%ld\n", time.tv_sec,
time.tv_usec);
outport(L);
gettimeofday(&time, NULL); printf("L: %ld.%ld\n", time.tv_sec,
time.tv_usec);
/* close(port); */
The sparcstation(with DTR patch) rapidly toggles DTR, while the X86 toggles seldom.
Help!
/Mark
hi Sivasubramanian,
as i'm on a vacation in San Francisco (i'm writing this on my Cingular 8525 Windows Pocket PC 5) I won't be able to take a look at the
report...(my email is jags_fl at yahoo dot com) but after u ran installation check tool did u look at the results? check for those 'Y' & 'N' as showed on following page:
http://www.sun.com/bigadmin/hcl/hcts/install_check.html
u would be able to see urself if any hardware is not compatible (at the end of installation check tool)...
- Jags Desai
Similar Messages
-
I have been working with a few applications that toggle off and on DTR on /dev/ttyb very quickly. (specifically flipit & bottlerocket for X-10 home automation)
I have compiled successfully with linux (RH 7.0 on i386) , Solaris on an SS5 (Solaris 8 -01/01) - after modifying my running
kernel with adb with a patch for the ZS driver, to allow rapid toggle of DTR)
The problem is, the system does not respond to DTR toggle like it should(quickly), but operation of a modem is fine with tip.
I have turned off the getty for /dev/ttyb with admintool.
There is many threads regarding the ZS & SE drivers with this type of behaviour, but there is no mention of contemporary Solaris X86 exhibiting the same problem.
I have a compiled this code on the sparcstation/x86 with different results.
#include <fcntl.h>
#include <termio.h>
#include <sys/time.h>
#define L 13
#define H 14
/* Global variable (just for this test) */
int port;
void outport(unsigned char x)
int bitset;
switch (x)
case L:
bitset = TIOCM_DTR;
ioctl(port, TIOCMBIS, &bitset);
break;
case H:
bitset = TIOCM_DTR;
ioctl(port, TIOCMBIC, &bitset);
break;
default :
printf("Invalid Status ...\n");
int main(int argc, char **argv)
struct timeval time;
int i;
if ((port = open("/dev/ttyb", O_RDWR | O_NDELAY | O_NOCTTY)) == -1)
printf("Unable to open /dev/ttyb/n");
exit(1);
/* NOTE: output to ttyb is inverted (H->L, L->H) */
for (i=0; i<1000; i++)
outport(H); /* init */
gettimeofday(&time, NULL);
printf("H: %ld.%ld\n", time.tv_sec,time.tv_usec);
outport(L);
gettimeofday(&time, NULL); printf("L:%ld.%ld\n",time.tv_sec,time.tv_usec);
/* close(port); */
The sparcstation(with DTR patch) rapidly toggles DTR, while the X86 toggles seldom.
Help!
/MarkIn Preferences->Appearance, see what the hot area display threshold is set to. It should be 97 or higher.
-
Sol8 x86 routing install problems
I've been banging my head against the virtual wall for a week over this one. I've installed Sol8 x86 on an e-machines 600 with a 40-gig drive (the OS is properly patched) and everything appears to be working fine, but I can't ping or traceroute to anywhere. The NIC has been swapped (and Solaris re-installed), the cable has been replaced with a known good cable, I'm getting activity lights on both sides of the cable, and my routing seems to be set up properly. Other machines (all NT) work just fine on this hub, so it's not an outside hardware or communications issue. The interface is configured properly with a netmask of 255.255.255.192, broadcast on x.x.x.63, and the routing tables show good routes (yes, I set up a default router in /etc). Today, I went ahead and re-installed everything from scratch, and still I get nothing - it's as if my system is on a network of one. I've come down to one of two possibilities: either Solaris isn't compatible with e-machines, or the ATA driver/patch for the 40 gig drives doesn't like handling communications. Any ideas, or has anyone else successfully installed Sol8 with the above configuration?
What is the NIC on an eMAchine? Is it on the HCL? What chip does it have?
-
3COM 3C905-TX NIC not working on Sol8 x86!
Hello all,
I am running an old HP Vectra VL8i 400 Mhz, 128MB ram, 8GB Maxtor IDE HDD,
3COM 3C905-TX NIC on Solaris 8 x86 (Intel Edition). I have been having HUGE
problems getting it to recognize any network interface. At first I had a
linksys LNE-TX100 NIC in it and after trying for days to get it to recognize
the NIC I gave up after finding that several other people had problems with
this NIC also. Thus, off a recommendation on sun's forums, I bought a 3COM
3C905-TX NIC. I installed the NIC today and verified its listed in the
'/boot/solaris/devicedb/master' file. It shows up as 'elxl' (those are L's,
not 1's I believe). I verified this in '/etc/driver_aliases'. Based upon
this and Sun's x86 HCL list which also lists my NIC I should have ZERO
problems.
I added my IP, hostname, and FQDN (dummy FQDN to stop sendmail's errors for
now until I put this box on a real network) to the /etc/hosts file. I then
added '/etc/hostname.elxl0' with my hostname. Next, I edited the
'/etc/netmasks' to include my network number and netmask.
Now, however, whenever I do an 'ifconfig -a', it only shows me 'lo0' the
local loopback and interestingly enough, the inet address for this interface
is 0.0.0.0. I can't ping this or do anything with it. This isn't the
problem though, the real problem is that I can't get it to bring the 'elxl0'
interface up. If I do a 'ifconfig elxl0 plumb' it gives me the error:
'ifconfig: plumb: elxl0: Bad file number'.
Also, on bootup the machine gives the following errors:
--- ifconfig: plumb: elxl0: Bad file number
--- Moving addresses from failed IPv4 interfaces: elxl0
--- Couldn't move, no alternative interface
--- in.rdisc: No interface up
I would REALLY appreciate ANY help on this matter as its incredibly
frustrating. Any advice is welcome...thanks!!
XiveXHi,
Thanks for your reply. Some cards are not supported by solaris 8.
Try this method.
Solaris 8 does not recognize these newer cards even though the chipsets are
well
known and have well tested, mature drivers in Solaris. This is just because the
vendor and device ID's are not in your /etc/driver_aliases file.
Step 1. Insert the 3COM NIC card in to the system.
Step 2: prtconf -v | grep pci
Example:
prtconf -v shows:
pci8086,7112
pci8086,7113
pci8086,5345
pci10b7,1000 <- 3com
Step 3. In file /etc/driver_aliases, look for the driver that matched the
chipset
on the card. One of them is elxl for the 3com chipset.
Example:
/etc/driver_aliases:
elx "pci10b7,5900"
elx "pci10b7,5950"
elxl "pci10b7,9000"
elxl "pci10b7,9001"
elxl "pci10b7,9050"
elxl "pci10b7,9055"
elxl "pci10b7,9056"
elxl "pci10b7,9004"
elxl "pci10b7,9005"
elxl "pci10b7,9006"
add elxl "pci10b7,1000"
Step 4. Add the vendor/ID that the Plug-and-Play BIOS startup message displayed
for this card like this: elxl "pci10b7,1000" This will support
the NIC
in Solaris.
Step 5. Add the following lines to support the card in Device Configuration
Assistant:
Example:
pci10b7,1000 pci10b7,1000 net pci elxl.bef "3COM 3C980B TX"
Add the entries in /boot/solaris/devicedb/master file, under PCI
devices
section
Step 6. Run "devlinks".
Step 7. Reboot the system with b -r option.
let me know the status.
Regards,
Senthilkumar
Developer Technical Support
http://www.sun.com/developers/support -
Error when starting DTR Console on NWDI 7.31
Hi Guys
When starting DTR console from command line on a Windows 2008 OS, im getting the following error
S:\usr\sap\NDI\SYS\global\com.sap.dtr.console>run
S:\usr\sap\NDI\SYS\global\com.sap.dtr.console>java -Dhttp.readtimeout=0 -cp S:\usr\sap\NDI\SYS\global\com.sap.dtr.console\sap.com~tc~dtr~console~all.jar;S:\usr\sap\NDI\SYS\global\com.sap.dtr.console\sap.com~tc~dtr~cmdlineappfwk~all.jar;S:\usr\sap\NDI\SYS\global\com.sap.dtr.console\antlr-runtime-3.0.1.jar com.sap.dtr.console.DTRConsoleApplication
Exception in thread "main" java.lang.RuntimeException: com.sap.dtr.cmdlinefwk.CommandLineException: Validation of the examples for the command "Discard" failed.
The example "discard -col -cip/collision/dce6250e4fd911dc81e400199905d653_3_b4c044e04fd511dccef000199905d653_b4c044d84fd511dca33b00199905d653_open_PredSucc" contains a command that is not valid against its specification.
at com.sap.dtr.console.DTRConsoleApplication.registerCommandSpecs(DTRConsoleApplication.java:207)
at com.sap.dtr.console.DTRConsoleApplication.initialize(DTRConsoleApplication.java:156)
at com.sap.dtr.console.DTRConsoleApplication.<init>(DTRConsoleApplication.java:137)
at com.sap.dtr.console.DTRConsoleApplication.main(DTRConsoleApplication.
java:311)
Caused by: com.sap.dtr.cmdlinefwk.CommandLineException: Validation of the examples for the command "Discard" failed.
The example "discard -col -cip /collision/dce6250e4fd911dc81e400199905d653_3_b4c044e04fd511dccef000199905d653_b4c044d84fd511dca33b00199905d653_open_PredSucc" contains a command that is not valid against its specification.
at com.sap.dtr.cmdlinefwk.CommandLineApplication.addCommandLineSpec(CommandLineApplication.java:115)
at com.sap.dtr.console.DTRConsoleApplication.registerCommandSpecs(DTRConsoleApplication.java:204)
... 3 more
Caused by: com.sap.dtr.cmdlinefwk.CommandNotSupportedException: Command 'discard' is not supported
at com.sap.dtr.cmdlinefwk.support.parser.DefaultCommandLineParser.parse(DefaultCommandLineParser.java:57)
at com.sap.dtr.cmdlinefwk.CommandLineApplication.addCommandLineSpec(CommandLineApplication.java:107)
... 4 more
Any idea what is missing? Im seeing the command line its showing S:\usr\sap\NDI\SYS\global\com.sap.dtr.console\antlr-runtime-3.0.1.jar, but this file is not present
Thesefiles are at OS level
Regards!Hi,
i have also problem with launching DTR console. I followed this article for enabling it:
Starting Command Line Tools - Using the Development and Production Infrastructure - SAP Library
But when I try to start the console via Run, I receive this error:
eclipse.buildId=unknown
java.version=1.6.0_38
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en
Framework arguments: -application com.sap.di.cltools.dtrshell
Command-line arguments: -application com.sap.di.cltools.dtrshell -data D:\IDE\IDE7.31SP12\eclipse\workspace/../runtime-New_configuration(2) -dev file:D:/IDE/IDE7.31SP12/eclipse/workspace/.metadata/.plugins/org.eclipse.pde.core/CBS Command Line Tool/dev.properties -os win32 -ws win32 -arch x86
Error
Wed Oct 29 15:53:05 EET 2014
Application error
java.lang.NullPointerException
at com.tssap.dtr.client.commandline.DTRShell.main(DTRShell.java:86)
at com.sap.di.cltools.internal.DtrShell.start(DtrShell.java:32)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
at org.eclipse.equinox.launcher.Main.main(Main.java:1287)
If you have solution to this problem, please give me advice.
Thanks! -
Installation problem sun solaris 9 x86 on intel
I am trying to install sun solaris 9 x86 intel platform edition on my home pc hp e-vectra, configuration is PIII 800 Mhz, 10 GB HDD, 128 MB Ram, 17" color monitor, but it giving me following error :-
BooT Panic: trap type e, error 0 at 117499
Cr0: 800000011, cr1: 4, cr3: 17e000
Eax: 0, ebx: 7e2c, ecx: 0 edx: 16e350
Es: fffffffe, edi: 17dfe0, ebp: 7e40, esp: 7e20
Entering boot debugger:
Please help me, how can I install sun solaris 9 x86 on my HP E-Vectra PC.
Kalpesh MehtaI had similar problems several months ago. I suspect this happens when host pc does not have floppy drive(or bios somehow misreports it) as it was in my case. Solaris 8 seems to work fine in the same environment, so I keep using it for now. Possible workaround might be to use DCA from Solaris 8: Installation of Sol9 started just fine after I entered Sol8 DCA and asked it to boot from Sol9 CD.
Hope this problem will be fixed in subsequent Sol9 releases.
Victor -
Solaris 10/X86 install appears to have destroyed my display.
Hello folks -
I'm new here, I searched and did not find anything that matched so I'm posting. If I'm asking about something previously covered, please be patient, I'll learn.
I am running an Asus A7N8 Deluxe motherboard with an Athlon 2800+, standard ATA/133 drives and an Nvidia 6800 AGP supplied by PNY. My display is a Viewsonic VA2012wb, which I've since learned is only available at a well-known warehouse membership store.
I've been using this setup under XP for some months now, and yesterday I decided to try and install Sol10/X86 again now that some new drivers are available that support my onboard LAN. Nothing untoward happened during the install (I'm very familiar with the process on Sparc hardware), and I was asked to reboot so I could start installing CD2.
Suddenly, no display on boot. Troubleshooting ensued, and I found that I was able to get the monitor to display if I connected the VGA cable instead of the DVI interface I've successfully used all this time.
Subsequent troubleshooting included:
1. Changing out the 6800 with a 6200 I had on hand.
2. Booting to XP to see if the Nvidia Twinview stuff had become confused - The Nvidia software behaved as if there was nothing available on the DVI input, so many menus did not even appear.
3. Checking with Viewsonic to make sure that I was clear on how the monitor selects inputs. It's largely automatic, but hitting the '2' key on the front panel forces a rescan of the analog and digital inputs.
4. Substituting another display on this workstation, with all cables unchanged, so I could verify that the DVI output on my video card still worked. Tested fine.
5. Moving the affected display to another workstation, to see if it was capable of functioning on the DVI input from a different machine. It was not, test failed.
6. Unplugging everything and letting it sit for over an hour (while I fumed) - test failed.
7. Returned the affected display to Costco today, for a spanky new one. It worked great on DVI with existing hardware (and under XP) this afternoon, so I decided to re-start my Solaris install.
Lather, rinse, repeat, or so I was about to find out....
After I was asked to reboot from CD1, my display died again.
Just like yesterday, it's currently working fine on the VGA input/dead to the world on DVI, and just like yesterday, everything was fine until the first reboot after the Solaris CD1. I repeated the most pertinent aspects of my prior diagnostic steps, and then I went out to the back porch to curse and throw tools until I felt better.
I cannot find a hardware reset button for the display, and an old friend of mine reports that he had a similar issue under Solaris 8/X86 in which he ended up blowing up a CRT. The Sol8 installer was overdriving the monitor.
That said, I don't think that the DVI interface is able to 'overdrive' a monitor, and that confuses me more deeply. I know that if I (re)abuse the return policy of this warehouse store once more tomorrow and get a new display it will fix the problem, but I'm hoping that I can fix this in house!
I refuse to believe that Solaris is actually frying the DVI input on my display, but I do have clear evidence that it the installer is a destructive force, at least with Nvidia cards and a VA2012wb. I'm seeing some similar threads on the Linux forums, some mentioning the part number of my display in specific, but no clear resolutions yet.
Any thoughts?
- EliOK, well... I did a restart, invoking the 'option' command, and the Lion Recovery partition did not show up, so I went ahead and booted back into SL, wherein I was given a 'The disk you inserted was not readable by this computer' with a choice of ejecting, ignoring, or initializing. I chose Ignore, and the drive now just shows up in disk utility as 'media' with no opportunity to interact with it.
I had the presence of mind to make a Lion DVD before I installed, so I booted with that, and it too was unable to interact with the drive.
Given the degraded state of this drive, I have no reason to suspect that entering target disk mode and mounting to my MBP would bear any fruit... looks like this sucker is beyond hope. Yay...
I will not be re-installing Lion until at least .2 comes out at this point.. I can't afford a wasted day like this again. -
Solaris x86 on Compaq DL360 (P21) server
I am having issues installing this OS on the server in the title... it is a DL360 with Dual PIII 998 processors and 1.4G RAM.
I setup the RAID controller at statup to use RAID1 with 2 x 36G drives.... and then boot from the Solaris Disk 1 (no the installer disk)...
I am using the RAID controller driver supplied from Compaq for Solaris 8 and at the first stage it successfully is added during the installation process....
The process goes through as per expected, setup network, setup drive layout and even install required OS modules.. then it happens....
... the request to insert the disk holding file CPQARY2 pops up, disk is inserted but the message 'file cannot be found on disk' is returned....
Silly thing is that the system has already used this driver from this disk to load the HDD RAID conntroller info into memory... it even installs to the disks with no problems....
Is this an issue because the drivers are for Sol8 and not 9??... and does anyone know where and if I can get the drivers for 9??.. they are not on the website for this server model....did you make any experiance regarding Solaris 10 X86 ?No, but...
Unfortunately there is no Solaris 10 driver for the
built in SmartArray of the DL360 (P21) available.... I expect that the same workaround is OK for Solaris 10, that is,
rename the DU/sol_28 directory to DU/sol_210 on HP's driver
update floppy. -
How To: Mylex 170 RAID + Solaris 8 x86
Hi,
My hardware:
1. Intel SAI2 Server Board
http://developer.intel.com/design/servers/sai2/
2. Mylex 170 RAID Adapter
http://www.mylex.com/products/acceleraid/datasheets/aclrd170.html
it always tell me "no disk found" when install Sol8 x86 (10/01). i already try to install from Software #1 but also don't work. i also try the Solaris 7 driver from Mylex website
http://www.mylex.com/support/productgd/index.html
it's don't work too. Anyone can help me? 1,000,000 Thanks
ChrisHello Michael,
thanks for the information.
There is no support for the Promise Ultra 133 IDE controller listed.
Also, searching the internet for a private developed driver was not
successful.
Anyway, I have tried to make a test installation on a hard disk
connected to the primary IDE controller and I detected a lot of
further installation problems with my equipments because of
missing or not properly identified drivers.
So I think I have to make further investigations on concepts
how to get Solaris 8 run in the best way.
Thanks again for your help,
Thomas -
...another problem with NIC's on x86:
according to pcelx(7D), 3c589C is supported by this driver under pcic, but prtconf doesn't show
any children under the controller. I've also tried:
1. 3c589D, it's not recognized as well.
2. pctc driver, although I got it to compile and eventually load (this driver requires "cs" which no longer ships with Sol10, so I've used the driver from Sol8), no luck.
3. initpcic driver (along with the all the steps from README ;), again, the driver loaded, but none of the 3com Etherlink III cards were being recognized by the system.
However, both cards work w/out issues on RH AS4-beta (2.6.5 kernel) which is installed on the same labtop (IBM T20).
Any suggestions, besides spending $$ @ http://www.lynnsoft.com, are appreciated.
PS: At least I got ext2fs work on Solaris 10 |-)
Patch posted @ http://www.webservertalk.com/message284284.htmls10 x86, 3com pcmcia 3c589 can not plumb.
Try initpcic
# pkgadd -d initpcic-1.7.pkg
The following packages are available:
1 XIGSpcic Xi Graphics PCIC adapter init driver
(i386) 1.7
Select package(s) you wish to process (or 'all' to process
all packages). (default: all) [?,??,q]: all
Installing Xi Graphics PCIC adapter init driver as <XIGSpcic>
## Executing preinstall script.
### Checking SunOS version
### ERROR: You must have Solaris verson 5.6, 5.7, 5.8 or 5.9
pkgadd: ERROR: preinstall script did not complete successfully
Installation of <XIGSpcic> failed.
Xi Graphics PCMCIA patch
Additional PC Card (PCMCIA) adapter support for Solaris 6, 7 and 8 x86. This package tries to work around a problem in the Solaris bus enumerator boot code. While it detects that a PCMCIA bridge is present, it does not properly initialize the bridge, and therefore it is not available when the system boots. What this package does is to force the bridge into an ISA only mode so that the bridge is usable after boot. Of course this means that CardBus cards cannot be used with this package. This package does not provide support for any of the Solaris Card specific drivers, so if your card is not on the Solaris HCL, it still will not work with this patch.
So could u share the solve process in detail?
Thanks. -
DTR component not fully functional
Hi all,
We recently tried to change the DTR repository properties file, according to SAP NOTE: 1001509.
After performing the process mentioned in this note, we noticed this particular repository.properties file has the wrong content (I downloaded the file from online NWDI - DTR and this caused the file to include HTML Tags and replacing the Key/Value pairings with a different keyset).
This caused the DTR to not fully function; for example we cannot checking any activities anymore. Whenever we try to restart the DTR application in the Web AS, we get a NumberformatException on multiple Key/Values in this repository.properties file.
At this moment, we are not capable of changing this repository.properties file since we cannot checkin activities.
We also tried to replace the repository.properties file on UX, but we now believe (since this file is also version controlled) it is only contained in the NWDI Database.
I've included the error trace DTR pushes out;the current repository.properties file (wrong one) and the correct repository.properties we wish to have in place.
This is a very challenging topic for our teams to solve.
Anybody up for an idea?
Thanks,
WesleyThe great thing about most BlackBerry phones is their removable battery. Anytime something goes wonky with your phone, doing a battery pull should be your first course of action. When you do a proper battery pull, many unnecessary temporary files get deleted and this helps your phone run smoother and ofter quicker. To do a proper battery pull, make sure your phone is powered on then remove the battery and replace it a few seconds later and wait for your phone to boot up. Don't worry, you won't lose any personal data. Many phones from competing manufacturers don't have this feature so be happy that you can correct many issues using this simple technique.
I can answer your question about voicemails right away. Your carrier's voicemail number should be programmed on the SIM card. To access it, simply press and hold the #1 on your phone for a second or two. That should direct you right to your voicemail box where you'll be prompted to enter your password. If you press and hold the #1 on your keypad and you're not directed to your voicemail box, contact your carrier to obtain the number as well as instructions on how to enter it in your phone.
Try the battery pull and report back with your results. Cheers.
- If my response has helped you, please click "Options" beside my post and mark it as solved. Clicking the "thumbs up" icon near the bottom of my response would also be appreciated. -
Preview toggle in Lighting Effects crashes CS6 Beta
I'm on Win7x64 Ultimate, 8GB RAM, GTX260-896 MB VRAM, latest drivers (296.10 released 13 Mar 2012).
I can use, and save the results of using, Lighting Effects (only relatively small (< 4 MB) flat 16-bit TIFFs and flat JPEGs tried so far) with no apparent difficulties. However, any but the most limited use (not exceededing three on average - applied as a continuous toggle) of the Preview button invariably causes CS6 Beta to crash. This is the error message generated by Windows:
"Adobe Photoshop CS6 has stopprd working
Windows can check online for a solution to the problem.
> Check online for a solution and close the program
> Close the program
Problem signature:
Problem Event Name: APPCRASH
Application Name: Photoshop.exe
Application Version: 13.0.0.0
Application Timestamp: 4f551de1
Fault Module Name: MSVCR100.dll
Fault Module Version: 10.0.40219.1
Fault Module Timestamp: 4d5f034a
Exception Code: c0000005
Exception Offset: 000000000003c145
OS Version: 6.1.7601.2.1.0.2561
Locale ID: 3081
Additional Information 1: 651f
Additional Information 2: 651f7c834e2a84316ab24fc8b52f3652
Additional Information 3: b579
Additional Information 4: b579ee6e46c3f5067c4f88b754331731"
This happens with all Basic, Normal and Advanced Drawing Modes in the "Advanced Settings" tab of the Graphics Processor Settings dialog in the Performance Tab of Preferences. Having ticked "Use Graphics Processor" and then clicked the "Advanced Settings" button, CS6 Beta tells me that Open CL is an available option (which is consistent with the release notes for the latest drivers) but because my graphics card is now about 4 or 5 years old, I have my doubts and so my testing has included not selecting that option. However all tests have selected "Use Graphics Processor to Accelerate Computation".
I was hoping that someone in the Adobe development team might be able to have a look at this issue for me? Please?Continuing to experience this problem - this time applying the filter to a Smart Object layer in an 84 MB PSD file - crash occuring after just 3 toggles of the Preview button.
Here is the summary and full report generated by NirSoft's AppCrashView (ver 1.11) program. It takes its info from the Windows WERs.
Can anyone else reproduce this behaviour ?
"Process File : Photoshop.exe
Event Name : Stopped working
Event Time : 15/04/2012 11:14:50 AM
User Name : ash1
Exception Code : 0xc000041d
Exception Offset : 0x0003bfa0
Fault Module Name : MSVCR100.dll
Fault Module Version: 10.0.40219.1
Process Path : C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\Photoshop.exe
Report File Size : 24,848
Report File Path : C:\Users\ash1\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_Photoshop.exe_1b 8b58bdaa548d6e15719b3bab048eabd76d4c_0bc93b0e\Report.wer
==================================================
Version=1
EventType=APPCRASH
EventTime=129789260908135188
ReportType=2
Consent=1
ReportIdentifier=65b7a714-8698-11e1-8101-e0cb4e0158b2
IntegratorReportIdentifier=65b7a713-8698-11e1-8101-e0cb4e0158b2
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=Photoshop.exe
Sig[1].Name=Application Version
Sig[1].Value=13.0.0.0
Sig[2].Name=Application Timestamp
Sig[2].Value=4f551de1
Sig[3].Name=Fault Module Name
Sig[3].Value=MSVCR100.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=10.0.40219.1
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=4d5f034a
Sig[6].Name=Exception Code
Sig[6].Value=c000041d
Sig[7].Name=Exception Offset
Sig[7].Value=000000000003bfa0
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.256.1
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=3081
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=5bd8
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=5bd849b86497feb978496e03527c669c
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=962e
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=962e959bbf98fe94a144f2382e80f5ea
UI[2]=C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\Photoshop.exe
UI[3]=Adobe Photoshop CS6 has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\Photoshop.exe
LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\Windows\system32\kernel32.dll
LoadedModule[3]=C:\Windows\system32\KERNELBASE.dll
LoadedModule[4]=C:\Windows\WinSxS\amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.760 1.17514_none_2b24536c71ed437a\gdiplus.dll
LoadedModule[5]=C:\Windows\system32\msvcrt.dll
LoadedModule[6]=C:\Windows\system32\USER32.dll
LoadedModule[7]=C:\Windows\system32\GDI32.dll
LoadedModule[8]=C:\Windows\system32\LPK.dll
LoadedModule[9]=C:\Windows\system32\USP10.dll
LoadedModule[10]=C:\Windows\system32\ole32.dll
LoadedModule[11]=C:\Windows\system32\RPCRT4.dll
LoadedModule[12]=C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\ExtendScript.dll
LoadedModule[13]=C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\MSVCR100.dll
LoadedModule[14]=C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\ScCore.dll
LoadedModule[15]=C:\Windows\system32\SHELL32.dll
LoadedModule[16]=C:\Windows\system32\SHLWAPI.dll
LoadedModule[17]=C:\Windows\system32\mscms.dll
LoadedModule[18]=C:\Windows\system32\USERENV.dll
LoadedModule[19]=C:\Windows\system32\profapi.dll
LoadedModule[20]=C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\MSVCP100.dll
LoadedModule[21]=C:\Windows\system32\OPENGL32.dll
LoadedModule[22]=C:\Windows\system32\ADVAPI32.dll
LoadedModule[23]=C:\Windows\SYSTEM32\sechost.dll
LoadedModule[24]=C:\Windows\system32\GLU32.dll
LoadedModule[25]=C:\Windows\system32\DDRAW.dll
LoadedModule[26]=C:\Windows\system32\DCIMAN32.dll
LoadedModule[27]=C:\Windows\system32\SETUPAPI.dll
LoadedModule[28]=C:\Windows\system32\CFGMGR32.dll
LoadedModule[29]=C:\Windows\system32\OLEAUT32.dll
LoadedModule[30]=C:\Windows\system32\DEVOBJ.dll
LoadedModule[31]=C:\Windows\system32\dwmapi.dll
LoadedModule[32]=C:\Windows\system32\WS2_32.dll
LoadedModule[33]=C:\Windows\system32\NSI.dll
LoadedModule[34]=C:\Windows\system32\WINSPOOL.DRV
LoadedModule[35]=C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\cg.dll
LoadedModule[36]=C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\cgGL.dll
LoadedModule[37]=C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\adbeape.dll
LoadedModule[38]=C:\Windows\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.616 1_none_08e61857a83bc251\MSVCR90.dll
LoadedModule[39]=C:\Windows\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.616 1_none_08e61857a83bc251\MSVCP90.dll
LoadedModule[40]=C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\AdobeOwl.dll
LoadedModule[41]=C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\ahclient.dll
LoadedModule[42]=C:\Windows\system32\WININET.dll
LoadedModule[43]=C:\Windows\system32\Normaliz.dll
LoadedModule[44]=C:\Windows\system32\iertutil.dll
LoadedModule[45]=C:\Windows\system32\urlmon.dll
LoadedModule[46]=C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\amtlib.dll
LoadedModule[47]=C:\Windows\system32\WINHTTP.dll
LoadedModule[48]=C:\Windows\system32\webio.dll
LoadedModule[49]=C:\Windows\system32\IPHLPAPI.DLL
LoadedModule[50]=C:\Windows\system32\WINNSI.DLL
LoadedModule[51]=C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\AXEDOMCore.dll
LoadedModule[52]=C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\MPS.dll
LoadedModule[53]=C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\PlugPlug.dll
LoadedModule[54]=C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\tbb.dll
LoadedModule[55]=C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\AdobeLinguistic.dll
LoadedModule[56]=C:\Windows\system32\PSAPI.DLL
LoadedModule[57]=C:\Windows\system32\IMM32.DLL
LoadedModule[58]=C:\Windows\system32\MSCTF.dll
LoadedModule[59]=C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\tbbmalloc.dll
LoadedModule[60]=C:\Windows\system32\VERSION.dll
LoadedModule[61]=C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1d f_6.0.7601.17514_none_fa396087175ac9ac\comctl32.dll
LoadedModule[62]=C:\Windows\system32\CRYPTBASE.dll
LoadedModule[63]=C:\Windows\system32\uxtheme.dll
LoadedModule[64]=C:\Windows\system32\STI.DLL
LoadedModule[65]=C:\Windows\system32\CLBCatQ.DLL
LoadedModule[66]=C:\Windows\system32\CRYPTSP.dll
LoadedModule[67]=C:\Windows\system32\rsaenh.dll
LoadedModule[68]=C:\Windows\system32\RpcRtRemote.dll
LoadedModule[69]=C:\Windows\system32\wiatrace.dll
LoadedModule[70]=C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\Photoshop.dll
LoadedModule[71]=C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\PSViews.dll
LoadedModule[72]=C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\PSArt.dll
LoadedModule[73]=C:\Windows\system32\c_g18030.dll
LoadedModule[74]=C:\Windows\system32\MSIMG32.dll
LoadedModule[75]=C:\Windows\system32\apphelp.dll
LoadedModule[76]=C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\Required\Plug-Ins\Extensions\FastCore.8BX
LoadedModule[77]=C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\Required\Plug-Ins\Extensions\MMXCore.8BX
LoadedModule[78]=C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\libmmd.dll
LoadedModule[79]=C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\Required\Plug-Ins\Extensions\MultiProcessor Support.8BX
LoadedModule[80]=C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\PLUGIN.dll
LoadedModule[81]=C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\Required\Plug-Ins\ADM\ADMPlugin.apl
LoadedModule[82]=C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\AdobeXMP.dll
LoadedModule[83]=C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\Required\Plug-Ins\File Formats\Dicom.8BI
LoadedModule[84]=C:\Windows\system32\WSOCK32.dll
LoadedModule[85]=C:\Windows\system32\NETAPI32.dll
LoadedModule[86]=C:\Windows\system32\netutils.dll
LoadedModule[87]=C:\Windows\system32\srvcli.dll
LoadedModule[88]=C:\Windows\system32\wkscli.dll
LoadedModule[89]=C:\Program Files\Common Files\Adobe\Plug-Ins\CS6\File Formats\Camera Raw.8bi
LoadedModule[90]=C:\Windows\system32\wbem\wbemprox.dll
LoadedModule[91]=C:\Windows\system32\wbemcomn.dll
LoadedModule[92]=C:\Windows\system32\wbem\wbemsvc.dll
LoadedModule[93]=C:\Windows\system32\wbem\fastprox.dll
LoadedModule[94]=C:\Windows\system32\NTDSAPI.dll
LoadedModule[95]=C:\Windows\system32\ntmarta.dll
LoadedModule[96]=C:\Windows\system32\WLDAP32.dll
LoadedModule[97]=C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\BIB.dll
LoadedModule[98]=C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\BIBUtils.dll
LoadedModule[99]=C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\ACE.dll
LoadedModule[100]=C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\AGM.dll
LoadedModule[101]=C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\CoolType.dll
LoadedModule[102]=C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\AXE8SharedExpat.dll
LoadedModule[103]=C:\Windows\system32\icm32.dll
LoadedModule[104]=C:\Windows\System32\msxml6.dll
LoadedModule[105]=C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\AdobePIP.dll
LoadedModule[106]=C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\LogSession.dll
LoadedModule[107]=C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\WRServices.dll
LoadedModule[108]=C:\Program Files\Common Files\Adobe\Linguistics\6.0\Providers\Plugins2\AdobeHunspellPlugin\AdobeHunspellPlugin.dl l
LoadedModule[109]=C:\Program Files\Common Files\Adobe\Linguistics\6.0\Providers\Plugins2\WRLiloPlugin1.3\WRLiloPlugin.dll
LoadedModule[110]=C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\Required\Plug-Ins\Extensions\ScriptingSupport.8li
LoadedModule[111]=C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\ScriptUIFlex.dll
LoadedModule[112]=C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\adobe_caps.dll
LoadedModule[113]=C:\Windows\system32\WindowsCodecs.dll
LoadedModule[114]=C:\Windows\system32\WTSAPI32.dll
LoadedModule[115]=C:\Windows\system32\WINSTA.dll
LoadedModule[116]=C:\Windows\system32\EhStorShell.dll
LoadedModule[117]=C:\Windows\system32\PROPSYS.dll
LoadedModule[118]=C:\Windows\System32\cscui.dll
LoadedModule[119]=C:\Windows\System32\CSCDLL.dll
LoadedModule[120]=C:\Windows\system32\CSCAPI.dll
LoadedModule[121]=C:\Windows\system32\ntshrui.dll
LoadedModule[122]=C:\Windows\system32\slc.dll
LoadedModule[123]=C:\Program Files\Common Files\Adobe\APE\3.3\adbeapecore.dll
LoadedModule[124]=C:\Windows\system32\SXS.DLL
LoadedModule[125]=C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\aif_core.dll
LoadedModule[126]=C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\aif_ogl.dll
LoadedModule[127]=C:\Windows\system32\nvoglv64.DLL
LoadedModule[128]=C:\Windows\system32\WINTRUST.dll
LoadedModule[129]=C:\Windows\system32\CRYPT32.dll
LoadedModule[130]=C:\Windows\system32\MSASN1.dll
LoadedModule[131]=C:\Program Files\Common Files\Adobe\APE\3.3\adbeapeengine.dll
LoadedModule[132]=C:\Windows\system32\OLEACC.dll
LoadedModule[133]=C:\Windows\system32\COMDLG32.dll
LoadedModule[134]=C:\Windows\system32\WINMM.dll
LoadedModule[135]=C:\Windows\system32\msi.dll
LoadedModule[136]=C:\Windows\system32\DSOUND.dll
LoadedModule[137]=C:\Windows\system32\POWRPROF.dll
LoadedModule[138]=C:\Windows\system32\DNSAPI.dll
LoadedModule[139]=C:\Windows\system32\dbghelp.dll
LoadedModule[140]=C:\Windows\system32\mlang.dll
LoadedModule[141]=C:\Windows\system32\Secur32.dll
LoadedModule[142]=C:\Windows\system32\SSPICLI.DLL
LoadedModule[143]=C:\Windows\system32\credssp.dll
LoadedModule[144]=C:\Windows\system32\schannel.DLL
LoadedModule[145]=C:\Windows\system32\MMDevAPI.DLL
LoadedModule[146]=C:\Windows\system32\wdmaud.drv
LoadedModule[147]=C:\Windows\system32\ksuser.dll
LoadedModule[148]=C:\Windows\system32\AVRT.dll
LoadedModule[149]=C:\Windows\system32\AUDIOSES.DLL
LoadedModule[150]=C:\Windows\system32\msacm32.drv
LoadedModule[151]=C:\Windows\system32\MSACM32.dll
LoadedModule[152]=C:\Windows\system32\midimap.dll
LoadedModule[153]=C:\Windows\system32\mswsock.dll
LoadedModule[154]=C:\Windows\System32\wshtcpip.dll
LoadedModule[155]=C:\Windows\System32\wship6.dll
LoadedModule[156]=C:\Program Files (x86)\Common Files\Adobe\CS6ServiceManager\lib\ServiceManager-Launcher_x64.dll
LoadedModule[157]=C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\updaternotifications.dll
LoadedModule[158]=C:\Windows\system32\taskschd.dll
LoadedModule[159]=C:\Windows\system32\wpdshext.dll
LoadedModule[160]=C:\Windows\System32\shdocvw.dll
LoadedModule[161]=C:\Windows\System32\ieframe.dll
LoadedModule[162]=C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\data_flow.dll
LoadedModule[163]=C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\image_runtime.dll
LoadedModule[164]=C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\image_flow.dll
LoadedModule[165]=C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\Required\Plug-Ins\3D Engines\Photoshop3DEngine.8BI
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Adobe Photoshop CS6
AppPath=C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\Photoshop.exe" -
Error while switching between DC, DTR & web dynpro perspectives
Hi,
I am facing the following error while switching between DC, DTR & web dynpro perspectives.
A SWT error has occured.
It is recommended to exit the workbench.
Subsequent errors may happen and may terminate the workbench without warning.
See error log for more details.
Exit workspace?
When I click on 'Ok' and check out the log file....
!SESSION Nov 08, 2006 19:02:46.730 -
java.version=1.4.2_12
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments: -os win32 -ws win32 -arch x86 -feature com.sap.java.ide C:\j2sdk\bin\javaw.exe
-Xmx512m
-Xms128m
-XX:PermSize=32m
-XX:MaxPermSize=128m
-DallUserDir='C:\Documents and Settings\All Users\Application Data'
-cp C:\Program Files\SAP\IDE\IDE70\eclipse\SapStartup.jar com.sap.ide.eclipse.startup.Main
-os win32
-ws win32
-arch x86
-feature com.sap.java.ide
-showsplash C:\Program Files\SAP\IDE\IDE70\eclipse\SapIde.exe -showsplash 600 -data C:\Documents and Settings\rajabhog\Documents\SAP\workspace -install file:C:/Program Files/SAP/IDE/IDE70/eclipse/
!ENTRY Startup 1 0 Nov 08, 2006 19:02:46.730
!MESSAGE Sap NetWeaver Developer Studio - Unknown Sap Internal Installation
!SESSION -
!ENTRY org.eclipse.core.launcher 4 0 Nov 08, 2006 19:03:03.734
!MESSAGE Exception launching the Eclipse Platform:
!STACK
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.ide.eclipse.startup.Main.basicRun(Main.java:291)
at com.sap.ide.eclipse.startup.Main.run(Main.java:789)
at com.sap.ide.eclipse.startup.Main.main(Main.java:607)
Caused by: java.lang.reflect.InvocationTargetException
at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:861)
at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
... 7 more
Caused by: org.eclipse.swt.SWTError: Item not added
at org.eclipse.swt.SWT.error(SWT.java:2356)
at org.eclipse.swt.SWT.error(SWT.java:2260)
at org.eclipse.swt.widgets.Widget.error(Widget.java:385)
at org.eclipse.swt.widgets.Menu.createItem(Menu.java:464)
at org.eclipse.swt.widgets.MenuItem.<init>(MenuItem.java:118)
at org.eclipse.jface.action.Separator.fill(Separator.java:48)
at org.eclipse.jface.action.MenuManager.update(MenuManager.java:555)
at org.eclipse.jface.action.MenuManager.update(MenuManager.java:456)
at org.eclipse.jface.action.MenuManager.fill(MenuManager.java:209)
at org.eclipse.jface.action.MenuManager.update(MenuManager.java:555)
at org.eclipse.jface.action.MenuManager.update(MenuManager.java:456)
at org.eclipse.jface.action.MenuManager.createMenuBar(MenuManager.java:146)
at org.eclipse.jface.window.ApplicationWindow.configureShell(ApplicationWindow.java:244)
at org.eclipse.ui.internal.WorkbenchWindow.configureShell(WorkbenchWindow.java:578)
at org.eclipse.jface.window.Window.createShell(Window.java:350)
at org.eclipse.jface.window.Window.create(Window.java:301)
at org.eclipse.ui.internal.Workbench.restoreState(Workbench.java:1258)
at org.eclipse.ui.internal.Workbench.access$10(Workbench.java:1223)
at org.eclipse.ui.internal.Workbench$12.run(Workbench.java:1141)
at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:1006)
at org.eclipse.core.runtime.Platform.run(Platform.java:413)
at org.eclipse.ui.internal.Workbench.openPreviousWorkbenchState(Workbench.java:1093)
at org.eclipse.ui.internal.Workbench.init(Workbench.java:870)
at org.eclipse.ui.internal.Workbench.run(Workbench.java:1373)
at com.tssap.util.startup.WBLauncher.run(WBLauncher.java:79)
at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858)
... 8 more
Please help me out...
As I have to fix this issue as early as possible.
Thanks & Regards,
RajPost your question in the SAP NetWeaver Technology Platform. It don't think it's JDI related...
-
I am trying to install SOL8 on Sparcststion 5,with two harddrives one of ~4gb and other 700mb by using wizard and selecting custom install and after all the files have been installed when the computer is rebooted it gives an error saying bootblk not found.
The boot disk is the 4gb one.can anyone please let me know how to go about it.
thanksWhat solaris 8 release are you using?
i810 video support is available by installing patches 110959-01 and
109401-06, available for download here:
http://access1.sun.com/patch.public/cgi-bin/readme2html.cgi?patch=110959&type=unb
http://access1.sun.com/patch.public/cgi-bin/readme2html.cgi?patch=109401&type=unb
Both patches were released mid-february 2001, so they are probably not included in the
solaris 8 1/2001 (or earlier) release!
Can you try to install using the "Software 1 of 2" cdrom, using the "Interactive" installation,
and at the video card / mouse / keyboard configuration screen just select the "bypass"
option. The installation continues in text mode and you should be able to complete the
installation.
Once solaris 8 x86 is installed and running (still in text mode), make sure that both of the
above mentioned patches are installed.
Login as user "root" and run "kdmconfig" to configure you i810 video hardware, mouse and
keyboard. Once the video card works OK, you can enable the GUI desktop login
using "/usr/dt/bin/dtconfig -e". -
ETA for Solaris x86-64 11g(R2)?
Does anyone have a contact that has any knowledge of what platforms are truly being supported for the 11gR2 release?
I'm having great difficulty getting an answer for Solaris x86-64 from our Oracle reps.
Thanks,
Bryanhamcdc wrote:
For (as long as I can remember) Oracle releases have toggled in terms of "platform priority" between
depending on the mood of the day...Solaris x86 doesn't strike me as particularly strategic from Oracle's perspectiveAnd that's fine Connor. We are running "big iron" (16 cores on one of the servers should qualify), although now in the x64 format instead of the overpriced Sparc versions we have phased out, after being told by Oracle that the planned to support the platform going forward.
However, either Oracle is going to support this platform, as metalink shows but on which they have not delivered, or not. If they are dropping it, other than support what exists, we won't be happy, but at least we can make plans for the future. This is all we have:
bq. Certify - Additional Info Oracle Database - Enterprise Edition Version 11gR1 64-bit On Sun Solaris x86-64 (64-bit) \\ Operating System: Sun Solaris x86-64 (64-bit) Version 10 \\ Oracle Database - Enterprise Edition Version 11gR1 64-bit \\ N/A Version N/A \\ Status: Projected \\ Product Version Note: \\ None available for this product. \\ Certification Note: \\ Schedule to be announced. \\ NOTE: This is the most current and accurate information. Do not log Service Requests to Support for additional information. When the date is known this note will be updated. \\ Certify Administrator - 2008
They owe us, the customers an honest answer and timeframe. I think we've been more than patient.
Bryan
Maybe you are looking for
-
PDFMaker cannot locate the Adobe PDF Printer's printer driver. Please reinstall Adobe Acrobat 9.0. I keep getting this message when I am trying to convert a file to pdf. There is not an Adobe PDF listed in my printers. I have tried to repair the inst
-
Pse 11 organiser view screen background colour
Am I able to change the background colour of the view screen in PSE 11 organiser? The current background is grey, which isn't a great colour to optimise viewing images. Black would be better.
-
Pages background color customization for poster template?
HOw can I customize the color of the background on the template poster on pages for iPad? It is normally blue and I would like to change it.
-
Editable cell in ALV OO with F4 Help
Hi Abapers, i have an ALV with an editable cell wich an F4 help is available on it. When clicking on the F4 button i'm getting the list of possible values but when choosing a value it is not updating the alv cell. (F4 help is on a Z* field wich i cre
-
Starting this morning, iMac with OSX Lion no longer playing sound in Mail program as messages are Sent