Om Mani Padme Hum
- wong chee tat :)
Friday, February 21, 2014
Scheduled Maintenance - POSB
Scheduled Maintenance - POSB
- wong chee tat :)
Service | Scheduled Maintenance Date | Expected Downtime | Remarks |
iBanking | 09 Feb 2014 | 0100hrs to 0105hrs, 0650hrs to 0655hrs | System Maintenance - MCSA Funds Transfer, and Portfolio Enquiry |
09 Feb 2014 | 0100hrs to 0705hrs | System Maintenance - Online Equity Trading(OET) | |
16 Feb 2014 | 0200hrs to 0245hrs | System Maintenance -Upload documents | |
16 Feb 2014 | 0650hrs to 0655hrs | System Maintenance - MCSA Funds Transfer, and Portfolio Enquiry | |
16 Feb 2014 | 0100hrs to 0105hrs | System Maintenance - MCSA Funds Transfer, and Portfolio Enquiry | |
16 Feb 2014 | 0100hrs to 0705hrs | System Maintenance - Online Equity Trading(OET) | |
22 Feb 2014 | 1000hrs to 0000hrs | System Maintenance - Online Equity Trading | |
23 Feb 2014 | 0000hrs to 0730hrs | System Maintenance - Token Registration | |
23 Feb 2014 | 0000hrs to 1200hrs | System Maintenance - Online Equity Trading | |
02 Mar 2014 | 0000hrs to 0600hrs | System Maintenance -Upload documents | |
mBanking | - | - | - |
iB Application | - | - | - |
iB - Trading Services | 22 Feb 2014 | 1000hrs to 0000hrs | System Maintenance |
23 Feb 2014 | 0000hrs to 1200hrs | System Maintenance | |
D2Pay | 16 Feb 2014 | 0300hrs to 0600hrs | System Maintenance |
Phone Banking | - | - | - |
NETS | - | - | - |
Passbook Update | - | - | - |
Automated Teller Machine (ATM) | - | - | - |
Cash Deposit Machine | - | - | - |
Coin Deposit Machine | - | - | - |
Cheque Deposit Machine | - | - | - |
POSB Print | - | - | - |
AXS D-Pay | - | - | - |
Token Registration | - | - |
- wong chee tat :)
Labels:
2014,
DBS,
DBS Bank Ltd,
feb,
maintenance,
posb,
System Updates,
Update,
Updates
Broken Windows, Broken Wireless
Someone came to me with an interesting problem:
The laptop has a problem with the wireless. Whenever anyone tries to connect to wireless, Windows 7 simply eeks out and produces Blue Screen of death (BSOD or simply the dread Blue Screen). Connecting to lan cable works. How to resolve that? And what is the problem?
Let us do this way:
On and off the wireless button. We can see that the laptop can detect the wifi signals - that is good.
Test that out: I'm using my phone as a hotspot and tries to connect to the laptop. Once it got my password or passphase, and before it even connects, the dread Blue Screen comes.
What does that info from Blue Screen says?
STOP 0x0000007F ( 0x0000... ....)
Googling provide some hints:
• Low-level hardware corruption, such as corrupt memory (RAM)
• Mismatched memory modules
• A malfunctioning motherboard
Other links point to problematic software programs.
Suspecting driver issue, but reinstalling the correct driver doesn't help. It crashes again with the same Blue Screen. So what is next? What options do we have?
Lets us zoom in....
So, is it a hardware or software problem?
Suddenly, I though of an idea. Why don't we test Linux out and there is no harm (and fun) testing ? Pump in Linux live cd and then connect to my hotspot. If it is able to detect and connect to my hotspot, then we know that there could be problem with Windows and the probably some corrupted software drivers. If it is a hardware issue, then connecting via Linux would likely fail as well. Then we can get the hardware replaced. That would simplify matters. Tested and able to get connected.
Format it and reinstall Windows 7 and start from scratch. Tested if is able to connect to wifi. It does! Cheers!
References:
http://support.microsoft.com/kb/137539
http://support.microsoft.com/kb/822789
- wong chee tat :)
The laptop has a problem with the wireless. Whenever anyone tries to connect to wireless, Windows 7 simply eeks out and produces Blue Screen of death (BSOD or simply the dread Blue Screen). Connecting to lan cable works. How to resolve that? And what is the problem?
Let us do this way:
On and off the wireless button. We can see that the laptop can detect the wifi signals - that is good.
Test that out: I'm using my phone as a hotspot and tries to connect to the laptop. Once it got my password or passphase, and before it even connects, the dread Blue Screen comes.
What does that info from Blue Screen says?
STOP 0x0000007F ( 0x0000... ....)
Googling provide some hints:
• Low-level hardware corruption, such as corrupt memory (RAM)
• Mismatched memory modules
• A malfunctioning motherboard
Other links point to problematic software programs.
Suspecting driver issue, but reinstalling the correct driver doesn't help. It crashes again with the same Blue Screen. So what is next? What options do we have?
Lets us zoom in....
So, is it a hardware or software problem?
Suddenly, I though of an idea. Why don't we test Linux out and there is no harm (and fun) testing ? Pump in Linux live cd and then connect to my hotspot. If it is able to detect and connect to my hotspot, then we know that there could be problem with Windows and the probably some corrupted software drivers. If it is a hardware issue, then connecting via Linux would likely fail as well. Then we can get the hardware replaced. That would simplify matters. Tested and able to get connected.
Format it and reinstall Windows 7 and start from scratch. Tested if is able to connect to wifi. It does! Cheers!
References:
http://support.microsoft.com/kb/137539
http://support.microsoft.com/kb/822789
- wong chee tat :)
Labels:
2014,
computer network,
computer networking,
feb,
mobile network,
network,
Window Vista,
Windows,
Windows 7,
Windows XP,
wireless
Subscribe to:
Posts (Atom)