Win2k DB service.

Hi Folks,
I want to alter the behavior of the Win2K DB service so that when I start the DB service (I have it set to manual) it does not automatically start the DB.
I have looked into modifying the -STARTTYPE parameter via the ORADIM utility and the -EDIT function but that does not seem to work.
I would appreciate any suggestions you might have.
Thank you - Simon.

Simon,
You might try setting the following registry key to TRUE:
HKLM\Software\ORACLE\HOME0\ORA_<ServiceName>_AUTOSTART
where
<ServiceName> is your Oracle service name.
If you have multiple Oracle homes you would need to set
the key under the appropriate HOME_X entry (I have assumed this to be HOME0 above).
Hope this helps.
Kailash.

Similar Messages

Win2k Index service and PDF files

Hi there,
is there a plug-in for Win2K to let the Index service work on PDF files as well? Thanks in advance for your help.

Hi,
I have changed the host already from localhost into the hostname of the linux server. I tried this also with the FQDN of the server. I have entered the following entry
Hostname linux = sap12
In the URL generator service = http://sap12
Must I restart the portal?
Richard

WLS as SNMP subagent in Win2K

Does the SNMP agent in WLS 7.0 have the ability to be configured as a
subagent (extension agent) for the Win2K SNMP Service? If so, would
someone supply the steps for configuration?
Thanks.
Tom Albrecht

Hi Ludovic,
I'm facing the similar problem on my directory server in China: SNMP subagent process could start firstly, but after several seconds (around 20 seconds) the process will be terminated automatically.
I could open SNMP master agent successfully.
#cd /var/opt/mps/serverroot/plugins/snmp/magt
#./magt CONFIG INIT &
#ps -ef | grep agt
root 761 1 0 14:23:40 ? 0:00 ./magt CONFIG INIT
I could run SNMP subagent process but after 20 seconds the SNMP subagent process is terminated.
#/var/opt/mps/serverroot/bin/slapd/server/sparcv9/ns-ldapagt -d /var/opt/mps/serverroot/slapd-srd2
Command was performed without any error, and then do ps -ef | grep agt, I could see "slapd-srd2" process is running.
but after around 20 seconds when I do "ps -ef | grep agt" again, process "slapd-srd2" was gone:
I tried to add "-D" in the last command and got following debug info in /var/opt/mps/serverroot/slapd-srd2/logs/nsldapagt.log
In agt_setup_sock_addr():host_name = srd2; Port=1199
get_ip_by_name() returened s_addr = 1 for srd2
doing the good return
smux connect failure: Network is unreachable
/var/opt/mps/serverroot/bin/slapd/server/sparcv9/ns-ldapagt: mgmt_init_env fialure! Exiting. Make sure the SNMP master agent is running
I tried to ping srd2, result is "alive", "srd2" is "132.197.198.41". I tried to change "srd2" to OAM IP address "132.197.198.41", the problem is still there.
Solution I tried
I tried to modify /etc/system, add "set ip:do_tcp_fusion = 0x0", then restart server, but it doesn't help me, I still have that problem.
I tried to re-install directory server application, but the problem is still there.
I saw your reply above, you mean this could be the problem of 32bit or 64bit, could you give me more information, I even don't know how to check if I'm running process on 32bit or 64bit.
Thank you so much!
BR/Carrie

[nForce]: Trouble Shooting Guide V1.6a

