Neo 4-F Red PCB Version

Switched my PC on this morning but my D-LED Bracket says that its initionalizing the floppy controller. The top right LED is red ONLY!. Tried to reset the bios by pressing the reset switch but nothing. Tried to take the battery out for 5 hours, nothing. My system is unbootable. Help!...

Quote from: Richard on 13-August-06, 21:09:18
zen62619,
Have you tried one stick of RAM at a time yet?
Take Care,
Richard
Yes, Richard... I have tried one stick of ram.. my ram is fine I have run tests on it in another system. I have even used 1 x 256DDR with no luck. I think I am going to RMA the board because I don't have no other test equipment. All I did was test cpu, memory and graphics card in another machine. My 6800 GS won't work eitha for some reason.

Similar Messages

MOVED: Neo 4-F Red PCB Version

This topic has been moved to AMD64 nVidia Based board.
https://forum-en.msi.com/index.php?topic=99815.0

Quote from: Richard on 13-August-06, 21:09:18
zen62619,
Have you tried one stick of RAM at a time yet?
Take Care,
Richard
Yes, Richard... I have tried one stick of ram.. my ram is fine I have run tests on it in another system. I have even used 1 x 256DDR with no luck. I think I am going to RMA the board because I don't have no other test equipment. All I did was test cpu, memory and graphics card in another machine. My 6800 GS won't work eitha for some reason.

Upgrade linux Red Hat version 4 to Red Hat version 5 on an appliance CWWLSE-1130-K9

Hi.
I have a WCS 5.0 installed on an appliance CWWLSE-1130-K9 to Red Hat Linux 4.0. I need to upgrade to Linux Red Hat version 5 in order to use WCS version 6.0. Does anyone know the procedure to do it?

You do need to have either your WLSE under warranty or a TAC smartnet contract for support on this device as far as product evolution and upgrades.
You may have a support contract since you have a WCS.

K7 Master PCB version

I HAVE AN MSI K7-MASTER AND AN ATHLON XP 1700 CPU, BUT SINCE I CAN'T FIGURE OUT WHAT THE PCB VERSION IS, I CAN'T USE 266MHz FSB. CAN SOMEONE TELL ME HOW I CAN DETERMINE MY BOARD VERSION? THANX.

THANKS FOR THE REPLY, I CHECKED OUT THE LINK WHICH TAKES ME TO MORE LINKS FOR MOTHERBOARDS. FOR K7 MASTER WITH AMD 761 CHIPSET, IT SAYS IT SUPPORTS 266MHz FSB BUT THEN LATER ON IT SAYS PCB VERSION 1.1 ONLY SUPPORTS 266MHz FSB. I HAD CHECKED OUT THIS PAGE BEFORE AND WAS OF NO HELP, IF ONLY MSI COULD MAKE IT CLEAR HOW TO DETERMINE MY PCB VERSION. SENT A MAIL TO MSI SUPPORT LONG TIME BACK AND GOT NO REPLY LIKE MANY TIMES BEFORE AND ENDED UP HERE AT THE FORUMS WHICH PROVIDE MORE HELP THEN NEEDED.

Any difference between motherboard version and PCB version?

I have MS-6340.
In the first page of the manual is written (Version 2.0) and in the scond page written (Manual revision:2.0)
While between the PCI slots of the motherboard is written VER:1 (guess this stands for PCB version)
- Is it possible to have PCB version different than the motherboard allover version?
- And in my case, shall I say that my mobo is version 2.0 with PCB ver. 1? or should consider it as ver. 1?

your motherboards a version v 1
dont worry about what revision the manual is

You better release the 6800 with red PCB...

... because, for modders who have your Neo2 series boards (FIS2R) it would look better.
im not putting a green card into my computer, that'd look shitty as hell. black would be okay too, since my theme is red/black right now. so think about that! uh, and not just because of me haha. but your FIS2R boards are modder boards (NB fan, red PCB), so you should implement this into your graphics card line too. pleeeeze?
Mobo, red
memory Heatspreaders, black
Sound Blaster, Black
9800XT, Red
case, black/silver
^^^^beautyful^^^^
edit: those four "*" mean s h i tt y... geez.

Quote
Well, my sound card is black, my motherboard is black, my memory heat spreaders are platinum. So a black video card would be sweet, but I'll live with green or red.
AOpen make their video cards mostly on black PCBs. They are very good overclockers too- in fact their GeForce FX range is very under-rated.

