'Assign resources to all ISA' Error (Neo2 Plat.)

finally put all my new components together on my new MSI Neo2 Platinum board. however, its locking up shortly after boot. Using the MSI D-Bracket, it's telling me its locking on the 'Assign resources to ISA' step. my component are below, but the only things i have plugged in or powered on are the SATA HD's, RAM, Vid Card, SB Audigy2.
amd athlon64 3000+
512MB Kingston HyperX 3200
12x8x16 Plextor DVDRW
72x Kenwood CDROM
40x12 Plextor CDRW
2x Western Digital 80GB HD (SATA)
Albatron geforce4 4600
SB Audigy2
any ideas as to what would be causing this? ive owned several MSI boards and never seen this error.

got it to get past that stage, seems it was a cdrom. however, ive run into more problems with this setup than anything ive ever worked on. still working on it now. glad i didnt take apart this computer yet...

Similar Messages

Assign Resources to all ISA Error

Hey guys... Since this is the most indescriptive error ive ever seen im gunna need some help. Just built the computer and only have a master harddrive, and videocard in there. The D-Bracket is reading the "Assign Resources to all ISA" error which doesnt seem to stop the computer from doing things, but i can hear it crunching away at something. If i let it sit it will eventually respond like 10min later at which point it continues to run incredibly slow. I have tried clearing the CMOS and it works, but does not solve the problem. The keyboard is the only device hooked up and it is nonUSB. I know the keyboard is good because it does repsond to keypresses like i said, just very very very slowly. Any ideas on what is causing this and what i can do to fix it?
Thanks
BTW
Athlon 64 3000+
K8N Neo Platinum
Corsair TwinX 3200
ATI x800XT
Western Digital 80gig 7200RPM (set as master)
No Floppy

Problem Solved
Heres what the problem was for those of you that also dont understand cryptic messages. I had my HD hooked up as the only device on the cable set as Master. Apparently the motherboard doesnt like it set that way. To solve the problem (in this case) just set the jumper to Cable Select and everything will be fine. The drive is a Western Digital so it might just be localized to that drive. I saw in my searches for a solution that 2 people had the same problem but caused by their cd drive. So if you happen across this error, check your jumpers it seems to be the root of the problem from what ive gathered/experienced.

Assign Resources to all ISA

Arg, I am getting this erro,Assign Resources to all ISA,r after switching video cards in my computer. It only happens with the X800 pro and not the 9800 pro. I have gone back and forth between the 2 a few times. With the same results. BTW this is on a k8n neo plat 3400+, 3700eb, true control 550 24A-12v 40A-5V 32A-3.3V. I also have audigy 2 and rocket raid 404 pci cards connected.

well Now I can get it to boot, but still no video. It makes a funny beep when the upper left corer of the d bracket is green.

Assign Resources to all ISA / Possible VGA Problem

Pentium 4 2.8GHz
MSI VIA PT8 Neo-V
2x elixir 512mb DDR400
6600LE AGP8x 256MB TV-OUT DVI
Maxtor Diamond Max Plus 9 80GB ATA 133
Raid Card (no info)
Creative Labs Soundblaster Audigy LS
Chieftec 340W 230V
XP Pro
I recently had problems with my machine where it kept freezing during windows start up. I changed hard drives, managed a new XP instalation. But then it started freezing again. The last couple of tiems I turned it on, it wouldn't do anything except report a disc error.
I have removed every device in the machine, everything 1 by 1. Plugging only one thing in, but I get the same light on the d bracket every time. The error lights means 'Assign Resources to all ISA'. I have tried clearing the CMOS with and without devices in.
I also get a series of bleeps, which I think is 2 very quick bleeps, followed by 8 short bleeps

well Now I can get it to boot, but still no video. It makes a funny beep when the upper left corer of the d bracket is green.

Assign Resources to all ISA ..no post

Hi,
I can't search for this topic on this forum, I get an error response every time.
MS-7030 with a Atllon 64 3200+ on an anted true power 430 supply, one WD hard drive and a 5700 Ultra video card. 2 PNY 512MB sticks on 2 and 3 slot.
Get error code Assign Resources to all ISA , when booting up. I get to the screen saying "tab for POST, del for BIOS setup" but can't do anything from there.
Is the MB bad? anybody else solved this problem?
Help would be very, very greatly appreciated.
Thanks,
Alfred