Hello.
Here is a guide to help solve some problems with K7N2 motherboards.
Problems arise in systems because some components do not work as they should.
Typical issues found with these boards consist of Non-nForce2 Approved RAM & a weak power supply. Other issues could be a cpu won't run at its rated fsb speed or an incorrectly mounted cpu cooler.
Sound problems - too many or incorrectly placed metal standoffs, bad drivers.
Windows won't install or you get a file read error - Incorrectly mounted CPU heat sink, RAM or power supply (PSU).
I've listed some instructions below to help those users that need a basic comprehensive guide to troubleshoot their systems with. Please read through the entire guide prior to posting for help on the forum.
Before you start doing anything, remove the power cord and make sure that you have touched the metal case of your system. This is called "Grounding yourself" and if you don't you could damage your system due to static discharge!
Thanks to Arioch and Dragon60 for comments on this.
1) BIOS/Startup POST reports wrong cpu or frequency
Check if jumper j10 and j11 are set to safemode and also check fsb settings in bios. If the jumpers are set to safe mode set them to normal, this is found in your motherboard manual. The jumpers vary with motherboards and manufacturers.
SafeMode sets cpu and memory to 100mhz.
Both memory and cpu are double pumped.
Data is clocked on the rise and fall of each clock cycle.
That means that 100mhz real frequency is 200mhz virtual frequency.
This is NOT without error and so your results may vary a little.
Non-Delta supports all cpu up to fsb 333
Delta supports all Socket A cpu
Duron upto 1300MHz = 100MHz (=200DDR)
Duron from 1400MHz = 133MHz (=266DDR)
Athlon B type = 100MHz (=200DDR)
Athlon C type = 133MHz (=266DDR)
Athlon XP - C type = 133MHz (=266DDR)
Athlon XP - D type = 166MHz (=333DDR)
Athlon XP - E type = 200MHz (=400DDR)
Support for new Duron 1400, 1600, 1800 with 266Mhz FSB (applebred)
The following boards support them:
(If a board is not on the list then it's not supported!)
-K7N2 6570 V1.0
-K7N2G-L 6570 V1.0
-K7N2G-ILSR 6570 V1.0
-K7N2 Delta 6570 V1.0
-K7N2GM-L 6777 V1.0
Thanks to DeathStalker
The best way to identify a processor is by using the OPN (Ordering Part Number) which can be found on the processor (E.g. AXDA 2700 D K V 3 D).
How to check which cpu you have:
http://www.amd.com/us-en/assets/content_type/DownloadableAssets/Electrical_Specification_Rev04_ENG.pdf
2) Over temp CPU
Is the Heat Sink and Fan rated for the CPU?
The CPU Heat Sink could be mounted wrong! Carefully remove it and check it. It can and will fit 2 ways but ther is only 1 right way. Examine the installation very carefully!
The Heat Sink has a recessed edge that has to be installed over the ridge (higher part or bump) of the socket. If installed backwards then it won't cool the entire area of the processor 'die' and could cause it to burn, thus killing it, or give you trouble as outlined in this guide.
Make sure that you use a QUALITY Thermal Compound/Paste and DO NOT reuse old compound! Note that some Heat Sinks are shipped with Thermal Pads, these are ok for some but will not give you the best heat transfer that a quality paste will.
Below are three images, the first two are incorrect, the last is correct.
Again..It is important to match the notch or step in the heatsink to the socket or it will not seat properly, causing immediate shutdowns, and ultimately damage your CPU.
If you use too much Silver based Thermal Compund you risk shorting the bridges on the CPU. This could cause damage to the CPU itself so use sparingly! If you feel that you've used too much then clean the die and substrate (the brown or green fiberglass material that the die is mounted on) and re-apply. Orange Clean TM is excellent for cleaning any type of thermal compound from a processor. Isopropyl Alchohol is ok but may leave traces of silver on the substrate. Using a 10X eye loupe will ensure that no traces of silver are shorting any bridges together after cleaning. DO NOT clean your processor while it rests in its socket on the motherboard. You run the risk of cleaner mixed with compound and dirt settling into your socket and that will cause further problems.
Last but not least. DO NOT use acetone to clean anything inside your PC. (or outside for that matter) It MAY not do any damage BUT it may dissolve some parts. Especially the coating on capacitors and resistors.
Silverbased compounds are not recommended by most manufacturers and if any traces are detected by them from an RMA'd processor they will usually void the warranty!
The latest AMD XP CPU's (XP-2000 and above) require a copperbased heatsink because their die are smaller and generate far more heat per square centimeter than the "old" CPU's did.
a)How to check the Heat Sink before taking it off:
There is a simple way to check the Heat Sink without taking it off. You do this by first checking your idle temp with SpeedFan or MBM, it should be below 50-55C.
Download Prime95 and run torture test for about 10 minutes while monitoring the temps, after about 1 minute or so it should stabilize and your temp should have gone up about 10-15C (max).
If it still goes up or the system crashes, there is a chance that you've mounted the heat sink incorrectly.
If your system can't run this check, (i.e. freezes or crashes) try setting your FSB to 100. Try to run the test again. If it still fails to run it could well be that the heat sink is mounted wrong or your power supply doesn't have enough power.
You cant check if the heatsink only has partial contact with the CPU die by looking on temperature monitor programs. The heatsink needs to be removed to see that.
If, after reading the guide regarding CPU Heat Sinks, you don't understand what we are talking about, then refer this link: AMD CPU & Cooling guide
http://www.amd.com/us-en/assets/content_type/white_papers_and_tech_docs/23986.pdf
3) Power Supplies
Most common cheap 300-350W power supply units (PSU for short) can't handle an XP-1700 or above, try a better one to be sure.
Make sure your PSU has 200W combined on the +3.3v & +5V rails and that the +3.3V rail is rated for 20A (A = Amps or Amperage) or above. This should be enough for most systems.
On the latest boards the +12V rail has become very important too, expecially with AMD ThunderBird & above CPU's. Make sure your PSU can supply 16A or more.
Alway's make sure you have a decent PSU, it never fails to spend a bit more on that part!
Borrow a bigger one from a friend if you are not sure.
Here's a good post on choosing the right power supply:
Choosing The Right Power Supply
This is the bare minimum that you should see on a PSU running an AMD processor. Intel is a bit more forgiving in some cases but with the amount of devices we use these days this minimum is a good guidline:
+3.3V - 28A or better
+5V - 35A or better
+12V - 16A or better
Watch out!! Cheap PSU's like Q-Tec come nowhere near these figures!! Do NOT trust the 300W or 400W rating on them!!! Q-Tec is about the worst of them all!!
4) Metal Stand-offs
Sometimes we are all a bit careless when it comes to changing a motherboard and forget to look at the layout of the stand-offs (those little silver or brass pieces that the screws screw into to hold the motherboard in the case) that are left from the old motherboard. Some motherboards use more than others thus some overlook the 'extra' one and mount that new board and never know the difference. Until they try to start their new baby up!
Remove the board and check for to see if you have too many of them by counting the holes or screws that you took out and then count the number of stand-offs you have in the case. Remove any uneeded stand-offs then remount your motherboard. Having 'extra's' can short out circuitry and cause all sorts of problems most of which are audio related.
Here are what typical stand-offs look like:
5) Sound
Two types of audio chipsets are used in these boards:
a) The -ILSR version uses Soundstorm and has drivers supplied from MSI or nVidia.
b) The -L version uses RealTek sound and has drivers supplied by MSI and Realtek.
There have been a lot of issues regarding the -L board and its drivers supplied by MSI. Realtek drivers seem to repair these issues and can be found here:
www.realtek.com.tw
Follow the ALC650 link.
6) RAM
Most of the issues involving these boards have been memory related. For various reasons cheaper generic memory doesn't run with nForce2 chipsets well and you should get nForce2 Approved RAM. Here is a link to nVidia's compatibility list as well as a list of what has worked for some:
Good Memory Choices for ALL K7N2 nF2 released boards
It's not a good idea to try to run DDR266 RAM when you have a 333FSB CPU, get DDR333 ram of decent quality.
If you think that you're having RAM issues then replace the ram with another brand to see if it fixes it or borrow some from a friend to check. Make sure it isn't cheap quality RAM or what you borrow isn't cheap quality. You can run to the local CompUSA (if you live in the USA that is) and buy some better quality RAM and return it later if you find that it isn't the problem.
DDR ram speeds:
Duron up to 1300/Athlon-B = 100FSB = PC-1600 = DDR200
Duron from 1400 = 133FSB = PC-2100 = DDR266
Athlon-C/XP up to 2600 = 133FSB = PC-2100 = DDR266
Athlon XP D-type and above = 166FSB = PC-2700 = DDR333
Athlon XP E-type and above = 200FSB = PC-3200 = DDR400
Set Fsb / Dram Ratio to 1:1 that means that the memory is working at the same speed as the fsb does.
Higher DDR speeds are only a must if you try to overclock. You can use faster RAM on a slower system and the motherboard bus will switch down in speed accordingly. The speeds given above are what should be used as a minimum, otherwise you're creating a serious bottleneck of data from the RAM.
Use a decent RAM testing utility such as Memtest86 if you suspect RAM is faulty. Typical failures of RAM include but are not limited to:
a) BSOD (Blue Screen of Death!)
b) Data Corruption
c) Machine won't cold boot
Try your system always with 1 RAM module at a time to see if you have a bad module. Swap modules if you have more than 1 to see if one or the other is bad. When upgrading remeber that adding more modules can give you trouble too. Especially if you mix manufacturers. Some sticks just won't work in pairs and some fail when you put 3 or more in the system. When you want to use 3 sticks, make very sure you use the nVidia tested and approved modules, they are your best chance that they will work without problems.
If still nothing try to seat the ram in another slot, sometimes they work better in another slot.
Thanks boost
Or raise the RAM voltage a little but be careful doing this! Sometimes this works when you have a lot of ram in the system.
7) BIOS
Sometimes when we play with our BIOS settings and set something wrong in it or set something incompatible with our hardware this causes the motherboard to not boot up. Sometimes they come from the factory that way as well. If so then clear the CMOS and start with the default settings. If it works try setting ONLY A FEW SETTINGS at a time and nothing more! If it works then go further from there a couple of settings at a time.
There are issues when changing VCORE and it gets stuck.
There are 3 ways to work around this issue.
1. Updating to the latest bios seems to fix it most of the time.
2. Clear CMOS, change VCORE in the BIOS, save changes then reboot and it should be changed.
3. Change VCORE in BIOS, save changes, turn off pc then disconnect PSU from wall outlet by either disconnecting the power cord or use the switch on the backside of the psu if there is one. Reconnect the power cord or turn the switch on again. Boot up the system, go into the BIOS and check under pc health to see if it has changed.
For RAID boards only!!
If you recieve a message at boot saying:
No Hard disk/drive present...BIOS will not be installed...
or something comparable, it means that there are no drives connected to the raid controllers and it's not installing the drivers needed to support the function of that particular device FROM BIOS ONLY! This is nothing to worry about and all of the other functions of your machine should work properly.
Modded bios to fix problems when using multiplier 10 and 10.5 and also to be able to use a higher FSB than with the MSI bios.
http://www.nforcershq.com/forum/viewtopic.php?t=46052
8) Clearing the CMOS chip
Disconnect the system power cord and push the case power button to drain all remaining power in the psu for approximately 15 seconds
Then move jumper jbat1 and wait 10 seconds and move it back to the original position. You should ensure that the jumper has metal inside of it when removed, sometimes (rarely) they don't. This process resets or clears the CMOS chip and is shown in most motherboard manuals.Now connect the power cord and restart your system.
Some motherboards require that the battery must be removed for 20 minutes before putting the battery and jbat1 back for the CMOS chip to be cleared.
***Starting your K7N2 Delta2 at default settings***
By "labtech1"
As some of you will be aware there is no safe mode jumper J10 on the K7N2 Delta2 series of boards. This has been replaced by the "insert" key method as used by Abit and Epox. To start your board at its default settings following an unsuccessful overclocking attempt you need to do the following using a ps2 keyboard. Turn off your machine and disconnect from the mains or turn off the switch on the back of the power supply. Press the front panel power switch several times to discharge any charge remaining in the power supply capacitors. Reconnect the power by plugging into wall socket or turning on psu power switch. Press and hold down "insert" on the keyboard and press the case front panel power switch. If you are successful it should start the cpu and memory at 100Mhz FSB. If it does press "delete" to reenter the bios to change your settings to known safe settings. Good luck.
9) Harddisks
If your hard drive is giving you problems:
Western Digital (WD) drive's are jumpered somewhat strange compared to others:
No jumper = Stand-Alone drive with no other drive attached to the cable.
Jumper master = Use this setting on your main drive if you have a slave drive installed in your system.
Jumper slave = Use this setting if you have a second hard drive installed in your system.
Cable Select - the preferred jumper setting
If your Hard Drive is doing weird things:
Make sure you have connected the color-coded connectors to the color-coded connectors on the motherboard and connect the other END of the cable to the hard drive. The middle connector can be left unattached without problems if not needed.
Not all motherboards have color-coded connectors.
IBM harddisks seem to fail a lot, try Drive-Fitness-Test on it, see if it has problems.
Run drive fitness test (DFT)
Maxtor also has its own version of hard drive check for their drives and is available from their website.
Any brand of hard drive can have problems so check the manufacturer website to see if there is a testing utility to use to make sure they are ok. Hard drive failures can cause some of the strangest problems with computers and should be checked via the Event Viewer of your Operating System or using the mfg's utility. Sometimes the Event Viewer will give you clues that you have bad sectors leading you to a potential hard drive failure. You could also find IDE/SCSI controllers that are suspect by looking there as well. Win9x and ME DO NOT have Event Viewers.
Alway's be sure your harddisk is in tip-top shape! If you suspect that it's not, replace it to verify.
IDE devices and hard drive guide (Written by Assaf & Bas)
IDE devices and hard drive guide(Written by Assaf & Bas)
To enable a hard drive over 137GB in Win2000 edit this registry key:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Atapi\Parameters]
"EnableBigLba"=dword:00000001
The K7N2G & Delta -ILSR boards support 2 IDE Devices on IDE 1 & 2, 1 IDE hard drive on IDE3 and 2 SATA drive's on the SATA Ports.
There is a modded bios that allows 2 drives on IDE3. USE THIS AT YOUR OWN RISK!!! Here is a link to it:
http://www.nforcershq.com/forum/viewtopic.php?t=27626&highlight=
Harddisk/power LED not functioning:
If your Hard Drive or Power LED doesn't work try turning the plug around on the motherboard connector. Some manufacturers don't mark or wire the LED cables properly and the LEDs will only work when + and - is correct.
Hard drive LEDs do not work with SATA drives but O&O Drive LED opens a little window and there you can see when a harddrive or cd is accessed. Works on both ide and sata drives.
10) Floppy Drives
If your floppy drive doesn't work or the LED stays on all of the time make sure the floppy is set correctly in the BIOS because the BIOS doesn't autodetect a floppy drive.
Check the cable making sure that the twist in the cable is at the floppy-drive side and flip the connector at the around. If it stays on after that or you still can't read a floppy disk try another drive or a different manufaturer type drive.
11) USB Ports
USB 2.0 ports are supported ONLY in Win2000 w/SP3 and XP w/SP1. Update your OS from Windows Update and let the OS install the ports after reboot and they should work.
If your USB ports aren't working:
Check in the BIOS if the ports are enabled. If you're using the front USB ports of your case check to see if all of the wires are connected properly.
There are 4 wires for each USB channel.
In some manufaturer's cases they are supplied with a wire called USBOC. Don't connect this as it can cause problems.
Also different mfg's mark the wires with different names so the basic nomenclature would be something like this:
+5v = +VCC
-D = -USB
+D = +USB
Note: Normally the cables are marked as +USB1 or -USB1, +USB2 or -USB2 and so on...please ensure that all of the 1's are together and all of the 2's are together.
12) Replacing parts and the system won't boot after
It's never a good idea to replace stuff like CPU and ram without taking the board out of the case. But if you do so please support the board because if you don't you might bend the board a little and cause trace breakage or component connections to the board to crack or break causing a bad contact. Always support the board when you replace components no matter what!
Also make sure your system is compatible with any replacement component. For example your PSU may not be able to handle a video card upgrade from a GeForce2 440MX to a GeForce4 Ti-4600 because the +12v rail is too low or the motherboard isn't rated to output the proper voltage to the AGP port.
If you have parts that work in another computer with a different chipset this DOES NOT mean they will work with the nforce2 chipset.
13) Graphics Card
If there is stability problem and/or can't use agp 8x then update to the latest bios and it should work. Also try to disable the 8x feature of the motherboard in the BIOS. If neither of these work then you may have a PSU that is under-powered and needs to be replaced. You could also have a faulty video card, AGP port on the motherboard among other things. If you have to disable the 8x feature in the BIOS then there is still a problem even if the card starts working. That may mean the motherboard is bad. Also use the latest drivers available from the respective manufacturer and don't forget to uninstall the old drivers first!! There is a sticky post in the VGA forum that details this process.
14) Checking the power supply
Don't do this if you don't know what you are doing!
a) Disconnect the power supply.
b) Orient the 20-pin power connector with the clip up.
c) Locate pin 4 and pin 8 top row, mostly green and black wire. (Usually the PSU manufacturer will have a drawing labeling the pins on their website)
d) Use a wire to short them (or better a 12V test lamp).
e) Now connect the power cord and the fan inside the power supply should start spinning. If it doesn't your power supply might be dead.
15) Windows
a) If you find that Windows2000/XP won't run stable:
Try to disable APIC and install again. Not all drivers/devices like the APIC.
b) Windows2000/XP won't install USB 2.0:
Install the latest service pack using Windows Update (SP3 Win2000 or SP1 WinXP). Windows should detect the USB ports on reboot and install the drivers for them. They should work now but if not you could have a faulty motherboard.
If you use a current or slipstreamed copy of Win2K or XP with the latest service pack they include these new drivers. This download will no longer be available on Windows Update.
USE THESE AT YOUR OWN RISK!!!
Slipstreaming Win2K with Service Packs and Creating a Bootable CD:
http://old.bink.nu/bootcd/
Slipstreaming Windows XP Service Packs and Creating a Bootable CD
http://www.windows-help.net/WindowsXP/winxp-sp1-bootcd.html
16) Raid
Configure a raid array:
After you have connected 1 or 2 hard drives to your Raid IDE port(s) press CTRL + F during boot and create a raid array.
It is possible to have 2 raid arrays working at the same time.
To boot from a raid array set SCSI as the first boot device.
To install windows on a raid array you have to press F6 to load raid drivers during the initial install of windows. This will be repeated during Windows desktop installation of drivers because the initial drivers are only loaded to memory during this initial install allowing the Windows installation program to access the raid drives. A default driver is loaded at bootup so that the drives can be accessed until the real drivers are loaded from the MB disk.
Raid 0 sets up striping which gives more performance for applications. Raid 1 sets up mirroring which gives drive security by duplicating the primary drive to the secondary drive.
When using two different sized drives in a raid array, the larger drive is forced to only use the amount of disk space that the smaller drive provides.
nForce 2 raid FAQ
(Mostly by Wonkanoby)
The third IDE only works with harddrives not optical drives such as CD,DVD. It only supports one drive.
You must create an array first, weather you are using 2 drives or just one
or nothing will happen .
You must also have a 3.5 floppy with the appropriate drivers handy.
INSTALLATION
To install raid as a boot drive.
Control + F and make the array.
Set SCSI second to cdrom in boot order.
Boot to xp cd and hit F6 as it prompts you to do right at the beginning and then insert the floppy.
This will be repeated during Windows desktop installation of drivers because the initial drivers are only loaded to memory during this initial install allowing the Windows installation program to access the raid drives.
The rest of the format/install is all as normal.
Drivers for the raid can be found here.
http://us-download.msi.com.tw/support/dvr_exe/sata48N.exe
Promise PDC20376 Serial-ATA RAID Utility
http://us-download.msi.com.tw/support/dvr_exe/37653.exe
If you make a new floppy, unrar them.
Then copy every thing including the text files to the floppy.
(no text files, nothing happens)
MODDED BIOS
such as
http://www.nforcershq.com/forum/viewtopic.php?t=27626
There are several offering full RAID.
They add ability to have 2x drives on ide 3.
I'm skeptical running raid 0 with both on the same ide myself.
Now these you must get the bios and the drivers.
The drivers are not the same as those for the RAID MSI includes.
The drivers are linked on that BIOS page I have provided.
RAID 0, sets up striping, which gives more performance for applications.
RAID 1, sets up mirroring which gives drive security by duplicating the primary drive to the secondary drive.
When using two different sized drives in a RAID array, the larger drive is forced to only use the amount of disk space that the smaller drive provides.
17) Good Links
J*A*G'S *Updated* nForce Cooling Guide (written by JAG)
Suggestions on posting and getting better answers (written by GlennVidia)
Good Memory Choices for K7N2G- IL and ILSR Board (written by Bonz)
ati problem ,post vga card model and bios (written by Wonkanoby)
Powersupplies(Written by Bas)
Moan Guide (Written by Wonkanoby)
A few good websites to have around!!
The Freeware Thread
NFORCE 2 OVERCLOCKING AND MODDING GUIDES
Use these guides, including the content of this entire guide, at your own risk!
This forum and it's members, including MSI, assume no liability whatsoever!
Part One
Part Two
I am not an expert on computers so I have most likely forgotten a lot of things. Please send me a private message or email me and I will add it if it's applicable. If you feel that something here is in error then please contact me via the above as well.
I also want to thank everyone that helped put this guide together.
All Star Lineup!
Arioch
DeathStalker
maesus
ClarkKent57
boost
Assaf
Bas
Tweetyoost
Stygge
HansH
GlennVidia
RoganJosh
Bonz
Wonkanoby
Dragon60
[T-A]_Super_10
labtech1

