Ok ok. Alright! Fully aligned with you that my problem is really a unique one given the fact that some other NOS1 users have dual boots configuration without problem.

I will wait for your suggestion rather than wasting more time and money going into random direction. 

For others, thanks so much for your suggestions trying to help me. Peter and I will post the solution once the ghost is hunted down.

Thanks again
Praphan

Thanks for sharing. I am still scratching my head. Where are those ghosts on my machines ? Dual boot can be one but mine may be more.
May be it is in NOS1 ? Dunno !
Glad that you have none 

Thanks Bert for the suggestion.

I am sure I reformatted (long one not a quick format) the partition before installing OS fresh. But I am not quite sure if I took out the Juli@ interface card.

When you format the drive before installing OS, how do you format it ? Use the format facility during the installation process at the stage where you are asked for the partition to which the OS is going to. Or use the long format in the disk management ?

May be I have to buy  another brand new HDD tomorrow and try it out. Hope the ghost will be gone !

Thanks again.
Praphan

Hi Peter,

Yeap, crystal clear - my problem is not related to SQ at all. I have already made a very clear statement of problem above.

You are right that I did not use a brand new HDD right out of the box for testing. I recently googled extensively trying  to understand the impact of dual boot configuration on PCIe bus. I cannot find something relevant but came across BCD (Boot Configuration Data) on Vista too. I did not pay much attention to this subject but understand that some ‘boot data’ still implanted on HDD even if the drive is reformatted.

However, yesterday I actually test one of the three Snipers with 2TB Green Cavier back up drive that only contains music files. I have never used this HDD inside the PC. It is just a back up drive, no OS ever been installed on this drive. I just use only this drive for testing by installing Server 2008 on it. No previous HDD was hooked to the system.  In vain, doesn’t work. Same PCIe conflict. Black screen – graphic card disable when PC connected to NOS1.  Can I consider this Green Cavier as new HDD ?

Do you suggest that I buy a brand new HDD and test it again ? 

I am not quite sure I understand your solution below. 

After I gave up I created a next W7 boot alongside the existing ones (Vista and W7 on an SSD). This new W7 boot was on a spinning disk. Right after that the Vista boot saw my NOS1 again.

From the above I understand that before NOS1 vanished, you had dual boot (Vista and W7) set up on your SSD ? Then one day your PC just did not see Juli@ card.

1.   What did you do before Juli@ vanished?
2.   To fix it, you install another W7 on spinning disk while you leave SSD containing Vista and W7 in the system too. So you had triple boots. And things just resolved !

In my case, the situation is more complicated since I reformatted my SSD which contained Vista (the one I installed before the problem arose). However, my original W7 on spinning disk is still there. What should I do on my case?

Ops ! sorry, you are still on your vacation. If this consumes your time, I can wait until you arrive back in Holland.

Thanks
Praphan

Gerard,

Thanks for the reminder. But if you read my post carefully, I have three PSUs on the test bench. Coincidentally, I just tested X58A UD3R with 2 PSUs (both are working well) yesterday, all other things being the same. Giving me same failure. So I am absolutely sure that it is not because of PSUs.

I cannot think of how PSU can cause PCIe bus conflict. This little EX 1xxx interface card does not suck power at all. Only one TI smt chip on it.

Thanks
Praphan

1. Of course, for my dual boot configuration, both OSs were not only go into different partition but different physical drive. W7 on spinning disk and another W7 or Vista on SSD. When Vista was installled, I overwrote it on second W7 on SSD. After this , I saw W7-Vista. Yes the multi-boot was validated.

2. No. I did not intend to use second W7 boot for music playback. So no Juli@ driver was installed. I did not even turn on NOS1.

3. Nope as per my no 2 answer above.

Although your questions seems logical but I am afraid that it is irrelevant.
How can we describe a situation where I used brand new identical mobo, new HHD, new little PCIe interface card , new GPU and freshly installed W7 and NOS refused to see Juli@ card and created bus lane conflict? Remember my NOS still always works with vintage PC.

Seems like what I did has done some hardware change to Juli@ card permanently.

Like I said, this can only happen to me. I did not intend to discourage you from configurating a dual boot on your PC. If you feel comfortable please do it and share your experience.

