Apple has announced what the world and it’s mother already knew -- the company will be holding an exclusive, invitation only event in Cupertino next Tuesday. Read more
Yesterday saw Microsoft launch their next-generation server products at an event in Los Angeles, and there's some all-too-predictable 'features' they wanted to talk about. Read more
Remember the big, glitzy E3 video game shows that now seem like a distant memory? So do most enthusiasts, and fondly they do remember. But now, it seems that the big E3 of old could be making a comeback. Read more
Apple is widely expected to introduce at least one new iPod music player (a new Nano, perhaps?) and announce price cuts on some existing iPod models at a press event in San Francisco next Tuesday.
Price cuts on iPod Touch model are seen as critical to th Read more
Smartphone apps are all the rage. But the Android, BlackBerry, Palm, and WinMo stores are babies to Apple’s iTunes store. Can they fight back? Read more
From horrible bluescreens to creepy Shadow Copy Services, here are ten Vista dilemmas and solutions, from a guy serving in the Vista trenches. Read more
Next year’s ultra-thin tablet PCs might be more like phones than netbooks, if Qualcomm gets its way. The Snapdragon chip takes on Intel's Atom. Read more
Archived from groups: alt.comp.periphs.mainboard.asus (More info?)
I have an Asus K8V Deluxe motherboard. Today I reloaded my Windows XP Pro
with SP2. For my primary drive I am using the VIA in mirroring mode, and my
secondary promise Mirroring mode. I kept getting the event ID 15 error in
my system log saying \\Device0\Harddisk\D not ready for access. I updated
all drivers still same thing. I looked around in my boot.ini file to see if
there was something funky in it.
I saw this command /noexecute=optin and did some research. I am using
Norton Systemworks 2005 Premier and Microsoft said there was a problem with
cleansweep. So I took out the /noexecute=optin option and rebooted and no
longer received the Event ID 15 in my event viewer also my system boots much
quicker after removing that option from the boot.ini. Does anyone know what
this does and why it could be causing that error. Microsoft recommends
leaving it in for security reasons but is it safe to leave it out since it
is fixing my problems? Any help would be appreciated.
Archived from groups: alt.comp.periphs.mainboard.asus (More info?)
The NX bit or DEP as it is otherwise called is a method of protecting your
system against worms / virii by preventing programs from executing data as
code. Worms infect systems by sending overly long / specially crafted pieces
of data which contain program code and overwrites a system location to point
execution to that data. 'Data' should never be executed.
The NX bit (on AMD) and SP2 enhancment have been implemented to enhance
security. Turning it off should be your *last* choice. If you have a
particularly good firewall and other anti virus products running on all
internal systems then the risk is reduced somewhat.
For a fuller discussion of the issue and your Nortons problems, see:
I suggest you go to the Nortons site and look for an update for their
product. Seek support from Nortons as the MS product is behaving as
designed.
Best of luck.
- Tim
"Ryan Tremblay" <ryan@1st.net> wrote in message
news:10sv3f2crfk6d37@news.supernews.com...
>I have an Asus K8V Deluxe motherboard. Today I reloaded my Windows XP Pro
>with SP2. For my primary drive I am using the VIA in mirroring mode, and
>my secondary promise Mirroring mode. I kept getting the event ID 15 error
>in my system log saying \\Device0\Harddisk\D not ready for access. I
>updated all drivers still same thing. I looked around in my boot.ini file
>to see if there was something funky in it.
>
> I saw this command /noexecute=optin and did some research. I am using
> Norton Systemworks 2005 Premier and Microsoft said there was a problem
> with cleansweep. So I took out the /noexecute=optin option and rebooted
> and no longer received the Event ID 15 in my event viewer also my system
> boots much quicker after removing that option from the boot.ini. Does
> anyone know what this does and why it could be causing that error.
> Microsoft recommends leaving it in for security reasons but is it safe to
> leave it out since it is fixing my problems? Any help would be
> appreciated.
>
> Ryan
>
>