Hello.
Here is a guide to help solve some problems with K7N2 motherboards.
Problems arise in systems because some components do not work as they should.
Typical issues found with these boards consist of Non-nForce2 Approved RAM & a weak power supply. Other issues could be a cpu won't run at its rated fsb speed or an incorrectly mounted cpu cooler.
Sound problems - too many or incorrectly placed metal standoffs, bad drivers.
Windows won't install or you get a file read error - Incorrectly mounted CPU heat sink, RAM or power supply (PSU).
I've listed some instructions below to help those users that need a basic comprehensive guide to troubleshoot their systems with. Please read through the entire guide prior to posting for help on the forum.
Before you start doing anything, remove the power cord and make sure that you have touched the metal case of your system. This is called "Grounding yourself" and if you don't you could damage your system due to static discharge!
Thanks to Arioch and Dragon60 for comments on this.
1) BIOS/Startup POST reports wrong cpu or frequency
Check if jumper j10 and j11 are set to safemode and also check fsb settings in bios. If the jumpers are set to safe mode set them to normal, this is found in your motherboard manual. The jumpers vary with motherboards and manufacturers.
SafeMode sets cpu and memory to 100mhz.
Both memory and cpu are double pumped.
Data is clocked on the rise and fall of each clock cycle.
That means that 100mhz real frequency is 200mhz virtual frequency.
This is NOT without error and so your results may vary a little.
Non-Delta supports all cpu up to fsb 333
Delta supports all Socket A cpu
Duron upto 1300MHz = 100MHz (=200DDR)
Duron from 1400MHz = 133MHz (=266DDR)
Athlon B type = 100MHz (=200DDR)
Athlon C type = 133MHz (=266DDR)
Athlon XP - C type = 133MHz (=266DDR)
Athlon XP - D type = 166MHz (=333DDR)
Athlon XP - E type = 200MHz (=400DDR)
Support for new Duron 1400, 1600, 1800 with 266Mhz FSB (applebred)
The following boards support them:
(If a board is not on the list then it's not supported!)
-K7N2 6570 V1.0
-K7N2G-L 6570 V1.0
-K7N2G-ILSR 6570 V1.0
-K7N2 Delta 6570 V1.0
-K7N2GM-L 6777 V1.0
Thanks to DeathStalker
The best way to identify a processor is by using the OPN (Ordering Part Number) which can be found on the processor (E.g. AXDA 2700 D K V 3 D).
How to check which cpu you have:
http://www.amd.com/us-en/assets/content_type/DownloadableAssets/Electrical_Specification_Rev04_ENG.pdf
2) Over temp CPU
Is the Heat Sink and Fan rated for the CPU?
The CPU Heat Sink could be mounted wrong! Carefully remove it and check it. It can and will fit 2 ways but ther is only 1 right way. Examine the installation very carefully!
The Heat Sink has a recessed edge that has to be installed over the ridge (higher part or bump) of the socket. If installed backwards then it won't cool the entire area of the processor 'die' and could cause it to burn, thus killing it, or give you trouble as outlined in this guide.
Make sure that you use a QUALITY Thermal Compound/Paste and DO NOT reuse old compound! Note that some Heat Sinks are shipped with Thermal Pads, these are ok for some but will not give you the best heat transfer that a quality paste will.
Below are three images, the first two are incorrect, the last is correct.
Again..It is important to match the notch or step in the heatsink to the socket or it will not seat properly, causing immediate shutdowns, and ultimately damage your CPU.
If you use too much Silver based Thermal Compund you risk shorting the bridges on the CPU. This could cause damage to the CPU itself so use sparingly! If you feel that you've used too much then clean the die and substrate (the brown or green fiberglass material that the die is mounted on) and re-apply. Orange Clean TM is excellent for cleaning any type of thermal compound from a processor. Isopropyl Alchohol is ok but may leave traces of silver on the substrate. Using a 10X eye loupe will ensure that no traces of silver are shorting any bridges together after cleaning. DO NOT clean your processor while it rests in its socket on the motherboard. You run the risk of cleaner mixed with compound and dirt settling into your socket and that will cause further problems.
Last but not least. DO NOT use acetone to clean anything inside your PC. (or outside for that matter) It MAY not do any damage BUT it may dissolve some parts. Especially the coating on capacitors and resistors.
Silverbased compounds are not recommended by most manufacturers and if any traces are detected by them from an RMA'd processor they will usually void the warranty!
The latest AMD XP CPU's (XP-2000 and above) require a copperbased heatsink because their die are smaller and generate far more heat per square centimeter than the "old" CPU's did.
a)How to check the Heat Sink before taking it off:
There is a simple way to check the Heat Sink without taking it off. You do this by first checking your idle temp with SpeedFan or MBM, it should be below 50-55C.
Download Prime95 and run torture test for about 10 minutes while monitoring the temps, after about 1 minute or so it should stabilize and your temp should have gone up about 10-15C (max).
If it still goes up or the system crashes, there is a chance that you've mounted the heat sink incorrectly.
If your system can't run this check, (i.e. freezes or crashes) try setting your FSB to 100. Try to run the test again. If it still fails to run it could well be that the heat sink is mounted wrong or your power supply doesn't have enough power.
You cant check if the heatsink only has partial contact with the CPU die by looking on temperature monitor programs. The heatsink needs to be removed to see that.
If, after reading the guide regarding CPU Heat Sinks, you don't understand what we are talking about, then refer this link: AMD CPU & Cooling guide
http://www.amd.com/us-en/assets/content_type/white_papers_and_tech_docs/23986.pdf
3) Power Supplies
Most common cheap 300-350W power supply units (PSU for short) can't handle an XP-1700 or above, try a better one to be sure.
Make sure your PSU has 200W combined on the +3.3v & +5V rails and that the +3.3V rail is rated for 20A (A = Amps or Amperage) or above. This should be enough for most systems.
On the latest boards the +12V rail has become very important too, expecially with AMD ThunderBird & above CPU's. Make sure your PSU can supply 16A or more.
Alway's make sure you have a decent PSU, it never fails to spend a bit more on that part!
Borrow a bigger one from a friend if you are not sure.
Here's a good post on choosing the right power supply:
Choosing The Right Power Supply
This is the bare minimum that you should see on a PSU running an AMD processor. Intel is a bit more forgiving in some cases but with the amount of devices we use these days this minimum is a good guidline:
+3.3V - 28A or better
+5V - 35A or better
+12V - 16A or better
Watch out!! Cheap PSU's like Q-Tec come nowhere near these figures!! Do NOT trust the 300W or 400W rating on them!!! Q-Tec is about the worst of them all!!
4) Metal Stand-offs
Sometimes we are all a bit careless when it comes to changing a motherboard and forget to look at the layout of the stand-offs (those little silver or brass pieces that the screws screw into to hold the motherboard in the case) that are left from the old motherboard. Some motherboards use more than others thus some overlook the 'extra' one and mount that new board and never know the difference. Until they try to start their new baby up!
Remove the board and check for to see if you have too many of them by counting the holes or screws that you took out and then count the number of stand-offs you have in the case. Remove any uneeded stand-offs then remount your motherboard. Having 'extra's' can short out circuitry and cause all sorts of problems most of which are audio related.
Here are what typical stand-offs look like:
5) Sound
Two types of audio chipsets are used in these boards:
a) The -ILSR version uses Soundstorm and has drivers supplied from MSI or nVidia.
b) The -L version uses RealTek sound and has drivers supplied by MSI and Realtek.
There have been a lot of issues regarding the -L board and its drivers supplied by MSI. Realtek drivers seem to repair these issues and can be found here:
www.realtek.com.tw
Follow the ALC650 link.
6) RAM
Most of the issues involving these boards have been memory related. For various reasons cheaper generic memory doesn't run with nForce2 chipsets well and you should get nForce2 Approved RAM. Here is a link to nVidia's compatibility list as well as a list of what has worked for some:
Good Memory Choices for ALL K7N2 nF2 released boards
It's not a good idea to try to run DDR266 RAM when you have a 333FSB CPU, get DDR333 ram of decent quality.
If you think that you're having RAM issues then replace the ram with another brand to see if it fixes it or borrow some from a friend to check. Make sure it isn't cheap quality RAM or what you borrow isn't cheap quality. You can run to the local CompUSA (if you live in the USA that is) and buy some better quality RAM and return it later if you find that it isn't the problem.
DDR ram speeds:
Duron up to 1300/Athlon-B = 100FSB = PC-1600 = DDR200
Duron from 1400 = 133FSB = PC-2100 = DDR266
Athlon-C/XP up to 2600 = 133FSB = PC-2100 = DDR266
Athlon XP D-type and above = 166FSB = PC-2700 = DDR333
Athlon XP E-type and above = 200FSB = PC-3200 = DDR400
Set Fsb / Dram Ratio to 1:1 that means that the memory is working at the same speed as the fsb does.
Higher DDR speeds are only a must if you try to overclock. You can use faster RAM on a slower system and the motherboard bus will switch down in speed accordingly. The speeds given above are what should be used as a minimum, otherwise you're creating a serious bottleneck of data from the RAM.
Use a decent RAM testing utility such as Memtest86 if you suspect RAM is faulty. Typical failures of RAM include but are not limited to:
a) BSOD (Blue Screen of Death!)
b) Data Corruption
c) Machine won't cold boot
Try your system always with 1 RAM module at a time to see if you have a bad module. Swap modules if you have more than 1 to see if one or the other is bad. When upgrading remeber that adding more modules can give you trouble too. Especially if you mix manufacturers. Some sticks just won't work in pairs and some fail when you put 3 or more in the system. When you want to use 3 sticks, make very sure you use the nVidia tested and approved modules, they are your best chance that they will work without problems.
If still nothing try to seat the ram in another slot, sometimes they work better in another slot.
Thanks boost
Or raise the RAM voltage a little but be careful doing this! Sometimes this works when you have a lot of ram in the system.
7) BIOS
Sometimes when we play with our BIOS settings and set something wrong in it or set something incompatible with our hardware this causes the motherboard to not boot up. Sometimes they come from the factory that way as well. If so then clear the CMOS and start with the default settings. If it works try setting ONLY A FEW SETTINGS at a time and nothing more! If it works then go further from there a couple of settings at a time.
There are issues when changing VCORE and it gets stuck.
There are 3 ways to work around this issue.
1. Updating to the latest bios seems to fix it most of the time.
2. Clear CMOS, change VCORE in the BIOS, save changes then reboot and it should be changed.
3. Change VCORE in BIOS, save changes, turn off pc then disconnect PSU from wall outlet by either disconnecting the power cord or use the switch on the backside of the psu if there is one. Reconnect the power cord or turn the switch on again. Boot up the system, go into the BIOS and check under pc health to see if it has changed.
For RAID boards only!!
If you recieve a message at boot saying:
No Hard disk/drive present...BIOS will not be installed...
or something comparable, it means that there are no drives connected to the raid controllers and it's not installing the drivers needed to support the function of that particular device FROM BIOS ONLY! This is nothing to worry about and all of the other functions of your machine should work properly.
Modded bios to fix problems when using multiplier 10 and 10.5 and also to be able to use a higher FSB than with the MSI bios.
http://www.nforcershq.com/forum/viewtopic.php?t=46052
8) Clearing the CMOS chip
Disconnect the system power cord and push the case power button to drain all remaining power in the psu for approximately 15 seconds
Then move jumper jbat1 and wait 10 seconds and move it back to the original position. You should ensure that the jumper has metal inside of it when removed, sometimes (rarely) they don't. This process resets or clears the CMOS chip and is shown in most motherboard manuals.Now connect the power cord and restart your system.
Some motherboards require that the battery must be removed for 20 minutes before putting the battery and jbat1 back for the CMOS chip to be cleared.
***Starting your K7N2 Delta2 at default settings***
By "labtech1"
As some of you will be aware there is no safe mode jumper J10 on the K7N2 Delta2 series of boards. This has been replaced by the "insert" key method as used by Abit and Epox. To start your board at its default settings following an unsuccessful overclocking attempt you need to do the following using a ps2 keyboard. Turn off your machine and disconnect from the mains or turn off the switch on the back of the power supply. Press the front panel power switch several times to discharge any charge remaining in the power supply capacitors. Reconnect the power by plugging into wall socket or turning on psu power switch. Press and hold down "insert" on the keyboard and press the case front panel power switch. If you are successful it should start the cpu and memory at 100Mhz FSB. If it does press "delete" to reenter the bios to change your settings to known safe settings. Good luck.
9) Harddisks
If your hard drive is giving you problems:
Western Digital (WD) drive's are jumpered somewhat strange compared to others:
No jumper = Stand-Alone drive with no other drive attached to the cable.
Jumper master = Use this setting on your main drive if you have a slave drive installed in your system.
Jumper slave = Use this setting if you have a second hard drive installed in your system.
Cable Select - the preferred jumper setting
If your Hard Drive is doing weird things:
Make sure you have connected the color-coded connectors to the color-coded connectors on the motherboard and connect the other END of the cable to the hard drive. The middle connector can be left unattached without problems if not needed.
Not all motherboards have color-coded connectors.
IBM harddisks seem to fail a lot, try Drive-Fitness-Test on it, see if it has problems.
Run drive fitness test (DFT)
Maxtor also has its own version of hard drive check for their drives and is available from their website.
Any brand of hard drive can have problems so check the manufacturer website to see if there is a testing utility to use to make sure they are ok. Hard drive failures can cause some of the strangest problems with computers and should be checked via the Event Viewer of your Operating System or using the mfg's utility. Sometimes the Event Viewer will give you clues that you have bad sectors leading you to a potential hard drive failure. You could also find IDE/SCSI controllers that are suspect by looking there as well. Win9x and ME DO NOT have Event Viewers.
Alway's be sure your harddisk is in tip-top shape! If you suspect that it's not, replace it to verify.
IDE devices and hard drive guide (Written by Assaf & Bas)
IDE devices and hard drive guide(Written by Assaf & Bas)
To enable a hard drive over 137GB in Win2000 edit this registry key:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Atapi\Parameters]
"EnableBigLba"=dword:00000001
The K7N2G & Delta -ILSR boards support 2 IDE Devices on IDE 1 & 2, 1 IDE hard drive on IDE3 and 2 SATA drive's on the SATA Ports.
There is a modded bios that allows 2 drives on IDE3. USE THIS AT YOUR OWN RISK!!! Here is a link to it:
http://www.nforcershq.com/forum/viewtopic.php?t=27626&highlight=
Harddisk/power LED not functioning:
If your Hard Drive or Power LED doesn't work try turning the plug around on the motherboard connector. Some manufacturers don't mark or wire the LED cables properly and the LEDs will only work when + and - is correct.
Hard drive LEDs do not work with SATA drives but O&O Drive LED opens a little window and there you can see when a harddrive or cd is accessed. Works on both ide and sata drives.
10) Floppy Drives
If your floppy drive doesn't work or the LED stays on all of the time make sure the floppy is set correctly in the BIOS because the BIOS doesn't autodetect a floppy drive.
Check the cable making sure that the twist in the cable is at the floppy-drive side and flip the connector at the around. If it stays on after that or you still can't read a floppy disk try another drive or a different manufaturer type drive.
11) USB Ports
USB 2.0 ports are supported ONLY in Win2000 w/SP3 and XP w/SP1. Update your OS from Windows Update and let the OS install the ports after reboot and they should work.
If your USB ports aren't working:
Check in the BIOS if the ports are enabled. If you're using the front USB ports of your case check to see if all of the wires are connected properly.
There are 4 wires for each USB channel.
In some manufaturer's cases they are supplied with a wire called USBOC. Don't connect this as it can cause problems.
Also different mfg's mark the wires with different names so the basic nomenclature would be something like this:
+5v = +VCC
-D = -USB
+D = +USB
Note: Normally the cables are marked as +USB1 or -USB1, +USB2 or -USB2 and so on...please ensure that all of the 1's are together and all of the 2's are together.
12) Replacing parts and the system won't boot after
It's never a good idea to replace stuff like CPU and ram without taking the board out of the case. But if you do so please support the board because if you don't you might bend the board a little and cause trace breakage or component connections to the board to crack or break causing a bad contact. Always support the board when you replace components no matter what!
Also make sure your system is compatible with any replacement component. For example your PSU may not be able to handle a video card upgrade from a GeForce2 440MX to a GeForce4 Ti-4600 because the +12v rail is too low or the motherboard isn't rated to output the proper voltage to the AGP port.
If you have parts that work in another computer with a different chipset this DOES NOT mean they will work with the nforce2 chipset.
13) Graphics Card
If there is stability problem and/or can't use agp 8x then update to the latest bios and it should work. Also try to disable the 8x feature of the motherboard in the BIOS. If neither of these work then you may have a PSU that is under-powered and needs to be replaced. You could also have a faulty video card, AGP port on the motherboard among other things. If you have to disable the 8x feature in the BIOS then there is still a problem even if the card starts working. That may mean the motherboard is bad. Also use the latest drivers available from the respective manufacturer and don't forget to uninstall the old drivers first!! There is a sticky post in the VGA forum that details this process.
14) Checking the power supply
Don't do this if you don't know what you are doing!
a) Disconnect the power supply.
b) Orient the 20-pin power connector with the clip up.
c) Locate pin 4 and pin 8 top row, mostly green and black wire. (Usually the PSU manufacturer will have a drawing labeling the pins on their website)
d) Use a wire to short them (or better a 12V test lamp).
e) Now connect the power cord and the fan inside the power supply should start spinning. If it doesn't your power supply might be dead.
15) Windows
a) If you find that Windows2000/XP won't run stable:
Try to disable APIC and install again. Not all drivers/devices like the APIC.
b) Windows2000/XP won't install USB 2.0:
Install the latest service pack using Windows Update (SP3 Win2000 or SP1 WinXP). Windows should detect the USB ports on reboot and install the drivers for them. They should work now but if not you could have a faulty motherboard.
If you use a current or slipstreamed copy of Win2K or XP with the latest service pack they include these new drivers. This download will no longer be available on Windows Update.
USE THESE AT YOUR OWN RISK!!!
Slipstreaming Win2K with Service Packs and Creating a Bootable CD:
http://old.bink.nu/bootcd/
Slipstreaming Windows XP Service Packs and Creating a Bootable CD
http://www.windows-help.net/WindowsXP/winxp-sp1-bootcd.html
16) Raid
Configure a raid array:
After you have connected 1 or 2 hard drives to your Raid IDE port(s) press CTRL + F during boot and create a raid array.
It is possible to have 2 raid arrays working at the same time.
To boot from a raid array set SCSI as the first boot device.
To install windows on a raid array you have to press F6 to load raid drivers during the initial install of windows. This will be repeated during Windows desktop installation of drivers because the initial drivers are only loaded to memory during this initial install allowing the Windows installation program to access the raid drives. A default driver is loaded at bootup so that the drives can be accessed until the real drivers are loaded from the MB disk.
Raid 0 sets up striping which gives more performance for applications. Raid 1 sets up mirroring which gives drive security by duplicating the primary drive to the secondary drive.
When using two different sized drives in a raid array, the larger drive is forced to only use the amount of disk space that the smaller drive provides.
nForce 2 raid FAQ
(Mostly by Wonkanoby)
The third IDE only works with harddrives not optical drives such as CD,DVD. It only supports one drive.
You must create an array first, weather you are using 2 drives or just one
or nothing will happen .
You must also have a 3.5 floppy with the appropriate drivers handy.
INSTALLATION
To install raid as a boot drive.
Control + F and make the array.
Set SCSI second to cdrom in boot order.
Boot to xp cd and hit F6 as it prompts you to do right at the beginning and then insert the floppy.
This will be repeated during Windows desktop installation of drivers because the initial drivers are only loaded to memory during this initial install allowing the Windows installation program to access the raid drives.
The rest of the format/install is all as normal.
Drivers for the raid can be found here.
http://us-download.msi.com.tw/support/dvr_exe/sata48N.exe
Promise PDC20376 Serial-ATA RAID Utility
http://us-download.msi.com.tw/support/dvr_exe/37653.exe
If you make a new floppy, unrar them.
Then copy every thing including the text files to the floppy.
(no text files, nothing happens)
MODDED BIOS
such as
http://www.nforcershq.com/forum/viewtopic.php?t=27626
There are several offering full RAID.
They add ability to have 2x drives on ide 3.
I'm skeptical running raid 0 with both on the same ide myself.
Now these you must get the bios and the drivers.
The drivers are not the same as those for the RAID MSI includes.
The drivers are linked on that BIOS page I have provided.
RAID 0, sets up striping, which gives more performance for applications.
RAID 1, sets up mirroring which gives drive security by duplicating the primary drive to the secondary drive.
When using two different sized drives in a RAID array, the larger drive is forced to only use the amount of disk space that the smaller drive provides.
17) Good Links
J*A*G'S *Updated* nForce Cooling Guide (written by JAG)
Suggestions on posting and getting better answers (written by GlennVidia)
Good Memory Choices for K7N2G- IL and ILSR Board (written by Bonz)
ati problem ,post vga card model and bios (written by Wonkanoby)
Powersupplies(Written by Bas)
Moan Guide (Written by Wonkanoby)
A few good websites to have around!!
The Freeware Thread
NFORCE 2 OVERCLOCKING AND MODDING GUIDES
Use these guides, including the content of this entire guide, at your own risk!
This forum and it's members, including MSI, assume no liability whatsoever!
Part One
Part Two
I am not an expert on computers so I have most likely forgotten a lot of things. Please send me a private message or email me and I will add it if it's applicable. If you feel that something here is in error then please contact me via the above as well.
I also want to thank everyone that helped put this guide together.
All Star Lineup!
Arioch
DeathStalker
maesus
ClarkKent57
boost
Assaf
Bas
Tweetyoost
Stygge
HansH
GlennVidia
RoganJosh
Bonz
Wonkanoby
Dragon60
[T-A]_Super_10
labtech1

