Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - rama

Pages: [1]
1
22.03.2015

email from     support@zte.com.cn
Sub: Unable to safely eject zte data card Ac2739.

thanks for contacting us. Since we are responsible for ZTE system equipment after sales service, we have forwarded your mail to our mobile Dept. Sorry for the inconvenience, wish you a nice day!

Dear Mobile Dept. Colleagues,
Please handle this issue for our respected customer at earliest, thanks!

23.03.2015

email from     mobile@zte.com.cn
Thanks for contacting ZTE.

For more assistance you can contact our ZTE Indian customer service at 1800 103 1900 from Monday to Friday between 9 AM to 5 PM .


email from me to   mobile@zte.com.cn, cc to support@zte.com.cn
I contacted the ZTE Indian customer service at 1800 103 1900, and after inquiring about what OS I am using etc, he asked me to contact Reliance and gave me the toll-free number. Since this is a technical matter and has nothing to do with Reliance, I didn't contact them. I'm just passing on this info to you.

email from     mobile@zte.com.cn
Thanks for contacting ZTE.

For this issue, please contact the local dealer where you purchased the device to or network operator to consult.

Should there be further assistance, please do not hesitate to contact us.


24.03.2015

I went to the Reliance outlet where I bought the modem and told them the email details. They said the issue is not related to them, and there mighty be something wrong with my laptop.

So I thought out a workaround - uninstall the modem which is installed as cd-rom drive through the device manager. The hitch is that you can't normally run the device manager as administrator when logged in as a standard user. The solution is to type devmgmt.msc in the search box, and then right click and use the  run as administrator menu.

Regards,
Rama.     

2
That's right, they were clueless! I've sent an email to support@zte.com.cn, let's see how it goes.

Regards,
Rama.     

3
I ran Driver Verifier for 48 hours continuously before reinstalling Vista, and it didn't find any error. 
Moreover, the same BSOD appeared while trying to install the modem with  freshly loaded Vista. It is more likely that the conflict is in Vista itself.

The bios has a 'set to default' option, which I had used before reinstallation, and now also, but it has made no difference.

Problems with this sort of modems are reported mainly in the linux system, like http://www.wikihow.com/Connect-Reliance-Broadband%2B-Zte-Modem-in-Linux-%28Using-Usb_Modeswitch%29  and http://en.wikipedia.org/wiki/Virtual_CD-ROM_switching_utility. I inquired with the local Reliance outlet if anyone has reported this problem, and they said 'No'.

I tried another tactic. Using the Autoruns program I disabled cdrom.sys, and tried to install the modem, but couldn't. With cdrom.sys disabled, Windows didn't try to install drivers when the modem was inserted. Running the modem's installation program also got stuck, because the device was not recognized when inserted as prompted.   I can't understand why usb drivers were not installed, or the device was not run with the already installed usb drivers.

Regards,
Rama.     

4
Rolling back the drivers has made no difference. I still think that the memory issue is linked to the very old bios, for which I could find no updates.

I checked the Disk Management and found that the DVD drive has been allocated "G", the same as under "Computer". There is no mention about the Usb modem when it is not plugged in. Once plugged in, it is shown as a cd-rom drive "H", file system is CDFS, and Disk Management says "Healthy (Primary Partition). Under "computer", it is shown as "Cd drive H", but further exploring shows that it is installed as 2 devices, "usb storage FFF1 usb device" and "cd-rom drive" with location "on usb mass storage device". Similarly, under device manager, it is found under "modem" as "usb modem FFF1" and under "DVD / CD-ROM drives" as  "cd-rom drive".

Here's the Vista blue screen Stop Code

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
0x1000007e   0xc0000005   0x9e206c19   0x80760bf8   0x807608f4   cdrom.sys+6c19            

Regards,
Rama.      

5
Okay, I got your point. I downloaded the relevant drivers and utilities from http://support.toshiba-tie.co.jp/windows7/download/Satellite_A100_32_sp.htm and installed. All of them installed without problem, except the Intel Chipset SW Installation Utility, which reported that the minimum requirements are not met. I downloaded the ATI RADEON XPRESS 200M Series driver from Cnet Download, which installed without problem. After restart, I uninstalled and reinstalled the modem. However, it is still recognized as a cdrom drive, and also 1Gb RAM only is detected.

Regards,
Rama.   

