ok.. maybe its an isolated incident... or maybe its just crap, idk..
i got an Mwave n258ka, u all know its stats... the only thing i added was a 512 mb stick o' ram and a 40 gig 4200 hd.. and windows xp home.
now. the problem, which i think is inherenet in all n258ka, uniwill class, mwave, ibp, etc..
i use my notebooks to game.. and sometimes i needa close the lid of my laptops, but need to keep the game running.. most of u all know, that inherently notebooks will go into standby or hibernate to save power when u do that. well i set mine under power options >> advanced, to literally "do nothing"... and i set the screen timer to close in 1 min.. the problem : THE SCREEN WON"T REACTIVATE after that 1 min! i don't know if this has been a topic b4, but i returned my notebook with that complaint. mwave replaced it [i live like 7 min from them] in about 1.5 days. i checked the notebook, no dead pixels.. and then i bring it home, after i reinstall all the drivers.. i repeat the process to see if they fixed the SCREEN WON't ACTIVATE error.. and the problem hasn't disappeared. its a new notebook. i remember cuz one of the usb ports had a distinguishing mark that this notebook didn't have.. so that means 2 [n258ka] notebook experiencing the same flaw..
the condition under which it happens :
1) AC is plugged in.
2) Under Power Options >> Advanced [tab].. the laptop will " do nothing " when the lid is closed.
3) Set the Power Options to turn off the screen to whatever time you want.
4) close the lid, and wait for the time u entered to pass.
5) when u know the screen is closed, open it.. it should be blank with no activity.
6) now try all u can to power it up, without resorting to manual restarts and standby or alt + f4.
i'm really psst that this flaw exists.. maybe its isolated to the first and second n258ka notebooks i got... or maybe its a flaw in the whole model line, despite who u buy it from..
any help ?! should i just return this one too?
the BIOs is already updated, tried everything i could think of to get around this problem, and so far, the only hting that works is hitting the standby button and waiting for it to boot up again.
i got an Mwave n258ka, u all know its stats... the only thing i added was a 512 mb stick o' ram and a 40 gig 4200 hd.. and windows xp home.
now. the problem, which i think is inherenet in all n258ka, uniwill class, mwave, ibp, etc..
i use my notebooks to game.. and sometimes i needa close the lid of my laptops, but need to keep the game running.. most of u all know, that inherently notebooks will go into standby or hibernate to save power when u do that. well i set mine under power options >> advanced, to literally "do nothing"... and i set the screen timer to close in 1 min.. the problem : THE SCREEN WON"T REACTIVATE after that 1 min! i don't know if this has been a topic b4, but i returned my notebook with that complaint. mwave replaced it [i live like 7 min from them] in about 1.5 days. i checked the notebook, no dead pixels.. and then i bring it home, after i reinstall all the drivers.. i repeat the process to see if they fixed the SCREEN WON't ACTIVATE error.. and the problem hasn't disappeared. its a new notebook. i remember cuz one of the usb ports had a distinguishing mark that this notebook didn't have.. so that means 2 [n258ka] notebook experiencing the same flaw..
the condition under which it happens :
1) AC is plugged in.
2) Under Power Options >> Advanced [tab].. the laptop will " do nothing " when the lid is closed.
3) Set the Power Options to turn off the screen to whatever time you want.
4) close the lid, and wait for the time u entered to pass.
5) when u know the screen is closed, open it.. it should be blank with no activity.
6) now try all u can to power it up, without resorting to manual restarts and standby or alt + f4.
i'm really psst that this flaw exists.. maybe its isolated to the first and second n258ka notebooks i got... or maybe its a flaw in the whole model line, despite who u buy it from..
any help ?! should i just return this one too?
the BIOs is already updated, tried everything i could think of to get around this problem, and so far, the only hting that works is hitting the standby button and waiting for it to boot up again.
