Swamptooth, thank you for your detailed post. I will check my settings. I may have enabled fast boot. But I am not fully sure I understand what you mean by "bypassing" BIOS. It never loads in to BIOS right away- it always offers to press F2 or Delete to enter BIOS. The problem was that it was not responding to F2 or Delete, or responding to it once out of 5 boot attempts. That problem started without me changing settings. It was able to enter BIOS when pressing F2, and then- no more. It got fixed by BIOS update and CMOS clearing (which could change settings to normal boot), but the fact is- it was loading and then it stoped and then it started. But I will use your suggestions, thank you.
 
Robert, seriously? I know- you know what you talking about- most of the time. lol. There is nothing wrong with the computer. It just does not like Maschine being connected on boot. And I am trying to figure it out. Also- can you, please, remind me what software you use to grab audio from Youtube? I think- you missed my post under "My life's Komplete now". That's ok- nothing important. Thanks a lot.

As computers get more advanced, launching the bios takes more time. To help computers start more quickly, the bios gets effectively slept like windows so when you start your pc it never crosses the point where you enter the bios gui. Restating windows is one way to ensure you cross the point where you can enter the gui.

My Word...this thread lol!!!
 
I am MS certified so may be able to help.....
 
Firstly one User mentioned that your BIOS is on the 1st memory stick, this isnt true, its on the CMOS battery or a built in ROM chip, your memory that you are referring to is RAM and NOT ROM.
 
I think what the User was referring to is that when your PC boots up the first thing the BIOS does is check the information stored in a tiny (64 bytes) amount of RAM located on the CMOS chip, this is why Asus asked you to reset your CMOS (probably by simply locating and removing it then re-inserting it)

 
I had to get that one out the way.....
 
Back to your initial problem....
 
Now XP can be a nightmare with USB devices sending Windows into an eternal loop.
 
Your FIRST point of call should be to go into Device Manager and from within there click on "Show hidden devices" (or something like that in the VIEW options - forgive me, its been some years since I used XP)..Once you have done that you will find that XP has cached numerous amounts of USB devices over time, go through them and delete the repeats and the ones you dont use. Reboot.
 
Then Plug in your NI controller and install.
 
Once you have done that get back to me and maybe I can help.
 
Hope this helps.
 
 
 
 

If machine is powered down, can you start windows? If so , your pc is likely trying to boot from that usb device when it is powered rather than your hard drives. Bios settings typically control this. Some usb devices like hard drives must be disconnected to affect this test.

I just noticed in the OP, the sig states Win XP SP3....
 
Can Vladasyn please change the sig to update the OS accordingly.....?
 
Anyway, my advice still applies about device manager and USB devices.

Btw, anyone know if Noel is M$ certified?
Wink

gswitz
Btw, anyone know if Noel is M$ certified?
Wink

 
lol, it doesnt actually count for much these days 
 
In a previous life, 10 years working in IT MS support does however.....

Yanno... I find this thread to be confusing and I'm not quite sure all what is being discussed here but it seems (and forgive me if this is an impossibility) that having the MIDI device connected at boot is what's really causing this chaos. Can Maschine not be turned on or connected AFTER you boot up? I never turn on any of my MIDI devices until the system is fully booted and I make sure I turn them on BEFORE loading Sonar. I've gone through a few different boot up/power on/open DAW procedures and this is the one that never fails.
 
You do seem to have a lot of issues with your system(s) Vlad. I'm kind of wondering if perhaps you've poked around at things so much you are experiencing a cascade effect of issues. Might be advisable to just wipe everything and start fresh. It should not be this complicated... especially on your brand new system.
 
Good luck.

Beepster
Yanno... I find this thread to be confusing and I'm not quite sure all what is being discussed here but it seems (and forgive me if this is an impossibility) that having the MIDI device connected at boot is what's really causing this chaos. Can Maschine not be turned on or connected AFTER you boot up? I never turn on any of my MIDI devices until the system is fully booted and I make sure I turn them on BEFORE loading Sonar. I've gone through a few different boot up/power on/open DAW procedures and this is the one that never fails.
 
You do seem to have a lot of issues with your system(s) Vlad. I'm kind of wondering if perhaps you've poked around at things so much you are experiencing a cascade effect of issues. Might be advisable to just wipe everything and start fresh. It should not be this complicated... especially on your brand new system.
 
Good luck.

 
Word. Its a minefield.
 
Installing incorrect memory, SSD drives, USB NI Maschine, unsure of what OS the OP is about....
 
But if we weave our way through the madness......I stand by my post....
 
Go into Device manager, check "show hidden devices", delete rogue USB device duplicates. Reboot Windows and reinstall the NI controller.

*whispers*
 
This thread really does smell of "TOO MUCH TINKERING"