Help with pcb version

Hi there
can anyone tell me how i find out what PCB version my ms 6378 motherboard is?

Hi
yes thank you I have found out that it is a version 2 motherboard, if I have understood the MS-6378 cpu support status correctly I should be able to upgrade my processor to a
Palomino (0.18u)133/266MHz FSB
Athlonxp 1500+ to Athlonxp 2100+
Could you please check if I am right
regards
Ruth Jay

What's the correct Red Hat version?

Good morning.
We want to install MySAP ERP 2005 on Linux on a IBM xseries 346 64 bit.
I've seen that Red Hat EL 4 is certified by SAP
In this page, http://www50.sap.com/linux/platforms/index.asp, is also specified the kernel to use.
But I haven't find any other suggestions on http://service.sap.com/pam
I'm a little bit confused about the correct version: AS, ES... 4.2, 4.4, 5?
Can anyone please give me a suggestion about the correct version to choose??
Regards,
Luca

This is the java version that I've installed:
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 2.2)
IBM J9SE VM (build 2.2, J2RE 1.4.2 IBM J9 2.2 Linux amd64-64 j9xa64142-20060824 (JIT enabled)
J9VM - 20060802_1551_LHdSMr
JIT - r7_level20060707_1808ifx1)
I've not yet set JAVA_HOME variable, nor PATH. Any other "customization" to do?
This is the last part of the "import.monitor.java.log" when start errors:
Import Monitor jobs: running 3, waiting 31, completed 38, failed 0, total 72.
Loading of 'SAPAPPL0_9' import package: ERROR
Import Monitor jobs: running 2, waiting 31, completed 38, failed 1, total 72.
Loading of 'SAPAPPL1_9' import package: ERROR
Loading of 'SAPAPPL2_5' import package: ERROR
Import Monitor jobs: running 0, waiting 31, completed 38, failed 3, total 72.
Import Monitor jobs: running 0, waiting 31, completed 38, failed 3, total 72.
Import Monitor jobs: running 1, waiting 30, completed 38, failed 3, total 72.
Import Monitor jobs: running 2, waiting 29, completed 38, failed 3, total 72.
Import Monitor jobs: running 3, waiting 28, completed 38, failed 3, total 72.
Loading of 'SAPSSEXC_6' import package: ERROR
Import Monitor jobs: running 2, waiting 28, completed 38, failed 4, total 72.
Loading of 'SAPSSEXC_2' import package: ERROR
Import Monitor jobs: running 1, waiting 28, completed 38, failed 5, total 72.
Loading of 'SAPAPPL0_5' import package: ERROR
Import Monitor jobs: running 0, waiting 28, completed 38, failed 6, total 72.
Import Monitor jobs: running 1, waiting 27, completed 38, failed 6, total 72.
Import Monitor jobs: running 2, waiting 26, completed 38, failed 6, total 72.
Import Monitor jobs: running 3, waiting 25, completed 38, failed 6, total 72.
Loading of 'SAPAPPL0_1' import package: ERROR
Import Monitor jobs: running 2, waiting 25, completed 38, failed 7, total 72.
Loading of 'SAPAPPL0_8' import package: ERROR
Import Monitor jobs: running 1, waiting 25, completed 38, failed 8, total 72.
Loading of 'SAPAPPL0_6' import package: ERROR
Import Monitor jobs: running 0, waiting 25, completed 38, failed 9, total 72.
Import Monitor jobs: running 1, waiting 24, completed 38, failed 9, total 72.
Import Monitor jobs: running 2, waiting 23, completed 38, failed 9, total 72.
Import Monitor jobs: running 3, waiting 22, completed 38, failed 9, total 72.
Loading of 'SAPAPPL0_4' import package: ERROR
Import Monitor jobs: running 2, waiting 22, completed 38, failed 10, total 72.
Loading of 'SAPPOOL' import package: ERROR
Import Monitor jobs: running 1, waiting 22, completed 38, failed 11, total 72.
Loading of 'SAPSDIC_1' import package: ERROR
Import Monitor jobs: running 0, waiting 22, completed 38, failed 12, total 72.
Import Monitor jobs: running 1, waiting 21, completed 38, failed 12, total 72.
Import Monitor jobs: running 2, waiting 20, completed 38, failed 12, total 72.
Import Monitor jobs: running 3, waiting 19, completed 38, failed 12, total 72.
Loading of 'SAPSSEXC_11' import package: ERROR
Import Monitor jobs: running 2, waiting 19, completed 38, failed 13, total 72.
Loading of 'SAPSSEXC_8' import package: ERROR
Import Monitor jobs: running 1, waiting 19, completed 38, failed 14, total 72.
Loading of 'SAPAPPL1_11' import package: ERROR
Import Monitor jobs: running 0, waiting 19, completed 38, failed 15, total 72.
Import Monitor jobs: running 1, waiting 18, completed 38, failed 15, total 72.
Import Monitor jobs: running 2, waiting 17, completed 38, failed 15, total 72.
Import Monitor jobs: running 3, waiting 16, completed 38, failed 15, total 72.
Loading of 'GLFUNCA' import package: ERROR
Import Monitor jobs: running 2, waiting 16, completed 38, failed 16, total 72.
Loading of 'SAPAPPL1_2' import package: ERROR
Import Monitor jobs: running 1, waiting 16, completed 38, failed 17, total 72.
Loading of 'SAPAPPL0_10' import package: ERROR
Import Monitor jobs: running 0, waiting 16, completed 38, failed 18, total 72.
Import Monitor jobs: running 1, waiting 15, completed 38, failed 18, total 72.
Import Monitor jobs: running 2, waiting 14, completed 38, failed 18, total 72.
Import Monitor jobs: running 3, waiting 13, completed 38, failed 18, total 72.
Loading of 'SAPSSEXC_13' import package: ERROR
Import Monitor jobs: running 2, waiting 13, completed 38, failed 19, total 72.
Loading of 'SCPRSVALS' import package: ERROR
Import Monitor jobs: running 1, waiting 13, completed 38, failed 20, total 72.
Loading of 'SAPAPPL1_6' import package: ERROR
Import Monitor jobs: running 0, waiting 13, completed 38, failed 21, total 72.
Import Monitor jobs: running 1, waiting 12, completed 38, failed 21, total 72.
Import Monitor jobs: running 2, waiting 11, completed 38, failed 21, total 72.
Import Monitor jobs: running 3, waiting 10, completed 38, failed 21, total 72.
Loading of 'SAPAPPL0_3' import package: ERROR
Import Monitor jobs: running 2, waiting 10, completed 38, failed 22, total 72.
Loading of 'SAPSDOCU' import package: ERROR
Import Monitor jobs: running 1, waiting 10, completed 38, failed 23, total 72.
Loading of 'SAPAPPL1_3' import package: ERROR
Import Monitor jobs: running 0, waiting 10, completed 38, failed 24, total 72.
Import Monitor jobs: running 1, waiting 9, completed 38, failed 24, total 72.
Import Monitor jobs: running 2, waiting 8, completed 38, failed 24, total 72.
Import Monitor jobs: running 3, waiting 7, completed 38, failed 24, total 72.
Loading of 'SAPSLOAD' import package: ERROR
Import Monitor jobs: running 2, waiting 7, completed 38, failed 25, total 72.
Loading of 'SAPSSEXC_1' import package: ERROR
Import Monitor jobs: running 1, waiting 7, completed 38, failed 26, total 72.
Loading of 'SAPSPROT' import package: ERROR
Import Monitor jobs: running 0, waiting 7, completed 38, failed 27, total 72.
Import Monitor jobs: running 1, waiting 6, completed 38, failed 27, total 72.
Import Monitor jobs: running 2, waiting 5, completed 38, failed 27, total 72.
Import Monitor jobs: running 3, waiting 4, completed 38, failed 27, total 72.
Loading of 'SAPDFACT' import package: ERROR
Import Monitor jobs: running 2, waiting 4, completed 38, failed 28, total 72.
Loading of 'SAPDDIM' import package: ERROR
Import Monitor jobs: running 1, waiting 4, completed 38, failed 29, total 72.
Loading of 'SAPUSER' import package: ERROR
Import Monitor jobs: running 0, waiting 4, completed 38, failed 30, total 72.
Import Monitor jobs: running 1, waiting 3, completed 38, failed 30, total 72.
Import Monitor jobs: running 2, waiting 2, completed 38, failed 30, total 72.
Import Monitor jobs: running 3, waiting 1, completed 38, failed 30, total 72.
Loading of 'SAP0000' import package: ERROR
Import Monitor jobs: running 2, waiting 1, completed 38, failed 31, total 72.
Loading of 'SAPUSER1' import package: ERROR
Import Monitor jobs: running 1, waiting 1, completed 38, failed 32, total 72.
Loading of 'SAPDODS' import package: ERROR
Import Monitor jobs: running 0, waiting 1, completed 38, failed 33, total 72.
Can you have some suggestions to solve the problem?
<b>Can I retry to resume installation from the point 17 or I've to start from the beginning and clear my last installation?
</b>