Java VM 1.4.2 Install problems

I have multiple Win2K Workstations (Service pack4 IE 6 Sp1) that do not install the VM properly. Although the install appears to go fine, when trying to access a site requiring that VM 1.4.2 be installed, Internet Explrer locks up. Double click on the Java Icon in the windows control panel and the console does not appear. Also, the java.exe gets stuck in the task amanger. This would appear to be an install issue. This is happening on at least 50% of the machines over two states that have tried to install. Has anyone seen this or have a fix?

Yes,
Actually I am the admin and am performing all the installs/tests. I also have another admin in another state doing the installs there and he has the same issues. I have spoken to tech support and have really gotten no-where, I have been asked to uninstall and reinstall, use 1.4.03 and try 1.4.05 as well. No luck with anything. This has to be an incompatibility with something wouldn't you say?

More then one WEMservices

Hi ,
I found 4 WEM services in my win2k server service and non of them are runing, I think it is because I have installed everything in one m/c. If I start any one then it is fine. if I try to start one more then it close the first one or some time it gives error and don't start the second one. I need some help about which service to start.
thanks ....

Yes, you can. There are many threads on this forum discussing this.
I have two site running fro my iweb.
Some have suggested running them under different users on the mac
Good luck,
Ben

J2EE1.3 and 1.2.1 version