6
Before I reinstalled Vista, I checked the Toshiba site for driver and bios update. Though some updates were available for satellite A100 at http://pc.toshiba-asia.com/mn/support/legacy-drivers, no update was available for my model PSAAKL - they were specific about model number. Now I found that updates for Windows 7 for all A100 have been posted at http://support.toshiba-tie.co.jp/windows7/download/Satellite_A100_32_sp.htm. As per the recommendation found there, I downloaded  Toshiba Service Station 2.2.9 from http://www.support.toshiba.com/support/viewContentDetail?contentId=4003322 and ran it. It reports that no software updates are available. I remember Drive the Life downloading and installing some drivers, and it seems to have done the job adequately.

Regards,
Rama.   

7
 dxdaig under the System tab mentions Genuine Intel(R) CPU T2080 @1.73GHz. I have re-run the Intel Driver Update Utility, but it doesn't list any driver as available - neither under Latest Drivers nor Old Drivers. I tried the Add legacy hardware wizard, and it said that it didn't find any hardware.

Regards,
Rama.

8
I too would prefer to unplug the modem after shutting down the laptop most of the time, but I think there is no harm in deviating in special circumstances.

No "Problem Devices" have been listed under System info.

Directx,  as Speccy did, mentions ATI RADEON XPRESS 200M Series. The AMD tool says "We are unable to find a driver for your system". However, I don't think there is a problem with drivers, except this modem case. Earlier, two devices were marked with driver errors in device manager, but Drive the Life has taken care of that. The Bios is Phoenix 5.40  but unfortunately there is no update available in their or Toshiba's  site.

Regards,
Rama.   

9
Finally it seems that I have found workarounds for the two problems.

First, the ejecting problem. According to http://www.windows7library.com/blog/performance/usb-quick-removal-option/, "Removing USB flash memory devices from your computer does not require you to use the Safely Remove Hardware and Eject Media function if the removal policy is set to default.". I first came to know of this from the comments of "Zibrz" at http://www.pcworld.com/article/2040932/how-to-safely-remove-a-usb-drive-even-when-windows-says-it-isnt-safe-to-do-so.html , so all thanks to him. I've also considered the warning at http://www.howtogeek.com/118546/htg-explains-do-you-really-need-to-safely-remove-usb-sticks/ , but I still think it is safe because of the following reasons.

1. I will be pulling out the modem only after disconnecting from the internet and closing the modem's interface.
2. There is 0 bytes free of 46.4 MB in the modem, so there is no possibility of Windows or other programs writing to it.

If there is any error in my reasoning, or if anyone has some relevant info that I'm unaware of, please post.

Second, the autoplay problem . I have gone to Control panel - Hardware and Sound - Autoplay and changed the option to "take no action" for the very first item in the list- Audio CD. Now when I insert the modem, the  autoplay menu doesn't open, but the modem's interface opens and gets ready to connect to the internet. I have confirmed that this change only has made the difference, because I haven't made this change in another User Account, and there Autoplay menu opens when the modem is inserted. Don't ask me what's the connection between playing an audio cd and opening a modem's interface, you'll have to  ask MS that!

Regards,
Rama.   

10
Thank you very much Boggin for your  untiring help. My video card is ATI RADEON XPRESS 200M Series. Before reinstalling Vista, I had indeed tried the AMD tool as well as the Intel tool, but they did not find any drivers to install.

I forgot to tell you yesterday that the Maximum memory box is under the advanced boot options (msconfig - system cofiguration - Boot - Advanced options). It seems to indicate more and more towards  the Bios, considering the fact that the system originally came with a 512 MB RAM   (and 80 GB HDD).

I found out something very important today. When the modem installed and worked in Windows 7, my relief was so great that I failed to check what driver Windows has used. I checked now and found it that it is none other than the villain of the past month - cdrom.sys. Now we can understand what has been happening. When I inserted it in Vista, Widows tried to install it with cdrom.sys, which created a conflict, and Vista crashed, correctly blaming cdrom.sys. Windows 7 seems to be more tolerant and is working, but taking it as a cdrom, which of course can not be ejected, but can be uninstalled from the device manager.

Regards,
Rama.                                                                                                                                                               .                                               

11
Uninstalling the DVD drive then rebooting has made no difference. http://answers.microsoft.com/en-us/windows/forum/windows_vista-hardware/why-does-windows-7-think-my-usb-modem-is-a-cd-rom/1c5be829-0e97-4900-a80c-344dab4f58ff clearly says that the issue was there in two different makes. Also, the zte modem is a self-contained unit, and is also working perfectly. I'm sure Windows is messing up with the drivers, because when I first reinstalled Vista and installed Sony Ericsson PC companion, Vista tried to install drivers and BSODed.  When I tried again, Sony Ericsson PC companion said "don't let windows install drivers", and somehow managed to install its own drivers. After installation it worked perfectly, but Vista showed an error in Device Manager that drivers are not properly installed.