thanks
Praphan

Hi George,

My haunted machine went back to the first day when I unboxed it. I hand carried it back from Europe like a new baby. It is a long story but I will try to make it short but comprehensive so it can be used as a summary post for my haunted experience to date. Peter might want to refer to this summary for his effort to be exorcist.

DISCLAIMERS:

1.   My situation can be unique or can be generic applicable to every NOS1 owners. I have no idea now. But if anyone of you came across situation close to mine please share.

2.   Given 1 above, you should not treat my experience as generic and prevent you from exploring things and enjoying our hobby. If you like adventure, go ahead and do something wild and join the club. Make sure you document your experience well for the benefit of others in this community.

MY PROBLEM :

PC system compatibility with NOS1 which resulted in various device conflicts on PCIe  bus. Some occured on the north bridge lane and some on the south bridge lane. What actually happened are described below.

SYSTEMS PUT ON TESTING :

Not only one PC system was tested, but about 10 mobos , 4 CPUs, many HDDs, 4 GPUs, 3 PCIe interface cards, 3 PSUs, 3 OSs (W7, Vista, 2008 servers – all 64 bits), 3 sets of RAMs. I posted them on another threat. Here is the link   http://www.phasure.com/index.php?topic=1636.msg16959#msg16959

BRIEF FINDINGS:

1.   AMD 880 and 890 chipset : After unboxing, my NOS1 was first connected to my 880 mobo. The system could detect Juli@ card right at the beginning but then something went wrong when switching interface card to other PCIe slots. Read this for further details :  http://www.phasure.com/index.php?topic=1636.msg16626#msg16626    Since then, this PC can never detect Juli@ card anymore, not only on 880 mobo but on 890 as well. My NOS1 decided not to work with any 880 or 890 chipsets and has an ability to memorize this decision.  If DVI cable is disconnected, all tested 880 and 890 systems worked perfectly fine. But if connected, the network adapter just disappeared (LAN disable) even though NOS1 is not powered (unplugged). My network adapter run on south bridge PCIe bus. When powering up NOS1, PC did not realize sound card.

2.   Intel 1155 socket : two P67 and one H67 mobos were tested with Sandy Bridge  i7 2600 and i5 2400. This compatibility issue came right at the BIOS stage. The booting effort went on and off and on and off in a loop and never reached the OS booting stage.  Read this :  http://www.phasure.com/index.php?topic=1636.msg16626#msg16626  Same post as 1 but under Intel heading. 

3.   Intel 1366 socket : about six X58 mobos were tested with i7 930 and i7 970. : First two tests with G1 Sniper and GA X58 UD7 (Suteetat’s music server) were successful. Note that these two systems are not configured with dual boot.   BTW, my ultimate music server used for driving NOS1 is Sniper plus i7 970. Two weeks ago, I was pondering around on how to use my music server for other applications like flight simulator and security software. So I decided to install another W7 and Vista (on another physical drive) to form a dual boot so XX will be clean on a dedicated OS.  Before installing the second OS, NOS1 was powered off.  The first run saw two W7s installed on different HDDs. It worked but quite confusing since I had no clue as to which W7 to choose from the boot screen. Then Vista was installed on top of W7 in the same partition. After powering up the NOS1, then came the device conflicts on PCIe. Depending on graphic card used, the conflict can be at north bridge lane (blank screen since graphic card is not detected), or can be south bridge PCIe lane (network adapter is gone). In any case, Juli@ card is not seen by the system. Since then my NOS1 decided again not to work with any X58 mobos. I did try changing another two new Sniper boards with freshly installed W7 on brand new HDD (all other remaining HDD disconnected). My NOS1 is very bright. It remembered Sniper and didn’t want to work with it anymore. I brought my NOS1 to Suteetat place two days ago and it behaved like a ghost this time. It refused to run on Suteetat’s same music server that I used to try successfully before.

4.   Vintage gamer PC belongs to my son : AMD Athlon 64 FX running on ASUS A8N32 mobo , 2 GB DDR2 RAM. As such I can manage to install W7 on this oldie.  For whatever reason, NOS1 loves this vintage machine like red wine. It sounds superb and it is the only one system so far that my NOS1 decided to work with.