I installed J2EE1.3 on my computer, win2K Professional service pack2 and I set all classpath and evironment variables up. I run j2ee.bat but it showed me some error messages. I didn't understand why it didn't work.
I uninstall J2EE1.3 version and installed 1.2.1 version and then it worked. who know why it does?

Thank you for your reply, neville_sequeira
As I said I didn't change env variables when i reinstall the J2EE1.2.1 ver.
The error messeges are following
Exception in thread "main" java.lang.NoClassDefFoundError: org/omg/CosNaming/Nam
ingContextOperations
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:460)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:11
1)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:247)
at java.net.URLClassLoader.access$100(URLClassLoader.java:55)
at java.net.URLClassLoader$1.run(URLClassLoader.java:194)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
at java.lang.ClassLoader.loadClass(ClassLoader.java:288)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:286)
at java.lang.ClassLoader.loadClass(ClassLoader.java:244)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:304)
at com.sun.corba.ee.internal.corba.ORB.<init>(ORB.java:296)
at com.sun.corba.ee.internal.iiop.ORB.<init>(ORB.java:88)
at com.sun.corba.ee.internal.POA.POAORB.<init>(POAORB.java:120)
at com.sun.corba.ee.internal.Interceptors.PIORB.<init>(PIORB.java:197)
at com.sun.corba.ee.internal.TxPOA.TxPIORB.<init>(TxPIORB.java:81)
at com.sun.enterprise.iiop.POAEJBORB.<init>(POAEJBORB.java:111)
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Class.java:237)
at org.omg.CORBA.ORB.create_impl(ORB.java:284)
at org.omg.CORBA.ORB.init(ORB.java:328)
at com.sun.enterprise.util.ORBManager.createORB(ORBManager.java:144)
at com.sun.enterprise.util.ORBManager.init(ORBManager.java:69)
at com.sun.enterprise.server.J2EEServer.createORB(J2EEServer.java:381)
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:193)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:918)
Thankyou