Thanks very much for you reply.
I finally found the problem. I'm embarrased to say, I forgot to change from master to CS on my WD hard drive.
thanks,
Miron

Assign resources to all ISA - hang

Hi all,
i recently made 2 new computers with this specs:
K8N Neo2Platinum
A64 3200+ (939)
A-data 2*512 MB 400 MHz
Ati X800 PRO
Maxtor SATA 200 GB
PSU: no name 350 W, +3,3 - 15A, +5 - 15A, +12 - 9A
or alternative (i have changed it), no name psu, 300W, +3.3 - 28A, +5 - 30a, +12 - 15A
One of this computers have some instability problem a now even wont start up. D-led shows: Assing resources to all ISA. I would like to ask what does it mean?
I know my psu are creapy (i hate these garage sales companies, which sell around here ). First i thing the problem will be in psu, but the second computers have the same specification and its running perfectly.
Please help me.
dwayne

Quote from: lef on 03-September-06, 05:21:28
Hi , i realy need to know is what that D-led statment: assing resources to ISA means . Why? Becouse this problem realy @!?#ed me Please Help me. my Pc is running normaly before and now D-led show assing resources to ISA ... LOL i hawen´t ISA ! .The same trouble as dwayne_stone .I run pc with only memory graf card and CPU. Thanx
Every PC still has ISA resources: keyboard, mouse, text-mode video, floppy drive, RTC, COMs, LPT... As far as I see, none of you have mentioned BIOS version nor whether you tried to clear CMOS nor whether the keyboard lights flash or you get a beep. The "resources" the msg refers to are IRQs, I/O addresses and possibly DMA channels which are all fixed for the system ISA devices. Start by disconnecting all non-essential devices; next try swapping external devices, e.g. keyboard, mouse... just use a different keyboard & mouse and then try switching the interface PS/2<->USB.

Assign resources to all ISA and garbled graphics on boot.....any suggestions?

Subject says it all. I boot up and get the above mentioned error from the LED bracket. If i could see clearly enough i could mess around in the bios.... I just replaced the MOBO, PSU and video card and this is the first attempt at rebooting it with the new components (exact same components just factory new).
UPDATE: I can get it to boot up to windows now but the graphic display is still messed up although i can see when im in windows. When I use an old video card (geforce 2) It works pretty much like normal with no graphic errors. With either video card in I get no LED errors when im finally in windows.
Could the new motherboard and video card with old HDD and winxp loading on it be causing the graphics issues? I will try a fresh install of winxp and see if that fixes it. Until then, any suggestions or comments would be appreciated. Thank you!

Thanks for the replies. All the components i just put in were the same exact components, I just did RMA for replacements because I had a power surge or something and things went bad. Maybe I just got lucky with the maddog crap psu for a year. I did have a thermaltake 420 watt PSU but it caused problems and I tried the maddogg and it worked fine so I assumed it was better quality than thermaltake. Would poor PSU cause the graphics card to display funky? makes since that I put in the small video card and it works fine....maybe ill try putting in the RMA'd thermaltake 420 PSU again. Thanks again
Also...No, I haven't done a clean install of windows yet because I wanted to start up and save some important data from the HDD then I was planning on doing a clean install after that.

Error Message while assigning resource to work orders

Hi All,
We have the MRS tool integration with service work orders for scheduling. When we assign the resources with 9 hours as duration there is no error. When we allocate more than 9 hours for some resources, not all, we receive the error message as
" Duration    29,160 S is not a multiple of 15 minutes " . These duration of secs varies when the duration is varied > 9 hours.
We have checked the planning board profile configurations but nothing seems to be visible. In customising we have the following settings,
Time Granularity                 : 15 mins
Min duraiton of assignments: 15 mins
Automatic Assignment Splits
Min duraiton           : 2 hours
Max overtime hours : 2 hours
Max Ratio is %       : 75
Can anyone throw some light on this?
Regards,
Selva

Hi Anil Satya,
The MRS is integrated with Service Order types and the operations are selected for each order then the assignment of hours takes place in MRS.
If the assignment is done for 9 hours then there is no such error. These errors are very specific to some personnel numbers ( not for all ) where the duration is more than 9 hours.
Is there any availability of resources for this operation / job through configuration settings? Why such a question is some resources even when 15 or 20 hours is assigned , no errors exists.
Hope this explanation provides a better clarity.
Regards,
Selva