Juli@ card has no CMOS to store firmware. What makes my NOS1 memorize its preference if it is not a ghost ?

Peter is now trying to hunt it down for me.

Praphan

Hi George,

Just woke up and get hungry. I will come back to you after my breakfast. Stay tuned for the ghost story.

My experience is real, unique and very hard to explain scientifically. No single NOS1 owner has such an extreme issue as mine. That's why Peter and I used code name "ghost" for my situation.

So stay tuned !

Praphan
Mobo geek and ghost buster
 

Hello Tim,

I guess you are coming from a gaming world into an audiophile community. I assume that you are an experienced OCer.

Before sharing my view on OC and CPU cooling, I want to draw your attention in running your XXHE player and NOS1 on Sandy Bridge platform. If you need integrated graphic on board, then you are looking at Intel H67 chipset. I do not know of anyone in this community who run P67 or H67 chipset with NOS1. Most of us are using mobos with 1366 socket. I did have experience in running both P67 and H67 mobos with NOS1. In my case, however, I failed to run NOS1 successfuly on P67 or H67 platform. A WORD OF CAUTION ! It does not necessarily mean that NOS1 is not compatible with P67/H67 mobos. But in my particular case, I have compatibility issue.  Why is that ? Peter and I are trying to figure it out. But in the meantime, you will take your own risk in running into a compatibility problem as mine. Please read my review here.

http://www.phasure.com/index.php?topic=1636.msg16626#msg16626

Juan has written an article suggesting those who intends to build a dedicated PC for XX and NOS 1. Please click this link. His article is the most comprehensive so far.

http://www.phasure.com/index.php?topic=1673.0

To answer your questions:

Overclocking : Of course, processing speed will result in a faster music files conversion on XX application. But I don’t think you need to go all the way to OC your PC to get the speed required to run optimum XX. OCing will generate heat which requires a better cooling (which is your second question). You have no choice but to run large CPU fan at high speed. Then comes more problem : audible noise and signal noise. Please read my thread by clicking this link .

http://www.phasure.com/index.php?topic=1662.msg16787#msg16787

From 0.9z-5 onward, Peter will make use of multicore processing to improve SQ. This is the reason why some of us here still stick to 1366 socket which supports hexa core processor. With HT on, XX will benefit from up to 12 threats even with half of the speed per threat. So speed is not so important as the ability to run HT.

Last advise, use your music server as a dedicated machine. Don’t run dual boots. I cannot explain why. But don’t do it if you are going to use the music server with NOS1. That said, I doubt you really need 2500k which is an unlocking version.    

Hope this will be helpful to you.

Praphan
Mobo Geek

Hi Peter,

Thanks heap for helping me to hunt down the ghosts. I eager to see what does it look like.
 
On the mobos stuff, unfortunately I own only on each of the socket. Don't have spare. But will ask Gigabyte if they have any spare that they don't need in their workshop.

Ready and fully armed to catch those ghosts with you.

Best
Praphan
 

Thanks Per,

After I fixed the issue with the help of Peter, I will share the findings in due course.

Anyone want to buy some of my mobos please let me know. Deep discount may be. But the shipping cost from Thailand and lack of warranty doesn't worth it .

Cheers !

Hello Everyone,

Just to let you guys know that I should be entitled to call myself MOBO GEEK.

Take a look at the mobos that I further tested on my NOS1. Here is the list : 3 Snipers, few X58As , two version of GA 880s, few P67s, ASUS oldie, three CPUs (AMD, i7 970 , i7 2600).

I am now still having some issues which needs Peter's help. I feel like I have a haunted machine and I need exorcist.  He he

Cheers !
Praphan

Very well put, Colonne,


I would like to add another component to your equation ie people-ware. When you purchase a mass consumer electronics, you would never get access to personalized service and support from the designer.  You won't get sincere help from fellow common users. The truth is that you can find this fourth component here at XXHE.

Cheers!
Praphan   

Thanks Peter, crystal clear.
Praphan

Hi Doc,

This is not new to me. Happen to me a number of time. With reboot, usually resolved.
I guess you bought a whole new set of RAM since your previous set was 6 x 2GB. Let's try your new half set of 3x 4 GB and see if you still have CR problem.
Good luck!