LabVIEW IDE crashing!

Hi there,
I have just run into some very strange behaviour in LabVIEW (7.0 on Win2k with service pack 2).
I have an event structure with several user events (about 12) listed in it. Everything was working fine yesterday. Today I tried to add another user event to the structure and LabVIEW crashed (giving usual cryptic error message saying referenced memory could not be read).
Now, I have experimented quite a bit, and have the following observations to give:
LabVIEW is happy adding more events until I try and add an event if the currently selected event is a Filter event (i.e Mouse Down?).
I have a certain Mouse Down? filter event, and if I change this to a non-filtered Mouse Down event then LabVIEW lets me add more event cases as normal. However, I need this to be a filtered event (i.e with the "?"), and in this case, the next I try and add results in the LabVIEW IDE crashing. I can add more events as long as I dont have a filtered event case currently selected, so I suppose this is a work-around.
To clarify, this occurs when I am trying to add events at design time, not at run time.
I tried to replicate this in a new VI, and everything works fine as expected :-(
I can't really attach the VI.
Has anybody else noticed behaviour like this???
nrp
CLA

hi there
thanks for your suggestions
>> A couple of suggestions:
>>1. Try opening the VI on a different computer\LV version.
>>2. Try copying all the code in the VI into another VI and see if this still happens.
>>3. Start deleting pieces of the VI until it stops (or there is nothing left).
I tried options 2 (same crash) and option 3 (crash stops when I delete the Filter events) before I posted the question.
I have tried opening the VI on another PC (also Win2k) with the same version of LabVIEW and it also crashes.
sigh...
I suppose I am just going to have to work around it for now... strange bug...
nrp
CLA

No Usb 2 Drivers In Sp1

According to MSI info about USB 2 drivers should be included in SP1 and are not available for separate download for Win XP.
I got SP1 but no USB 2 drivers could be found i still have the old ones from Microsoft.
I can imagine that many users did not check if they really got USB 2 drivers.
Appreciate any help.

Microsoft added the USB 2 support in Service Pack 4 for Win2k and Service Pack 1 for WinXP
the thing is thet after installing the Service Pack don`t expect Windows to detect the USB 2 ports by itself ... you`ll have to delete them from the Device Manager then run Add/Remove Hardware to force it to detect them.

Problem AFTER installation of MiniSAP 4.6D

Hi SAP Gurus!
I bought the book "ABAP Objects" by Keller/Krueger and it came with 2 CDs for install MiniSAP 4.6D. I successfully installed it. But when I click "Start SAP MBS" opens a DOS window with the following information:
C:MBS>runmbs
C:MBS>set DBMS_TYPE=mss
C:MBS>set DIR_LIBRARY=.
C:MBS>set MSSQL_DBNAME=MBS
C:MBS>rem del pxastat
C:MBS>start /B msg_server.exe pf=MBS_D00.pfl
C:MBS>disp+work.exe break pf=MBS_D00.pfl
dp Ctrl-C enabled
rslgwr1(21): Searching for overlap point in pre-existing SysLog file...
MSG_SERVER died => main: MsSInit
Sat Jan 01 22:38:29 2005
SemSpinning: 2277 usec for 89793 loops -> 39 loops per usec
rslgwr1(21): Searching for overlap point in pre-existing SysLog file...
DISPATCHER died => DpSapEnvInit: DpCommInit
after that: NOTHING. SAPLogon can´t connect. I checked my hosts file and it's OK, checked my services file and it's OK.
I am working with Win2K Server Service Pack 3, installed MiniSAP 4.6D and SAPLogon 46D.
I hope you can help me.
Thank you in advance.

I had the same problem but when i looked a the install instructions says it needed service pack 4

TI4200 drivers

i have G4Ti4200-TD(MS-8870) card and it seems that i cant use any drivers over v30 as it causes win 2k to hang up on startup.
Is there any solutions to this, apart from being stuck with out of date drivers, until i buy a new card?
xp1800
512 pc133
win 2k (all updates)
directx 9 (8 tried also)
G4Ti4200-TD(MS-8870)
also bios on graphics card is upto date
Also any way of uninstalling DX9? coz progs that required DX8 will no longer run X(
cheers in advance

Few methods to try...
Try the 41.07 or 41.09 drivers and also updated your mobo drivers.
Update your Win2k to service pack 3.
Do clean un-installlation first, restart com and re-install the driver again.
By the way, how much power does your PSU supply and what are the programs that requires DirectX 8.1 only at you side? Sounds intruiging to me somehow...
All the Best... :D !!!

USB 2 devices not recognized on Master Farm Mainboard

I have a few problems with a MSI E7210 Master FARM motherboard.
One of these problems is is that I cant use USB 2 Sticks once the Intel drivers are installed. The USB ports on the back work. But on the front it gives an error Unrecognized USB device. Before I install the intel drivers the USB ports on the front work but only in 1.1 mode. I have clear the cmos but it did not help. I'm also missing an menu in the BIOS PNP/PCI Configuration. (See link)
Missing PNP/PCI Configuration
Due missing this options I can't reset the ESCD Configuration data.
I'm really getting a headache and I'm not getting happy with this board. I have made a call to MSI USA with this problem about the missing menu option and the man told me its by design. I hope there is someone here in the forum who has good connections with MSI people so that they could look at this problem. I mustn't be the only one in the world with this problem.

For OS like Win2K or WinXP, you've to update to Service Pack 4 for Win2K and Service Pack 2 for WinXP to get USB 2.0 to work.

Listener service not start automatically after reboot in Win2K server Clust

Hi all,
I set up a two node Server Cluster with Microsoft Windows 2000 server cluster service. Hardware are two HP DL380 servers and HP MSA500 (the shared storage). The cluster's IP address is 10.1.241.65. When I shut down both servers and restart the primary server, the listener server service will not start automatically. The listener log is:
Started with pid=1108
Error listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=10.1.241.65)(PORT=1521)))
TNS-12545: Connect failed because target host or object does not exist
TNS-12560: TNS:protocol adapter error
TNS-00515: Connect failed because target host or object does not exist
32-bit Windows Error: 49: Unknown error
The service is set up automatically start. I suspect the cluster virtual IP is not available immediately after reboot. So I tried setting the Recovery after first failure and second failure to 3 minitues each, and setting up Dependencies of the listener on the cluster service in the Win2K Service panel. Neither worked.
The service can be manually start.
Any suggestion?
Frank.