K8N NEO Platinum 4 Red LED at Startup

I installed a new MSI K8N Neo Platinum mainboard in my computer in December 2005, and my computer has been a pain ever since. My problem is 85% of the time when I turn the power on it just won't boot up, I get 4 Red LED lights. If I shut it off and on half a dozen to 20 times. During one of those times it will bootup normal and work great. Shutdowns are normal.
My Family hates this and won't use it. This computer has been nicknamed the MSI Little Witch. I have had it down to barebones out of case with just graphic card, 1 memory stick, IDE harddrive, keyboard and mouse, it will do same thing. I've unplugged and replugged everything countless times. It still does it. I have tried Maxtor, Samsung, and Western Digital hard drives with fresh install of Windows XP Pro, it still does same thing. I have alternated memory sticks, same thing. It will warm reboot as long as I don't powerdown, but if I shut the power off it will not reboot until it cools down about 20 minutes. Then I can go through the same startup problems as I normally have. I have not done any overclocking.
Anyone have a fix to this fustrating problem?

I have the same problem with my K8N Neo Platinum. Except mine seems to occur after the motherboard has not had power after sometime. For example, it happened every time I moved my computer when I moved into and out of my dorm room. I don't know if its the same "cooling down" time you're talking about, but what usually fixes it for me (at least temporarily) is killing the power to the machine while it is on. Regular soft resets won't work for many tries, but when the computer is on with all 4 red LEDs i'll flip the power switch on the power supply. That usually makes it work fine. Also another thing that seemed to intermittently trigger it is changes to the BIOS. A CMOS reset would not fix that either. I would have to flip the power switch and kill the power. Then after starting it
up again it would be okay. I have also tried multiple combinations of different cpus, memory sticks, and video cards. I also made sure there were no shorts to ground anywhere.
Also after a year of solid operation (with the exception of this problem) I started to get Machine Check Exception BSODs in XP. I think this was because of a possible bad stick of RAM, because that seemed to cause lockups in the way beginning of the Windows setup (where it is loading files such as Windows Executive, etc). When I removed it and put another stick in, the windows installation would go fine. But, that did not fix the issue with this motherboard.
I've had so many problems with the multiple K8N Neo Platinums I have purchased. This is absolutely ridiculous I'm extremely POed at MSI for the widespread K8N series problems. I am usually very tolerant to companies when they have problems with products because I understand that problems and glitches can easily occur in mass production and design. It is virtually impossible to make a "perfect" product from the start. But the lack of response and concern from MSI about this is ridiculous. MSI did make an excellent motherboard here--if you can get a working one.