As far as chipset drivers are concerned, there is no support for this model in Toshiba site, not even in the legacy category.

Regards,
Rama.








12
During the past month, I have come to see the seamy side Of Windows. Now I have the same problems as at http://answers.microsoft.com/en-us/windows/forum/windows_vista-hardware/why-does-windows-7-think-my-usb-modem-is-a-cd-rom/1c5be829-0e97-4900-a80c-344dab4f58ff, and have to shut down the computer if I want to safely remove the modem. I've decided to let it be and ignore the "solutions" suggested by MS, lest Windows messes up and renders the modem inoperable like it did in Vista.

Regarding the rules at the Vista forum, this is what they say:

This site includes links to other sites on the world wide web. We are not responsible for such sites and cannot vouch for the suitability or accuracy of their content. You link to them at your own risk.

though they also say

The owners of [ARG:2 UNDEFINED] reserve the right to remove, edit, move or close any thread for any reason.

Regards,
Rama.


13
Thank you Boggin.

I posted at the other forum immediately after posting here, but that post has been removed, and I didn't get any messages. Being a Vista forum, may be they were reluctant to let it be known how Vista failed, and there was no help.

I noticed a curious thing about the memory . In Vista, like I said, the Max Memory box won't go above  800 something, and in Windows 7 it won't go above 1024. May be somebody has an insight into this.

Regards,
Rama.

14
Even once again reinstalling Vista and immediately trying to install the modem in safe mode resulted in the same old BSOD. It looked more and more likely that Vista is messing up things. Having struggled with this for a month, I decided enough is enough, and installed Windows 7, which had no problem in installing the modem even in regular mode.

I'd like to record my heartfelt gratitude to Shane, Boggin and Heyroxie for taking the time and effort to help me out.

I had posted this problem at http://www.vistax64.com/crashes-debugging/303557-bsod-installing-zte-data-card-ac2739.html some weeks back. The thread has had more than 1700 views, whish shows the keen interest this problem has created. I'll post there and give a link to this thread, so that more people come to know about this place and utilize it.

Regarding memory non-detection problem, in the absence of other explanations, we can attribute it to the very old BIOS, and leave it at that.

Thank you once again, one and all.

Regards, 
Rama.

15
Thank you very much for the input, you certainly have the right idea. Since Windows has been reporting that the drivers are up to date, I ran a free Driver Manager called "Drive The Life" to scan the drivers. Sure enough, it pinpointed the 3 drivers you mentioned ( NIC, Atheros and Display) plus one motherboard driver as needing repair. It downloaded them and installed, but the Display driver is not digitally signed and needs restart, so I restarted and inserted the  modem - BSOD. So next time I inserted the  modem without restarting - again BSOD. After some trials, I found out that Windows reinstalls the old display driver when it reboots. Finally I just uninstalled all the 3 items in safe mode and inserted the modem without giving Windows a chance to reinstall them - still the same old BSOD blaming cdrom.sys. I don't understand how a freshly installed OS can have driver errors.

Also, please clarify whether the other people had problem installing the modem, or running it after installation.

Regarding the other points, after reinstallation of Vista, there's no IE in the laptop.

I ran sfc /scannow. Here's the info about "can not repair". I think we can safely ignore the "gpedit" entries, since they were created yesterday only. I don't understand any of the others, and somebody knowledgeable will have to interpret them.

Regards,
Rama



POQ 51 ends.
2015-03-13 16:39:13, Info                  CSI    00000132 [SR] Verify complete
2015-03-13 16:39:14, Info                  CSI    00000133 [SR] Repairing 4 components
2015-03-13 16:39:14, Info                  CSI    00000134 [SR] Beginning Verify and Repair transaction
2015-03-13 16:39:14, Info                  CSI    00000135 Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-fde_31bf3856ad364e35_6.0.6000.16386_none_a5d5397a5ec02105\fde.dll do not match actual file [l:14{7}]"fde.dll" :
  Found: {l:32 b:ofJrYBMvfbcRFAtPFwvTqckgU78Xi+9tWAnhLEg79/w=} Expected: {l:32 b:CZev8RyTePmcz/iNnXxsP21L7UrUSFJLD/c3nLJjKmd=}