The command to start automatically the listener is :
lsnrctl start
check the parameters in : <ORACLE_HOME>/network/admin/listener.ora
check the IP address or host name
Joel Pérez

Can't create services port in Win2K

Hello guys:
    I was trying to install IDES on my laptop. The OS is Win2K Advanced Server with sp4. But there was a error when I installed the central instance of iDES.
   It said:'opying c:/winnt/system32/drivers/etc/services to c:/winnt/system32/drivers/etc/services.saptmp
Internal error:a call to syslib failed. system error message:no error'. And i thought it should be something wrong when IDES was trying to create service ports. So I opened the 'service' file in the directory which said in the error message, and found that IDES added one line 'sapmszzz 3600/tcp   #sapsystem message port', it should be more than one line, right?
     I don't know what happened during the installation, and ask for your help to solve this. Anyone will be appreciated!
Best Regards!
Zippo

Andreas, it's not quite correct:
The lines look like this:
sapdb<nn> 32<nn>/tcp
sapgw<nn> 33<nn>/tcp
sapms<SID> 36<nn>/tcp
where <nn> should be 00 in this case...
But the service number has to be unique.
If your services contains for example an entry:
sapmsAAB 3600/tcp
you will fail to add
sapmsAAX 3600/tcp
Therefore you typically have to modify the sapms<SID> entry if you install more than one system with the Number 00 to different values.
sapms<XXX> entries have to be identical on all SAP Systems which should talk to another.
regards
Peter