What is the difference between P35 Neo2-FR PCB versions?

Hi there
I have a PC built with a P35 Neo2-FR motherboard, PCB v1.1.
I'm just about to make another PC up using this board and it has PCB v1.2.
What is the difference between these? are there other versions and what is the change log between these?
Cheers

Hello Stonedofmoo,
there is no crucial difference between PCB v1.1 and v1.2. BIOS Versions are the same and there are no differences in functionality either.
The only difference I can see from looking at pictures of both revisions, are two extra capacitors next to the Realtek SoundChip on Rev. 1.1 boards.
If you want more detailed technical information, you will have to contact MSI directly and hope that they can give you a better answer:
-How to Contact MSI for Help

Large PNG shows up red in version 9.0.115.0

For this project we did we used a very large PNG in the
background (about 9800px in width). I know it's not the most
efficient way of doing this... next time we'll probably chop it up
into smaller pieces.
The problem as of playerversion 9.0.115.0 is that this large
PNG shows up red in the background. I've tested it in FIrefox with
flashswitcher and in any version lower than this an higher than 8
it shows up perfectly. The problem seems to appear on a Mac as well
but i don't have one i can use to test this on.
I've put up a test version of the problem here:
http://clients.merge-media.com/ara/test/test.html
You can download the test fla here:
http://clients.merge-media.com/ara/test/test.zip
(25mb)
Does any of you guys know if there's a workaround for this or
maybe something to fix this?
Thanks in advance,
J.