2015-03-13 16:39:14, Info                  CSI    00000136 [SR] Cannot repair member file [l:14{7}]"fde.dll" of Microsoft-Windows-fde, Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-03-13 16:39:14, Info                  CSI    00000137 Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-fdeploy_31bf3856ad364e35_6.0.6000.16386_none_dd7ed04153d3440b\fdeploy.dll do not match actual file [l:22{11}]"fdeploy.dll" :
  Found: {l:32 b:X2Mxr15BWaSKXy2mybUslwVk9Y/FqInLy5D57coBHZA=} Expected: {l:32 b:h/n4DaywC5cZowEPvzatqmZJqn3OAVxEom2aWKV56Vx=}
2015-03-13 16:39:14, Info                  CSI    00000138 [SR] Cannot repair member file [l:22{11}]"fdeploy.dll" of Microsoft-Windows-fdeploy, Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-03-13 16:39:14, Info                  CSI    00000139 Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-grouppolicy-gptext_31bf3856ad364e35_6.0.6000.16386_none_35190a8e921bbf42\gptext.dll do not match actual file [l:20{10}]"gptext.dll" :
  Found: {l:32 b:4R/wpzngnfdc0a94M7qP6Hg+i5N+LV89wlqPbSNLqTt=} Expected: {l:32 b:nHTHvUBGGBqit4oUTvrcam63/8I5zfU11jkc5Iw01Y8=}
2015-03-13 16:39:14, Info                  CSI    0000013a [SR] Cannot repair member file [l:20{10}]"gptext.dll" of Microsoft-Windows-GroupPolicy-Gptext, Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-03-13 16:39:14, Info                  CSI    0000013b Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-g..policy-admin-gpedit_31bf3856ad364e35_6.0.6000.16386_none_cbfb6a9967fc57b1\gpedit.dll do not match actual file [l:20{10}]"gpedit.dll" :
  Found: {l:32 b:kr66STTQJj/SGCfMluAmidqauu1XH+iINrNGn3DUoo7=} Expected: {l:32 b:YRuQ0/4v6elpjn/fZ1RsgTAHbfRMZUm7+4XQcKq14T6=}
2015-03-13 16:39:14, Info                  CSI    0000013c [SR] Cannot repair member file [l:20{10}]"gpedit.dll" of Microsoft-Windows-GroupPolicy-Admin-Gpedit, Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-03-13 16:39:14, Info                  CSI    0000013d Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-grouppolicy-gptext_31bf3856ad364e35_6.0.6000.16386_none_35190a8e921bbf42\gptext.dll do not match actual file [l:20{10}]"gptext.dll" :
  Found: {l:32 b:4R/wpzngnfdc0a94M7qP6Hg+i5N+LV89wlqPbSNLqTt=} Expected: {l:32 b:nHTHvUBGGBqit4oUTvrcam63/8I5zfU11jkc5Iw01Y8=}
2015-03-13 16:39:14, Info                  CSI    0000013e [SR] Cannot repair member file [l:20{10}]"gptext.dll" of Microsoft-Windows-GroupPolicy-Gptext, Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-03-13 16:39:14, Info                  CSI    0000013f Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-g..policy-admin-gpedit_31bf3856ad364e35_6.0.6000.16386_none_cbfb6a9967fc57b1\gpedit.dll do not match actual file [l:20{10}]"gpedit.dll" :
  Found: {l:32 b:kr66STTQJj/SGCfMluAmidqauu1XH+iINrNGn3DUoo7=} Expected: {l:32 b:YRuQ0/4v6elpjn/fZ1RsgTAHbfRMZUm7+4XQcKq14T6=}
2015-03-13 16:39:14, Info                  CSI    00000140 [SR] Cannot repair member file [l:20{10}]"gpedit.dll" of Microsoft-Windows-GroupPolicy-Admin-Gpedit, Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-03-13 16:39:14, Info                  CSI    00000141 Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-fdeploy_31bf3856ad364e35_6.0.6000.16386_none_dd7ed04153d3440b\fdeploy.dll do not match actual file [l:22{11}]"fdeploy.dll" :
  Found: {l:32 b:X2Mxr15BWaSKXy2mybUslwVk9Y/FqInLy5D57coBHZA=} Expected: {l:32 b:h/n4DaywC5cZowEPvzatqmZJqn3OAVxEom2aWKV56Vx=}
