Tuesday, February 27, 2007
^_^
Yes yes .. it's been years since I last posted.. Can't be helped, have been super busy with lotsa work since the last post. The project's been ramped up and there's lots of things to be done as we're making a release every week.
Even had to cater to a custom order during the CNY period. They wanted to demo our app to the HP dudes @ USA and the Vista laptop the VP was bringing didn't have the proper audio interfaces. Therefore there was a snap decision to create a WMP plugin to interface with the app, just like how the OSX's one is handled.
And of course who has to do it?
Yours truly of course, since the OSX's one is mine .. heh.
Windows COM programming totally sucks. For some reason the constructor and destructor (FinalConstruct and FinalRelease) were being called more than once, even though the template's tooltips said it was a one time initialisation. Damn COM objects! Damn C++! Anyways finally managed to whip out in record time a WMP plugin .. from 0 COM knowledge. Not too bad huh /flex
During that period, I learnt how sucky Vista is.
First was WMP11. To install a plugin in WMP9 and 10, you could just go to Options and go to the plugins tab and click add. But for WMP11? No..... even though the plugin page says you can add plugins, there's no add button. The help file's stupid too. Just says you need to be an admin to add plugins, but doesn't tell you how.
After some research, managed to find out how to install a BLOODY plugin. It's back to the usual "regsvr32" crap. Way to go for a "GUI" based OS. But that's not all... When I tried to register my plugin, it gave me an obscure error 0x008..something or other. Some googling told me that it was a permissions problem, that I needed to be admin to do the operation.
So I peeked at my User account. Sure thing, I was admin. OK, so I realised I needed sudo. Well.. okay, that's fair. *nix + OSX work that way too, even if you are logged as admin, you'll still have to sudo if you need to do some special stuff. The problem now was... how the heck do I sudo in Vista? Naturally "sudo" didn't work. -_-
Finally managed to get it to work. How? Open Explorer, go to Windows\system32, look for cmd, right click and choose run as admin. WTF? That's so stupid. In any *nix system, all you need to do is type "sudo". In OSX, all you need to do is type "sudo". Why isn't there a way to easily switch to super user mode in Vista? Why must I navigate all the way to system32, right click and choose run as admin? The entire session is now admin. If I forgot and left it and went to the toilet, some malicious dude could do evil stuff to the OS. Vista is so.. freaking.. dumb.
Oh .. WMP11 is dumb too. How do you add plugins to iTunes? Simply copy the file to the plugins directory and restart. Voila! How do you add plugins to Winamp? Simply copy the files to the directory and restart (could be wrong there.. rusty!). Why in the 9 freaking hells do I have to be SUPER USER and run a COMMAND LINE PROMPT to add in a simple plugin? WMP9 > WMP11 there. And at least update your UI and your freaking help files to reflect that.
Pbbt.
Also, whoever who thought up the stupid user authentication thing ought to be shot. Twice. No. Fitty billion times. This ad from Apple most accurately sums it all up.
To copy a file (that is, my dll plugin) to a "protected" place like C:\program files\windows media player, I have to authenticate. Again, fair enough. I have to do that on a *nix/OSX box too. However, the BIG BIG BIG problem is that it's modal.
Process: Click file -> Drag file to explorer pointing to protected folder -> Dialogue box appears telling me I have to yada yada yada give confirmation -> Click ok -> Screen flashes (the first time it happened I went oO? Comp crash?) -> Annoying modal box appears asking me to confirm. During this period I can do NOTHING until I continue/cancel.
Problem? Yeah. Totally. For OSX, which I use the most often besides XP, a (ONE) dialogue box appears, and I just enter my password and I'm done. If I'm doing other stuff or another application wants my attention, I can just leave that dialogue box there until I want to deal with it.
Vista is so super secure. I can't copy a file from a network drive to a protected place. When I do that action, a dialogue box appears telling me that I have to give confirmation, which I click ok (or continue. w/e), then this box appears telling me that I can't do that .. blah blah. Look. If I want to copy a file. COPY it! Or just say no on the outset. What's the point of popping up that dumb dialogue box if you're going to stop me later anyways? 1 more click for me.
Replacing a file in protected folders.
To replace a file, I have to go through 3 dialogues. 1: Do you want to replace? Copy? Cancel? Copy and rename the original file? (At least I think that's what it is. Kinda remember that there was a 4th option). THEN it pops up the dialogue again, then tat modal thing.
-_-
The worse part here (what? You mean there's worse parts to all that clicking on continue?) is the copy/replace/cancel option. In OSX, it's a simple Continue or Cancel. This one has an ultra big dialog box with pretty icons and lotsa text telling you what will happen if you Replace, what will happen if you copy .. etc etc. Dude. I don't need that information. Provide a ? or tooltips if you want. Don't make it appear all the time.
Odd.
When you cancel a delete on a file, you'd expect it to be a no-op right? The OS just stays silent if you click cancel. However, for some gay mysterious reason, that's not the case for Vista.
Deleting a file in a protected folder.
Click delete -> Click continue -> Click cancel on annoying modal box -> A file progress window appears (for you XP users, it's somewhat like that window that appears when you copy many files, a little icon and a progress bar with a cancel button). The first time it happened, I was going wtf? Didn't I click cancel? Well yeah apparently it's a "cancel" action. Apparently, the file is ... sent to the recycle bin when I clicked on delete (or something like that), so when I click cancel at the last step, it needs to restore it.
It's not extremely stable too. The business edition test machine I was using died 2 times while I was testing. The first time it died silently. I just left it to idle while I did stuff on my Mac. Turned back, and it was dead. Not the normal kind of dead, it was massive graphics corruption kind of dead. Think of copying the picture of 1 window and pasting it everywhere on the screen. (Actually kinda worse but it's the closest I can think of). And it was doing NOTHING.
Bah.
Vista is so gay. Of course, one may argue that I was doing "power user" stuff, copying files from protected places, etc. But it's just showing how annoying it is. I've done this on XP, done this on OSX, nothing at all. I don't need an OS to keep asking me dumb questions on annoyingly big dialogue boxes.
Pretty sure I'm not going to get a Vista. If I were to get one, it's purely for games. WTB more OSX games! Thinking of switching to the OSX platform. Would be great if I could get it running on Resurrection though, seems to be alot of hoops to jump through though. Shimatta!
Even had to cater to a custom order during the CNY period. They wanted to demo our app to the HP dudes @ USA and the Vista laptop the VP was bringing didn't have the proper audio interfaces. Therefore there was a snap decision to create a WMP plugin to interface with the app, just like how the OSX's one is handled.
And of course who has to do it?
Yours truly of course, since the OSX's one is mine .. heh.
Windows COM programming totally sucks. For some reason the constructor and destructor (FinalConstruct and FinalRelease) were being called more than once, even though the template's tooltips said it was a one time initialisation. Damn COM objects! Damn C++! Anyways finally managed to whip out in record time a WMP plugin .. from 0 COM knowledge. Not too bad huh /flex
During that period, I learnt how sucky Vista is.
First was WMP11. To install a plugin in WMP9 and 10, you could just go to Options and go to the plugins tab and click add. But for WMP11? No..... even though the plugin page says you can add plugins, there's no add button. The help file's stupid too. Just says you need to be an admin to add plugins, but doesn't tell you how.
After some research, managed to find out how to install a BLOODY plugin. It's back to the usual "regsvr32" crap. Way to go for a "GUI" based OS. But that's not all... When I tried to register my plugin, it gave me an obscure error 0x008..something or other. Some googling told me that it was a permissions problem, that I needed to be admin to do the operation.
So I peeked at my User account. Sure thing, I was admin. OK, so I realised I needed sudo. Well.. okay, that's fair. *nix + OSX work that way too, even if you are logged as admin, you'll still have to sudo if you need to do some special stuff. The problem now was... how the heck do I sudo in Vista? Naturally "sudo" didn't work. -_-
Finally managed to get it to work. How? Open Explorer, go to Windows\system32, look for cmd, right click and choose run as admin. WTF? That's so stupid. In any *nix system, all you need to do is type "sudo". In OSX, all you need to do is type "sudo". Why isn't there a way to easily switch to super user mode in Vista? Why must I navigate all the way to system32, right click and choose run as admin? The entire session is now admin. If I forgot and left it and went to the toilet, some malicious dude could do evil stuff to the OS. Vista is so.. freaking.. dumb.
Oh .. WMP11 is dumb too. How do you add plugins to iTunes? Simply copy the file to the plugins directory and restart. Voila! How do you add plugins to Winamp? Simply copy the files to the directory and restart (could be wrong there.. rusty!). Why in the 9 freaking hells do I have to be SUPER USER and run a COMMAND LINE PROMPT to add in a simple plugin? WMP9 > WMP11 there. And at least update your UI and your freaking help files to reflect that.
Pbbt.
Also, whoever who thought up the stupid user authentication thing ought to be shot. Twice. No. Fitty billion times. This ad from Apple most accurately sums it all up.
To copy a file (that is, my dll plugin) to a "protected" place like C:\program files\windows media player, I have to authenticate. Again, fair enough. I have to do that on a *nix/OSX box too. However, the BIG BIG BIG problem is that it's modal.
Process: Click file -> Drag file to explorer pointing to protected folder -> Dialogue box appears telling me I have to yada yada yada give confirmation -> Click ok -> Screen flashes (the first time it happened I went oO? Comp crash?) -> Annoying modal box appears asking me to confirm. During this period I can do NOTHING until I continue/cancel.
Problem? Yeah. Totally. For OSX, which I use the most often besides XP, a (ONE) dialogue box appears, and I just enter my password and I'm done. If I'm doing other stuff or another application wants my attention, I can just leave that dialogue box there until I want to deal with it.
Vista is so super secure. I can't copy a file from a network drive to a protected place. When I do that action, a dialogue box appears telling me that I have to give confirmation, which I click ok (or continue. w/e), then this box appears telling me that I can't do that .. blah blah. Look. If I want to copy a file. COPY it! Or just say no on the outset. What's the point of popping up that dumb dialogue box if you're going to stop me later anyways? 1 more click for me.
Replacing a file in protected folders.
To replace a file, I have to go through 3 dialogues. 1: Do you want to replace? Copy? Cancel? Copy and rename the original file? (At least I think that's what it is. Kinda remember that there was a 4th option). THEN it pops up the dialogue again, then tat modal thing.
-_-
The worse part here (what? You mean there's worse parts to all that clicking on continue?) is the copy/replace/cancel option. In OSX, it's a simple Continue or Cancel. This one has an ultra big dialog box with pretty icons and lotsa text telling you what will happen if you Replace, what will happen if you copy .. etc etc. Dude. I don't need that information. Provide a ? or tooltips if you want. Don't make it appear all the time.
Odd.
When you cancel a delete on a file, you'd expect it to be a no-op right? The OS just stays silent if you click cancel. However, for some gay mysterious reason, that's not the case for Vista.
Deleting a file in a protected folder.
Click delete -> Click continue -> Click cancel on annoying modal box -> A file progress window appears (for you XP users, it's somewhat like that window that appears when you copy many files, a little icon and a progress bar with a cancel button). The first time it happened, I was going wtf? Didn't I click cancel? Well yeah apparently it's a "cancel" action. Apparently, the file is ... sent to the recycle bin when I clicked on delete (or something like that), so when I click cancel at the last step, it needs to restore it.
It's not extremely stable too. The business edition test machine I was using died 2 times while I was testing. The first time it died silently. I just left it to idle while I did stuff on my Mac. Turned back, and it was dead. Not the normal kind of dead, it was massive graphics corruption kind of dead. Think of copying the picture of 1 window and pasting it everywhere on the screen. (Actually kinda worse but it's the closest I can think of). And it was doing NOTHING.
Bah.
Vista is so gay. Of course, one may argue that I was doing "power user" stuff, copying files from protected places, etc. But it's just showing how annoying it is. I've done this on XP, done this on OSX, nothing at all. I don't need an OS to keep asking me dumb questions on annoyingly big dialogue boxes.
Pretty sure I'm not going to get a Vista. If I were to get one, it's purely for games. WTB more OSX games! Thinking of switching to the OSX platform. Would be great if I could get it running on Resurrection though, seems to be alot of hoops to jump through though. Shimatta!
Tuesday, February 06, 2007
And to continue ...
And I was planning to do other stuff on that weekend!
Hairdressers ... spring cleaning ............
T_T
gone.
SIGH.
At least I guess .. I spring cleaned Resurrection..? ........... EXCEPT FOR THAT @($*&@( DOUBLE BOOTING PROBLEM.
And the hdd problem, I'm too scared to even plug in my WD to wipe it clean. Was thinking of just taking out all my drives, plug it in, and use the XP installation disk to delete my partitions, can't even secure erase it from Norton.. SIGH
Hairdressers ... spring cleaning ............
T_T
gone.
SIGH.
At least I guess .. I spring cleaned Resurrection..? ........... EXCEPT FOR THAT @($*&@( DOUBLE BOOTING PROBLEM.
And the hdd problem, I'm too scared to even plug in my WD to wipe it clean. Was thinking of just taking out all my drives, plug it in, and use the XP installation disk to delete my partitions, can't even secure erase it from Norton.. SIGH
Ayam Alife!
Been a long while since I posted .. Have been busy with work and stuff. Had a traumatic weekend when I went home .. Flipped on Resurrection, and she couldn't boot! Gah! She couldn't even hit bios. Kept rebooting. :S
Started pulling stuff out and trying to boot. Finally pulled out the mobo and tried to boot... no dice. *severely traumatised*
Decided to bring in the mobo the next day to RMA... SIGH.
Met R and went down to SLS to RMA the mobo, he went to the office while I went to SLS. Then when I got there, the dude said actually mobo must/should RMA at the distributor, otherwise dunno when they will fix (duh?) But good thing the distributor was coming down in the afternoon so he could bring another one for me to change.
So went back to the office and did some work, closed some bugs, added some bug notes while waiting.
Finally at long last, I got my new mobo and went home to hook her up. Before I encased her into Resurrection's metal shell, I tested her to make sure that she could boot. You know, the good ol' insert the screw driver in a specific locations. Hooked her up and lugged the heavy metal casing back. Powered her on and lo Windows finally started.
All was fine and dandy until she started crashing really badly.
It would be like *chat on msn* *hear some ... dropping sound* and Resurrection will chug to a halt. She was even starting to hang at chkdsk -_-;; at that point, I was reaching @($&*@*(!! state. WTF was happening?!? Then errors like "unknown hard error" started popping up.
....
Severely traumatised, I formed several conclusions
1: Most obvious, hdd xX
2: The new mobo has a new revision of the ACHI driver, it could be that.
So I decided to reinstall windows.
...
Windows setup takes like a few gazillion years to load -_-. Upon startup, it loads like fitty billion drivers which you've never EVER seen before. QLogic? Nani? SCSI? Just load the ones I need lah, the rest just load on demand! <_<
At first I decided to be lazy and do a repair, after grinding through a yellow progress bar which purports to be "checking your disk", it ended with a "Setup has repair errors in your disk, press F3 to restart" message. Which I dutifully did (not that you have much of a choice)
After getting into setup .. again .. zzz... I tried to repair again, it went through the yellow progress bar, and ended with a "Setup has detected that your drive is corrupted and blah, Setup cannot continue" -_-
So I decided (was just banging my head against a wall) to reinstall windows clean
After grinding through setup again (more times than mentioned!), I finally reached the install windows screen. Selected that I want - install windows in c, delete current windows... It did the Yellow Progress Bar (AGAIN!) and deleted my windows :O zomg! .. Then it *gasp* started to install windows .........
However ...... at driver.cab, it suddenly bailed on me with this message "Setup cannot copy driver.cab from the cd.. make sure blah blah file there blah" .. I was fainting. Don't tell me my CD died too!? .. I tried both Xps that I had but no dice, finally had no choice but to reboot ....
.. And grind through setup .. again.
This time it couldn't even detect my primary disk -_-
Went through setup ......... again.
Detected C. D and E (which were separate partitions on the same physical disk) were listed as UNKNOWN.
Nonetheless, tried to install windows into C. At 97% of the Yellow Progress Bar, it bailed on me again. This time it was d3d8.dll which couldn't be found.
After some teeth gnashing (this time it's pretty apparent that it's not media fault)..
Went through setup ......... yet again.
This time it managed to detect all my partitions, and installed ......
It even managed to boot into the GUI part of the installation! Zomg!
... Tried to install East Asian language, halfway through the grinding .. it died.
I've nv seen Setup @ GUI side bail so spectacularly before, but it did. I finally did the wise thing and gave up.
Went and got a new harddisk, a Hitachi Deathstar 500GB the next day. Installed everything fine.
However, something odd happened when I plugged in my old primary disk (which is a WD 320GB) to save my data. My ACHI bios couldn't detect my Deathstar! :O But it managed to detect my WD fine. .. -_- After clearing CMOS, it finally detected both drives and booted. Once in windows, I quickly arranged for my sweet sweet data to escape into the Ark. (Maybe I should rename one of my partitions that). It was a painful journey, imagine the torrential rain, pouring down into the waterlogged muddy land, with your data, gray with mud, struggling to make it across. The ones who had gone over screaming for their companions to get to safety. After several breakages in connection (which brought down the file transfer but not windows, thankfully), the pertinent data managed to get Saved. Finally. The rest had to be jettisoned.
You'd think all would be well at this point, but strangely .. it seems that after this, the mobo's starting to have difficulty in detecting my Deathstar -_-, my 250 Hitachi is still reliably detected -_-.
At this point I decided (not very wisely) to flash the bios of my mobo, to hopefully fix this "bug". This is my first and last time flashing a gigabyte board. The windows flashing application is extremely poorly written. There's some threading issues around. When it's making the ftp connection to download the new bios, the gui hangs.. -_-; When it's doing the MOST IMPORTANT job (the sole reason for its existence!), the GUI hung. You know how traumatic that is!? Updating the bios of your mobo's one of the most :S things to do, pull the plug, windows hang .. and it's dead.
So finally, thankfully, the application didn't die, and I rebooted. Instead of a friendly bios screen, this screen appeared.
Scanning BIOS from Harddisk . . .
Nani?! The power button started winking at me at this point. After sitting around for a moment waiting for THINGS to happen, I decided to just restart the damn thing. When she restarted (fingers crossed!) she went into the Dual Bios (which gigabyte always trumpets about) selection screen and said "Updating bios" ... .... .. and completed.
Hurrah?
Well.
I booted into windows, the second before the Welcome screen was to appear, Resurrection did a hard reset. THEN windows booted up perfectly. -_-
Seriously!?
Neither did the flash fix my "can't detect Deathstar 500" problem too.
So now I have 2 problems, unreliable detection of Primary Deathstar and 2 boots to get into windows.
Just (hopefully) fixed the first problem. My mobo has 2 raid/IDE controllers, the ICH8R and the Gigabyte one. Previously I've been using the ICH8R, so now I've plugged both my drives to the Gigabyte controller (note to self, when I reinstall windows I'll have to plug them back to ICH8R, cos that's the one I have drivers for.. I could try getting the gigabyte ones I guess ..... sigh)
So far so good. Detection's much faster on the Gigabyte controller than ICH8R.
However, my windows still has the double booting problem -_- Not sure how to fix it. Not really keen to reinstall windows.
On the bright side, at least it's ... automated.............?
GAH!
/wail T_T
Started pulling stuff out and trying to boot. Finally pulled out the mobo and tried to boot... no dice. *severely traumatised*
Decided to bring in the mobo the next day to RMA... SIGH.
Met R and went down to SLS to RMA the mobo, he went to the office while I went to SLS. Then when I got there, the dude said actually mobo must/should RMA at the distributor, otherwise dunno when they will fix (duh?) But good thing the distributor was coming down in the afternoon so he could bring another one for me to change.
So went back to the office and did some work, closed some bugs, added some bug notes while waiting.
Finally at long last, I got my new mobo and went home to hook her up. Before I encased her into Resurrection's metal shell, I tested her to make sure that she could boot. You know, the good ol' insert the screw driver in a specific locations. Hooked her up and lugged the heavy metal casing back. Powered her on and lo Windows finally started.
All was fine and dandy until she started crashing really badly.
It would be like *chat on msn* *hear some ... dropping sound* and Resurrection will chug to a halt. She was even starting to hang at chkdsk -_-;; at that point, I was reaching @($&*@*(!! state. WTF was happening?!? Then errors like "unknown hard error" started popping up.
....
Severely traumatised, I formed several conclusions
1: Most obvious, hdd xX
2: The new mobo has a new revision of the ACHI driver, it could be that.
So I decided to reinstall windows.
...
Windows setup takes like a few gazillion years to load -_-. Upon startup, it loads like fitty billion drivers which you've never EVER seen before. QLogic? Nani? SCSI? Just load the ones I need lah, the rest just load on demand! <_<
At first I decided to be lazy and do a repair, after grinding through a yellow progress bar which purports to be "checking your disk", it ended with a "Setup has repair errors in your disk, press F3 to restart" message. Which I dutifully did (not that you have much of a choice)
After getting into setup .. again .. zzz... I tried to repair again, it went through the yellow progress bar, and ended with a "Setup has detected that your drive is corrupted and blah, Setup cannot continue" -_-
So I decided (was just banging my head against a wall) to reinstall windows clean
After grinding through setup again (more times than mentioned!), I finally reached the install windows screen. Selected that I want - install windows in c, delete current windows... It did the Yellow Progress Bar (AGAIN!) and deleted my windows :O zomg! .. Then it *gasp* started to install windows .........
However ...... at driver.cab, it suddenly bailed on me with this message "Setup cannot copy driver.cab from the cd.. make sure blah blah file there blah" .. I was fainting. Don't tell me my CD died too!? .. I tried both Xps that I had but no dice, finally had no choice but to reboot ....
.. And grind through setup .. again.
This time it couldn't even detect my primary disk -_-
Went through setup ......... again.
Detected C. D and E (which were separate partitions on the same physical disk) were listed as UNKNOWN.
Nonetheless, tried to install windows into C. At 97% of the Yellow Progress Bar, it bailed on me again. This time it was d3d8.dll which couldn't be found.
After some teeth gnashing (this time it's pretty apparent that it's not media fault)..
Went through setup ......... yet again.
This time it managed to detect all my partitions, and installed ......
It even managed to boot into the GUI part of the installation! Zomg!
... Tried to install East Asian language, halfway through the grinding .. it died.
I've nv seen Setup @ GUI side bail so spectacularly before, but it did. I finally did the wise thing and gave up.
Went and got a new harddisk, a Hitachi Deathstar 500GB the next day. Installed everything fine.
However, something odd happened when I plugged in my old primary disk (which is a WD 320GB) to save my data. My ACHI bios couldn't detect my Deathstar! :O But it managed to detect my WD fine. .. -_- After clearing CMOS, it finally detected both drives and booted. Once in windows, I quickly arranged for my sweet sweet data to escape into the Ark. (Maybe I should rename one of my partitions that). It was a painful journey, imagine the torrential rain, pouring down into the waterlogged muddy land, with your data, gray with mud, struggling to make it across. The ones who had gone over screaming for their companions to get to safety. After several breakages in connection (which brought down the file transfer but not windows, thankfully), the pertinent data managed to get Saved. Finally. The rest had to be jettisoned.
You'd think all would be well at this point, but strangely .. it seems that after this, the mobo's starting to have difficulty in detecting my Deathstar -_-, my 250 Hitachi is still reliably detected -_-.
At this point I decided (not very wisely) to flash the bios of my mobo, to hopefully fix this "bug". This is my first and last time flashing a gigabyte board. The windows flashing application is extremely poorly written. There's some threading issues around. When it's making the ftp connection to download the new bios, the gui hangs.. -_-; When it's doing the MOST IMPORTANT job (the sole reason for its existence!), the GUI hung. You know how traumatic that is!? Updating the bios of your mobo's one of the most :S things to do, pull the plug, windows hang .. and it's dead.
So finally, thankfully, the application didn't die, and I rebooted. Instead of a friendly bios screen, this screen appeared.
Scanning BIOS from Harddisk . . .
Nani?! The power button started winking at me at this point. After sitting around for a moment waiting for THINGS to happen, I decided to just restart the damn thing. When she restarted (fingers crossed!) she went into the Dual Bios (which gigabyte always trumpets about) selection screen and said "Updating bios" ... .... .. and completed.
Hurrah?
Well.
I booted into windows, the second before the Welcome screen was to appear, Resurrection did a hard reset. THEN windows booted up perfectly. -_-
Seriously!?
Neither did the flash fix my "can't detect Deathstar 500" problem too.
So now I have 2 problems, unreliable detection of Primary Deathstar and 2 boots to get into windows.
Just (hopefully) fixed the first problem. My mobo has 2 raid/IDE controllers, the ICH8R and the Gigabyte one. Previously I've been using the ICH8R, so now I've plugged both my drives to the Gigabyte controller (note to self, when I reinstall windows I'll have to plug them back to ICH8R, cos that's the one I have drivers for.. I could try getting the gigabyte ones I guess ..... sigh)
So far so good. Detection's much faster on the Gigabyte controller than ICH8R.
However, my windows still has the double booting problem -_- Not sure how to fix it. Not really keen to reinstall windows.
On the bright side, at least it's ... automated.............?
GAH!
/wail T_T
Subscribe to:
Posts (Atom)