Scared to get a Neo2 Plat with all the problems here!

I plan on getting a Neo2 Plat, but scared from all these problems that people are asking about...I dont want problems :(

Quote
kweckstrom I'm still a little confused you claim to have been building computers since computers were practically invented but you coulden't figure out how to get a new 939 board up and running reliably?? It's really not that hard.. not like the P90 (the pentium that didn't run)
1 you check for compatability,
2 you buy your parts,
3 you put it together..
4 it runs.
First of all, you should read an entire post before replying. You must not have read it, because I obviously DID figure it out.
If you look at the compatibility list for the MSI board, it's abysmal. They test VERY few modules, and they haven't tested anything newer. Newer modules (like the newer Corsair XL's or Micron Ballistix) remain untested, and aren't likely to BE tested "officially". The Corsair 3200LLPT's worked fine in my P4 rig. They worked fine on the Gigabyte 939 NF3 board. One can reasonably expect that they would have worked fine on the MSI, after all it's the same chipset.
But no, they didn't. Not even after upgrading my power supply. Yet if I slap all this stuff together on the gigabyte board, all was fine and dandy, even on a PS that only delivered 18A on +12v.
When I tried out the ballistix, I ran into even worse problems, even after ignoring SPD and upping voltage to it's rated 2.8v. But after upgrading my Power Supply, those problems went away and the system is now rock solid and stable.
I'm an older guy with a wife and 2 kids, not to mention a full-time career as a network engineer. I don't have tons of nights and weekends to work through nagging compatibility or stability issues. That's why I say I wouldn't put myself through that mess again.
Quote
If your buying enthousiast grade parts expect to do a little research first because it's a fact there are more untested parts and there will be some incompatabilities but it's absolutely no different than any intel platform of the same age..
Maybe you should have had someone with a little more time and skill build a system for you??
Then you may have been able to aviod these PEBCAK errors lol
Taking the high road, I see
You should actually read my post next time. I solved the problem long ago. I'm simply saying that this platform is an annoying one because there are tons of incompatibilities that lead to stability issues. That's fact, and you aren't much of an engineer if you dispute it.
What you say about intel systems of the same age is completely untrue. You'd have a hard time finding an intel board that's incompatible with DDR2 by any specific vendor. You'd also have a hard time finding any intel boards that have quirks with PCI Express cards. You'll also have a hard time finding any Power Supply compatibilities with LGA775, because a specific type of power supply is required (dual-rail with PCI-E headers). Sorry, you're wrong here.
On the Athlon64-939, out of the gate you'll have problems with certain hardware.
Take the Geforce 6800's.... The 6800's don't require 2D and 3D clock speeds to be identical on a P4 system. The bios by default doesn't normalize clock speeds for 2d and 3d, because a 425mhz 2D core value uses power needlessly and doesn't make much sense. But if you're on the Nforce3 platform, you're FORCED to set them identically or your 3d games will stutter and eventually freeze.
There's people with issues on Nforce3 using Fast Writes. Some people have to disable them. You simply don't need to do this on intel.
There's people with issues using Audigy cards (the original Audigy 1). They cause BSOD's. This doesn't happen on Intel systems. They work fine there. (Audigy 2 is unaffected).
If someone's doing research into problems regarding the Athlon64 platform, i'm not going to blow sunshine up everyone's butt. I'm going to tell it like it is. I'm not married to any specific vendor, and i'm not someone who's going to insult someone's system building or research skills because he ran into problems with his latest build.
These problems are VERY real, and if you read this board it's LOADED with people who are having issues with stability. You shouldn't be quick to blame their research or skill with a screwdriver.

Does Neo2 Plat bios 1.4 official contain all the "updates" in the beta bios 1.36/1.37

given the minimal info on change logs in the beta bios for the Neo2 plat..does the official 1.4 bios contain the updated in 1.36b and 1.37b
thus is 1.4 bios the best bios...

1.4 is the latest official bios. Normally new bioses are cumulative and include the previous fixes.
Working fixes of bios 1.36 and 1.37 sould even be included in version 1.3, because this is the final version of the 1.3x betas.

Getting dump while assigning resource to role

Hi,
We are using BAPI_BUS2177_STAFFING_ADD to assign resource to role.
It is assigning first resource to first role in first project. And giving dump for next resource to role assignment for the same project.
Short dump description is like as follows:
The exception 'CX_DPR_FATAL_ERROR' was raised, but it was not caught anywhere
along
the call hierarchy.
Since exceptions represent error situations and this error was not
adequately responded to, the running ABAP program
'CL_DPR_AUTHORIZATION_SERVICES=CP' has to be
terminated.
The problem is of "COMMIT". I ma not understanding where to write exact commit. Even if we are commiting at project level it is giving dump.
Could you please give any suggestion on it.
Thanks & Regards,
Anil Salekar

Hello Kaixiang,
When you add staffing to project then commit after each resource assignment. That will avoid the dump.
Use:
CALL FUNCTION 'BAPI_CPROJECTS_COMMIT_WORK'
TABLES
return = it_return.
Note: Re award if useful
Thanks,
Appasaheb..

Need urgent help :'The requested resource does not exist error'

Hi All,
I am getting 'The requested resource does not exist error' when trying to acess http://machinename:50000/irj
Even when i access http://machinename:50000, i get the same 'The root directory does not exist' error. I checked in visual admin, there is no other application deployed except my application.
Any clues? Pls help
thanks
bhawna

HI ,
Did succeed to solve your problem. I am running into same problem.
Any help is welcome.
Thank u very much.

How to identify what are all the errors appears in process chain,

Hi all,
i have a process chain running, but i want to find out what are all the errors that the process chain has thrown
thanks
pooja

Hi Pooja,
Errors in monitoring:
SID error
Reason: If the corresponding master data is missing for the particular transaction data.
         1. Check for the load timing for the respective master data, if it less than an hour then make the request red and repeat the ip.
         2. If the data is loaded to PSA then you have to delete the request from target and manually push the data to from PSA.
         3. If we are required for selective update then note down the info source from header and find it in RSA1,select the one with Single as postfix.
         4. Goto data selection tab and change the range.
Tip: change the last 4 digits for from to 0000and the last 4 digit for to     9999.
        5. Repeat the ip.
         6. In case only of failure in one target goto RSA1 find the PSA, put he request no. and reschedule it.
Note: IF PSA is present never make the request red rather delete it.
Replication error
Reason: Data source replication Failed.
         1. In order to handle this error you should be known to IP, info source and source system.
         2. Goto RSA1, find the data source in the source sys tab.
         3. Right click on the data source and replicate it.
         4. Since all the transformation rules pertaining to this data source need to be reactivated so go to SE38 and execute rs_transtru_activat_all, data source and sys name.
         5. Delete the red request from the target.
Update R not supported
Reason: The corresponding initialization flag for the ip is lost.
         1. Goto header click on the ip and goto schedule tab and click initialize in the source system, whatever screen appears delete the only request present(the initialization flag).
         2. Goto RSA1, find the ip in the info source (one with the Adhoc initialize flag).
         3. Goto update tab and select Initialize delta process try going for with data transfer.
         4. Reschedule the IP.
Duplicate Record Error
Reason: Duplicate error records for the loaded master data.
         1. Goto info package via header or via RSA1.
         2. Goto processing tab and change the ip setting, selecting only PSA and ignore duplicate records and re run the ip.
         3. Do remember to change the ip settings back to the original once after the second step.
ODS activation failure
Reason: Prerequisites for ODs activation not satisfied i.e. unique key.
         1. Goto maintain variant.
         2. Check for the QM status of the requests in the target they should be green.
         3. Then click the ODS activation tab.
         4. In the screen which appears put the requests for which ODS activation failed.
         5. Activate these and keep on refreshing them until status reverts from green,
Remember to refresh these requests one at a time.
         6. If requests are red then delete them from target.
         7. Reschedule the IP.
Note: Never Try activating ODS manually if it is Y1.
Aggregate Rollup error
Reason: No aggregate found for the respective rollup.
         1. Click on the variant in which the error occurred.
         2. Goto chain tab and copy the variant and instance.
         3. Run the nestle provided program YBW05.
         4. Put in info in there and put the status as g green.
         5. Execute and refresh the status.
Lock issue
Reason: The same ip is been locked by other user or may be used by other process chain.
         1. We can see the locked entries and in the transaction SM12.
         2. Wait for the other process to get complete once the ip loads to target in that process then there is no need for running it for the process.
         3. In other case make the request red, when PSA is present then goto environment tab ->schedule->initiate update.
         4. In the box appears select update in the background.
         5. And the manually update the failed IPs by selecting manual update in the context menu.
Alfa confirming value error, Time conversion error, Chain didnt start, Delay due to long running job, Poor system performance,Heirarchy node exist in duplicate.
Reasons:
Alfa confirming error: Data format mismatch.
Time conversion error: Date, time format mismatch.
Chain didnt start: A scheduled chain didnt triggered at the prescribed timing.
-For all the above error we have to raise a ticket.
Idoc or TRFC error
Reason: An Idoc is been stuck somewhere.
         1. Reload the Master Data manually again from Info-package at RSA1.
         2. Release the Idoc.
         3. In the source system level got environment->transaction->Transaction RFC or Data ware housing level.
         4. In the Screen if the status is Transaction Recorded it means its stuck goto edit and click Execute LUW or press F6.
         5. If status is Transaction executing then it means its fine wait.
         6. Or raise ticket.
Error Due to short Dump
Reason: Error due to Short dump could be due to many reasons i.e. memory, table space, lock, error record, page allocation, failed change run.
Process terminated in the Source system.
           Reason: Sometimes we face that a load has failed due to job Termination at Source System.
      This happens due to unavailability of the source system or some connectivity problem between source and target systems.
1.      Make the request red.
2.      Delete the request from the data target.
3.      Reschedule the ip.
4.      If still the job fails raise the ticket.
And also check in following links:
Process Chain Errors
/people/mona.kapur/blog/2008/01/14/process-chain-errors
Common Process chain errors
For Data Load Errors check this blog:
/people/siegfried.szameitat/blog/2005/07/28/data-load-errors--basic-checks
Pls assign points if it helps u,
Thanks & Regards,
Madhu

All validation error from saxParser.parse

I am getting just the 1st error but I want all the errors in the 1st pass itself.
Attaching the code for reference also.
?would really appreciate you suggestion.
==code---
public class EDITExtractSchema {
static Document document;
public void validateXMLVOusingXSD(String str)
try {
//create a SchemaFactory capable of understanding W3C XML Schemas (WXS)
SchemaFactory factory = SchemaFactory.newInstance("http://www.w3.org/2001/XMLSchema");
//Set the error handler to receive any error during Schema Compilation
XMLErrorHandler errorHandler = new XMLErrorHandler();
factory.setErrorHandler(errorHandler);
//set the resource resolver to customize resource resolution
//factory.setResourceResolver( new MyLSResourceResolver());
// load a WXS schema, represented by a Schema instance
File schemaFile = new File("C:/Temp/project2-CorrVO/XSDs/TaxExtract5498DetailVO.xsd");
Schema schema = factory.newSchema(new StreamSource(schemaFile));
SAXParserFactory spf = SAXParserFactory.newInstance();
//spf.setNamespaceAware(true);
//spf.setValidating(true);
spf.setFeature("http://apache.org/xml/features/validation/schema-full-checking", true);
//Just set the Schema instance on SAXParserFactory
spf.setSchema(schema);
//Obtain the SAXParser instance
SAXParser saxParser = spf.newSAXParser();
//parser will parse the XML document but validate it using Schema instance
//saxParser.parse(new File(str), myHandler);
saxParser.parse(new File(str),new MyDefaulyHandler());
}catch(ParserConfigurationException e) {
System.out.println("ParserConfigurationException-" + e);
}catch (SAXException e) {
System.out.println("SAXException-" + e);
catch (Exception e) {
System.out.println("Exception-" + e);
/*// output the errors XML
XMLWriter writer = null;
try {
writer = new XMLWriter(OutputFormat.createPrettyPrint());
} catch (UnsupportedEncodingException e) {
System.out.println("validate error" + e);
e.printStackTrace();
try {
writer.write(errorHandler.geterrors());
} catch (IOException e) {
System.out.println("validate error" + e);
e.printStackTrace();
//implement error handler
public static class XMLErrorHandler implements ErrorHandler {
private boolean valid = true;
public void reset() {
// Assume document is valid until proven otherwise
valid = true;
public boolean isValid() {
return valid;
public void warning(SAXParseException exception) throws SAXException{
System.out.println("Warning: " + exception.getMessage());
System.out.println(" at line " + exception.getLineNumber()
+ ", column " + exception.getColumnNumber());
System.out.println(" in entity " + exception.getSystemId());
valid = true;
public void error(SAXParseException exception) throws SAXException{
System.out.println("Error: " + exception.getMessage());
System.out.println(" at line " + exception.getLineNumber()
+ ", column " + exception.getColumnNumber());
System.out.println(" in entity " + exception.getSystemId());
valid = true;
/* // output the errors XML
XMLWriter writer = null;
try {
writer = new XMLWriter(OutputFormat.createPrettyPrint());
} catch (UnsupportedEncodingException e) {
System.out.println("validate error" + e);
e.printStackTrace();
try {
writer.write((Object)exception);
} catch (IOException e) {
System.out.println("validate error" + e);
e.printStackTrace();
public void fatalError(SAXParseException exception) throws SAXException {
System.out.println("Fatal Error: " + exception.getMessage());
System.out.println(" at line " + exception.getLineNumber()
+ ", column " + exception.getColumnNumber());
System.out.println(" in entity " + exception.getSystemId());
valid = true;
public static class MyDefaulyHandler extends DefaultHandler {
private boolean valid = true;
public void reset() {
// Assume document is valid until proven otherwise
valid = true;
public boolean isValid() {
return valid;
public void warning(SAXParseException exception) throws SAXException{
System.out.println("Warning: " + exception.getMessage());
System.out.println(" at line " + exception.getLineNumber()
+ ", column " + exception.getColumnNumber());
System.out.println(" in entity " + exception.getSystemId());
valid = true;
public void error(SAXParseException exception) throws SAXException{
System.out.println("Error: " + exception.getMessage());
System.out.println(" at line " + exception.getLineNumber()
+ ", column " + exception.getColumnNumber());
System.out.println(" in entity " + exception.getSystemId());
valid = true;
/* // output the errors XML
XMLWriter writer = null;
try {
writer = new XMLWriter(OutputFormat.createPrettyPrint());
} catch (UnsupportedEncodingException e) {
System.out.println("validate error" + e);
e.printStackTrace();
try {
writer.write((Object)exception);
} catch (IOException e) {
System.out.println("validate error" + e);
e.printStackTrace();
public void fatalError(SAXParseException exception) throws SAXException {
System.out.println("Fatal Error: " + exception.getMessage());
System.out.println(" at line " + exception.getLineNumber()
+ ", column " + exception.getColumnNumber());
System.out.println(" in entity " + exception.getSystemId());
valid = true;
public static void main(String[] args) {
EDITExtractSchema schemaClass = new EDITExtractSchema();
try {
schemaClass.validateXMLVOusingXSD("C:/Temp/project2-CorrVO/XSDs/TaxExtract5498DetailVO.xml");
}catch (Exception e) {
System.out.println("xml file read error Exception-" + e);
--====
Regards,
Tapas

No really, it will report all the error if you turn on the validation and implement the error hander methods(error()).
ALSO,
My XSD had "<xs:sequence>" which was causing the problem.
We had to change it to "<xs:all>". Now all the errors are getting reported.
thx!

What is it with the onboard devices on Neo2 Plat.

What is it with the onboard devices on the Neo2 Plat. The sound really really sucks. Bass is like not there at all, other sounds is of LOW quality - Even with the Nforce driver the sound sucks, infact this is the WORST onboard sound I have ever tried.
The wireless module is also a tragic "thing". Keeps reseting ur conection every 15 mins or so (I have 3 computers with wireless, the Neo 2 Plat is the only haveing this problem). When the wireless is working (until the next reset in 15 mins) the Package loss is like 40%???? What is that.
I thought I had a "DOA" MOBO device, GOT ANOTHER ONE. SAME SHITE.
Even tried the Win64 RC edition, guess what, same problems.
If I am wrong about this let me know (find it hard to belive since I have tested 2 Neo2 Plat, with the same problems).

take a look at the new apple wireless keyboard... they use the same layout.

'Assign resources to all ISA' Error (Neo2 Plat.)

Similar Messages

Maybe you are looking for