2015-03-13 16:39:14, Info                  CSI    00000142 [SR] Cannot repair member file [l:22{11}]"fdeploy.dll" of Microsoft-Windows-fdeploy, Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-03-13 16:39:14, Info                  CSI    00000143 Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-fde_31bf3856ad364e35_6.0.6000.16386_none_a5d5397a5ec02105\fde.dll do not match actual file [l:14{7}]"fde.dll" :
  Found: {l:32 b:ofJrYBMvfbcRFAtPFwvTqckgU78Xi+9tWAnhLEg79/w=} Expected: {l:32 b:CZev8RyTePmcz/iNnXxsP21L7UrUSFJLD/c3nLJjKmd=}
2015-03-13 16:39:14, Info                  CSI    00000144 [SR] Cannot repair member file [l:14{7}]"fde.dll" of Microsoft-Windows-fde, Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-03-13 16:39:14, Info                  CSI    00000145 Repair results created:
POQ 52 starts:
 
POQ 52 ends.
2015-03-13 16:39:14, Info                  CSI    00000146 [SR] Repair complete

16
Thank you Shane for the info. I guess I was taken in by the patching disclaimer at the top of the page, and didn't read the post carefully. I have now downloaded and run the file, which installed  gpedit without any problem. However, my (Vista) version doesn't have any "Device Installation" folder under Computer Configuration->Administrative Templates->System, nor any option for "Prevent Installation of Devices not described by other policy settings". The only relevant option it has is "turn off windows update device driver search prompt". I enabled this, but as it pertains to update, it seems to be no use at the present situation.

Regards,
Rama.

17
Thank you Shane for the input. I had already seen that post, but it won't work, because Home basic editions don't have Group Policy Editor (gpedit.msc) installed. There is a patch for that, but I don't want to try it, because I don't know typing, and am not comfortable with patching. However, I will post the link here in case it benefits somebody else.

Regards,
Rama

http://www.askvg.com/how-to-enable-group-policy-editor-gpedit-msc-in-windows-7-home-premium-home-basic-and-starter-editions/

18
Thank you Shane and Boggin for your inputs. I had indeed run TDSSKiller before re-installing Vista, and it found no infection. As for as cdrom.sys is concerned, the driver is fresh from the re-install from the OEM original DVD.

I went to safe mode and disabled the display driver and inserted the modem. Still the same BSOD blaming cdrom.sys.

 msconfig does have a Max Memory check box, which was already unchecked. When I checked it, it showed 800 something and wouldn't go up by clicking the button. When I physically entered 1900, it returned to 800 something. There is no memory options in the BIOS.

Regarding BSOD, is there a way to actually stop auto-installation of drivers, and force it to install the drivers I have?

Regards,
Rama.

19
Position as on 13.02.2015

My Toshiba Satellite A100 - PSAAKL - 00M008 runs on genuine Windows Vista Home Basic - SP2 with auto updates enabled and is up-to-date. Though the system is slow (old model), and the Bios is 2007, there has been no major problem. However, when I tried to install zte data card Ac2739, windows consistently blue screens. I've ascertained that there's no problem with the data card itself. I have done the memory test, checkdisc, and sfc /scannow, but no issues. I've tried to install it in Safe Mode, Clean Boot Mode and with Avast disabled, but no go. Whocrashed says the probable culprit is cdrom.sys, but the installed driver version (2006) is the latest one. I've  disabled the driver and tried to install the data card, but still the same result.
The USB port is ok, since I am using it to access GPRS through my phone.

I ran Driver Verfier for 48 hours continously, but no BSOD.

Position as on  09.03.2015

As a last resort, I re-installed Vista from my OEM disk - with no service packs. Still, the BSOD occurs when I try to install the modem. I think Vista is causing the BSOD by trying to install the wrong drivers. I've tried to prevent Vista from installing drivers by selecting the "do not install drivers" option from "Advanced System Settings - Hardware",but Vista still tries to install drivers, which results in an immediate BSOD. I've got the Reliance Netconnect software with drivers, but Windows is doing its own driver installation and BSODing.

There is another problem, doesn't seem to be related. After the Original 512 MB RAM failed, I've been using a 1 GB RAM in one of the slots. Now, because of the increased load, I've added another 1 GB RAM to the other slot, but both the BIOS and Windows show only 1 GB RAM. I've ascertained that both the sticks and both the slots work fine. Speccy and CPU-z also report 2GB RAM.I couldn't find any update for the bios.

I have uploaded the latest specs and mimidumps.

Any help is appreciated. Thank you.
Rama.

http://speccy.piriform.com/results/FK4TMhaINdRZasO3ZVEINUZ

Pages: [1]