Did anyone open a support case for this?
http://www.adobe.com/support/contact/
Important Note: These online forums are for user-to-user
discussions of Adobe products, and are not an official customer
support channel for Adobe. If you require direct assistance, or
prefer to contact Adobe support staff directly, please contact
Adobe support.

K8N Neo-FSR 4 Red LEDS

I put together an amd64 system:
K8N Neo-FSR
AMD Athlon 64 3000+
1024mb corsair valueselect (2x512)
When I power on, I get 4 red leds on the dbracket, which is supposedly a damaged or incorrectly installed cpu. I am 99% sure that both of the cpus that i tried were good, but I am 100% sure that one of them was. I also tried reseating them a few times. Is there anything else 4 red leds means?
Also, the computer turns on with the powers supply switch and the power/reset switches don't work at all even though they are plugged in to the correct places. Anyone got any ideas?

I had the exact same problem. Thought it was the CPU, so returned it and got a new one, and the error continued. Here's how I got it to stop:
Take EVERYTHING off the mobo. All the PCI/AGP cards and the ram. You can leave your drives hooked up, but unplug the power from them.
Then, try to reboot it. When I did that, it finally got past the 4 LEDs and gave the memory error leds. So I put in the ram, and it gave me the next error. So on and so forth. I kept putting in whatever piece of hardware it was crying about, until it got all the way through, at which point I put in my extra stuff (sound card, tv card). Yes, it's a pain in the ass.
When I was putting them back in, the only thing I did different is I put my tv card in the slot above the orange PCI slot (the one on the bottom that is "enhanced"). I'm wondering if that wasn't the problem to begin with.

Red Frames - Version 7.2.1

I know there have been a lot of discussions about red frames in CC, I think I've read them all and tried every solution, here's my situation in case there is something that I missed.
I work with many long (2 hour plus) .mov files with the AVdn codec and after an upgrade to CC on Friday these files now have red frames every 5 minutes or so (maybe more) when opened in anything CC.
I'm using 7.2.1, have tried deleting my media cache, have tried opening, closing, reopening, restarting, exporting, copying, pasting, and nothing works.
Is there a solution that I missed BESIDES the following:
Re-exporting all my files with a different codec and using Media Encoder CS6
Rolling back to a prior version

Hi William,
Can you update Premiere Pro to Premiere Pro CC (7.2.2) or CC 2014? That should solve your issue.
Thanks,
Kevin

Red:NWDS version

Hi all,
I have some bit confusion in nwds..actually nwds has some version such as 7.0, 7.1,7.2 and 7.3....
For instance....nwds 7.0 support jdk 1.4 only. in similar way i want to know about nwds version and which are the jdk version will support for the particular nwds..
can you suggest me regarding this...
Regards,
Dharmaraj

Dear Dharmaraj
Better yor have same version and SP Level as SAP J2EE Server for NWDS Developer Studio.
Even It is compatible for SAP Server Version 7.0, 7.1, 7.2, 7.3 with NWDS NWDS Developer Studio 7.0, 7.1, 7.2, 7.3 respectively.
For more details you can refer to installation guide and production availability matris in the service market place for more details.
Hope it will helps
Best Regards
Arun Jaiswal

Difference between MSI 945PL NEO version 1 and 2

Hello,
My computer just died, I believe the motherboard is dead. I have a spare MSI 945PL NEO motherboard on hand. I would like to use my CPU from the dead machine with MSI motherboard. The CPU is intel Core 2 Duo 2.2 GHz. I looked on MSI website. The MSI 945PL NEO PCB v2 support Core 2 Duo CPU but not the PCB version 1. What is the difference between PCB version 1 and 2? What I can see is less RAM slot and faster FSB on V2. I want to know if I put my Core 2 Duo CPU into the motherboard, will it boot up? or will it damage the CPU? I do not mind the performance if the system can work together.
Thanks

We can't tell you which specific changes have been made to PCB 2.2 but in fact there is no Core 2 Duo support for PCB 1.0. As I still don't know if you have 1.0 or 2.2 I can't tell you what happens with your board. None the less it will most likely simply don't work if you try on 1.0 (board does not post). Using an unsupported cpu is a gamble: >>How to check CPU support<<

Neo 4-F Red PCB Version

Similar Messages

Maybe you are looking for