Minimum user rights to run WLS 8.1 as a Win2k service

Anyone know what the "minimum" user rights are required to run WLS 8.1 as a service
on Win2k?
(no connections to remote server directories etc is required)

"TomL" <[email protected]> wrote:
Anyone know what the "minimum" user rights are
required to run WLS 8.1 as a service on Win2k?Tom,
WebLogic can log on to Microsoft Windows NT 5.0/2000 under the
"LocalSystem" account. This is a local account used by system
processes.
So, your WebLogic Server 8.1 service, running in the context of the
LocalSystem account, would inherit these characteristics:
- This service cannot open the registry key: HKEY_CURRENT_USER...
- This service is allowed to open registry key:
HKEY_LOCAL_MACHINE\SECURITY...
- This service has limited access to network resources,
such as shares and pipes, because it has no credentials
and must connect using a null session...
- If the service opens a command window and runs a batch file,
the user could use CTRL+C to terminate the batch file and
gain access to a command window with LocalSystem permissions...
- This service cannot share objects with other applications
unless they are opened using a DACL or NULL DACL...
- Finally, if this Service requires anything more than a
brief moment to perform necessary initialization, it may
be required to create another thread to do the common
initialization while the main thread continues with
processing.
Brian J. Mitchell
Systems Administrator, MIS
TRX
6 West Druid Hills Drive
Atlanta, GA 30329 USA
http://www.trx.com
email: [email protected]
office: +1 404 327 7238
mobile: +1 678 283 6530

Win2k DB service.

Similar Messages

Maybe you are looking for