Sir,can you help me?
-
This is by design. Ultimately if you do this enough times it will ruin the USB "Pen" drive. The operating system mounts a virtual file system and needs to unmount it to leave the memory on the "Pen" drive in a useable state. Things that trigger a Blue Screen that are obvious (like this) probably should not be repeated. This is not a software problem it's hardware.
I only read CP for the articles. Code-frog System Architects, Inc.
Hi! Code-frog, Thank you very much! If I do the same on win2000 and winXP it never trigger a Blue Screen. I know that Win2000 and WinXp have their own USB pen disk drivers. I can not understant that it's a hardware problem but not a software. So what couses the difference phenomena on win98 and win2000(WinXp)? Thanks! momer
-
yeah, i understood the question... i only said that there was no need to ask it many times on many forums at a time. well, for your question, i am not sure about the answer, that's why i didn't let you my thought. i actually think that there's nothing you can do again that blue screen under Windows95/98/ME... but i may be wrong.
TOXCCT >>> GEII power
[toxcct][VisualCalc 2.24][3.0 soon...]"i actually think that there's nothing you can do again that blue screen under Windows95/98/ME... but i may be wrong." yeah,i think maybe you are wrong. Couse the usb pen disk driver can do more work after the pen disk removed suddenly. So what about your opinion? thanks! momer
-
Hi! Code-frog, Thank you very much! If I do the same on win2000 and winXP it never trigger a Blue Screen. I know that Win2000 and WinXp have their own USB pen disk drivers. I can not understant that it's a hardware problem but not a software. So what couses the difference phenomena on win98 and win2000(WinXp)? Thanks! momer
It's really a moot point. "Surprising" the driver with an unexpected removable of the device will result in data corruption. You just don't do it. If the volume on that stick is not dismounted properly, you stand a LARGE chance of corrupting the contents of the stick. Then, a Blue Screen of Death will be the least of your problems. RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
-
It's really a moot point. "Surprising" the driver with an unexpected removable of the device will result in data corruption. You just don't do it. If the volume on that stick is not dismounted properly, you stand a LARGE chance of corrupting the contents of the stick. Then, a Blue Screen of Death will be the least of your problems. RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
Hi! Dave, Thank you very much! Yes,except testing my driver I never remove the device whilt it exchage data with pc,but I can never sure about that my customer never do it. I wish my customer can use my pen-disk on win98 system just like they use it on win2000 or winXp system. So,sir,pls give me your suggestion. Thanks! momer All the blesses we enjoy are the fruit of labor,toil,study and self-denail.
-
Hi! Dave, Thank you very much! Yes,except testing my driver I never remove the device whilt it exchage data with pc,but I can never sure about that my customer never do it. I wish my customer can use my pen-disk on win98 system just like they use it on win2000 or winXp system. So,sir,pls give me your suggestion. Thanks! momer All the blesses we enjoy are the fruit of labor,toil,study and self-denail.
No ideas, cause I haven't written for 9x systems in a VERY long time, and never a device driver. You're talking about writing a device driver for a system that hasn't been supported by Microsoft in ages. Help on this is going to be extremely difficult to come by, if for no other reason, no one has anything to test the code on! RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
-
Hi! I had download the source code of mass storage device driver for windows98 from Microsoft websit.And builded it with 98ddk on windows98 system,and then installed it on win98 system. It can work correctly all the time. If I suddenly remove the device from pc when copying file from pc to device or from device to pc on win98 system,the blue screen occur,and i have to restart my system. But if do the same on win2000 or winxp there is no blue screen. Now i wanna modify the driver source code to avoid the blue screen when suddently remove the device while it is exchanging data with pc on win98 system. My question is: 1,If my hope has the possibility to come true? 2,If has,then which part of source code of this drive should i have to modify,and what couses the blue screen? I know that in the source code it just abort all the pipes when device remove sudently but nothing else. Thanks! momer All the blesses we are enjoy are the fruit of labor,toil,study and self-denail.
When i had Win98 a lot of driver shows blue screen, to remove without blue screen, you should go to safe mode.
-
No ideas, cause I haven't written for 9x systems in a VERY long time, and never a device driver. You're talking about writing a device driver for a system that hasn't been supported by Microsoft in ages. Help on this is going to be extremely difficult to come by, if for no other reason, no one has anything to test the code on! RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
-
When i had Win98 a lot of driver shows blue screen, to remove without blue screen, you should go to safe mode.
-
Yeah,I know it. But my problem is how to modify my driver code to avoid the blue screen,and no need to go to safe mode. Thanks!
It's up to you to debug your driver code and find out why it's causing the BSOD. There's no one thing you can do to fix it. You have to find the bug and correct it, or implement the code to handle the situation that causes it. But, it all starts with you and the kernel debugger... RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
-
It's up to you to debug your driver code and find out why it's causing the BSOD. There's no one thing you can do to fix it. You have to find the bug and correct it, or implement the code to handle the situation that causes it. But, it all starts with you and the kernel debugger... RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome