network 1 and i don t mean rename the Results

Sponsored Links:


I have a huge problem with my win 7 network. The initial problem started when I had to connect to the internet via USB (HTC Hero internet sharing) when I first did this, I had to install drivers from vista x64. But I eventually got it working. Or at least I thought.

Next time I booted up windows, it could still find the network, but not access the internet. So I eventualy uninstalled the HTC Hero NDIS driver from "Device manager" and installed it again. Once again I found myself online. But this time only for 5 hours, and this time the network was called "Network 2" in the Network and Sharing Center

I was quickly on my "network 4"
Eventually I got my DSL internet to work (on wireless), so I didn't need the USB network anymore. But with this new network I couldn't connect via the cable eighter since the "Network Sharing Center" show 2 networks when I'm on cable, both the network 4 (with internet access) and another network which cannot connect to the internet. I think this is where the problem lies, this extra connection is messing with the internet line.

So my question is this: How do I start over, so the next time I add a network it will be called network 1. And I don't mean rename the connection. But how to uninstall all previous networks so I can start over?

Regards Anders Berg

A recent news-handling problem has brought this one back, so I thought
I'd bring it up again.


I have a - non-networked - Windows 95 system, used for testing some
equipment. These tests create log files ON ITS HARD DISC (usually the
desktop, for convenience; they're only 41k files, in threes). As part of
our procedure, these log files have to be stored on our company network;
the procedure we use to do this is to copy them onto a floppy disc on
the '95 machine, carry it the few yards to the networked XP machine
which has a USB floppy drive, and copy the files to the network drive.
lost, so no recovery is necessary. The files are still there on the
desktop (hard drive) of the '95 system.

(Sorry for shouting, but throughout this thread, people have very kindly
spent a lot of time trying to help with recovery, which isn't needed.)

Purely out of perversity, I continue to use the floppy with the bad
sectors; I have other work I can do while waiting (or, if not, I use a
good floppy).

1. 95 machine. After experiencing problems, I rescan the floppy, on the
'95 machine, so that any newly-bad sectors get marked. (I'm curious as
to whether a scan rescans already-marked-as-bad sectors; I think it must
do, as it seems to take longer each time, whereas I wouldn't expect it
to if it was skipping already-marked-as-bad sectors.) While _doing_ this
scan, the '95 machine still lets me do other things, just incredibly
slowly, which puzzles me, though I accept what some people here have
said about low-level drivers and the like. (I don't have - nor the means
to install - any utilities, such as resource meters, that aren't part of
the basic '95 system.)

2. XP machine.
(a) When it is having problems reading the floppy, it goes through this
cycle many times: floppy drive light on and floppy turning; light off
and not turning _for several seconds_. (_What_ is it doing during that
time?) After many such cycles, it reports a problem. Until it does, it
becomes unresponsive in explorer windows, though I can do other things.
(b) If I try to close the explorer window with the X before it has given
up, it usually ignores me. If I close it with task manager, it does
close it, but is obviously upset: it blanks where the taskbar was
(eventually redrawing it), and does various other things which show it
isn't happy, including closing any other explorer windows (such as the
one showing the network drive I was copying the files to), _and these
are really closed and don't come back_, so it's not just an
incredibly-slow-redraw matter.
(c) After such, whether I wait (ages) for the error message or terminate
the process, it seems to have some "memory" that there was something
wrong: attempts to read even an OK floppy often don't work. I find
either closing the explorer window that was looking at drive A:, or
unplugging the USB floppy drive and putting it back (I usually use
another socket), make it read OK again.

(I report these as just curiosities that will probably now never be
solved - that project is coming to an end, so I won't have much
opportunity to investigate further - I think.)

(Read on ...)

In message , Twayne
In ,
J. P. Gilliver (John) typed:
On the XP system, if the read fails, it also seems to
lock up the system. I don't know _what_ it is doing: it
sits there, not even accessing the floppy continuously -
the light comes on for a few seconds, then goes off for a
few seconds, and eventually - sometimes after a minute or
more - comes up with an error message; again, the system
is a little sluggish to do anything else, though nothing
like as much so as the '95 system. But what is really
weird is that it seems to sulk where the floppy is
concerned: once it has decided there is a problem, it
refuses - by going into the
mode - to do _anything_ with the floppy, even delete or
rename a file, _or use a (different, good) floppy.
Sometimes, if I think it has locked up completely, I kill
the process with Task Manager, which works - XP is more
robust that way - but from the way it does it, it is
clearly having a _major_ effect: it usually closes _all_
explorer windows, blanks and eventually redraws the
taskbar, breaks iconoid, redraws the desktop, and so on.
Again, I can't see why doing something as trivial as
accessing a floppy - even if it's dud - should have such
a major effect on the system. (I also think the XP system
is less tolerant of the poor floppy.)
I repeat, I _know_ a good floppy is only pennies, and I
have one: it's just the principle that bugs me, of why
doing such a nominally simple thing should cripple both
systems so much.
(I've included the '98 newsgroup as I thought they might
be interested/have views/answers.)

Everyone who has responded so far has given good information. Taken
together, IMO they give a good picture of what's going on. A bit higher
level explanation might go thusly:

Being magnetic, floppy disks do lost their data over time as short as 6
[All good stuff but not an explanation of why the OSs are behaving as
they are.]
There are DOS programs around that are meant to "recover" decaying
floppies. Mine seems to be lost in the archives somewhere; all I see left is

And dud HDs - I forget the name, but we have one that will sit trying to
read a sector for ages; we left it for several days trying to salvage
something from a (I think it was all of 20M!) drive that had come with a
piece of equipment (from a division that was being closed down and
nobody knew where the backups were for this ancient equipment; I am sure
there would originally have been such).

the WordStar to Word converter, meaning several others are hiding away from
me too.
The "recover floppy" program did a lot better and more efficient job than
anything you could do manually and was often surpsingly effectively. I guess
Google would be the best way to find it now.

As I've explained, the data isn't lost (it's still on the machine it's
being copied from); I'm just curious as to why the OSs (if anything,
particularly the XP one; I accept a slowdown for the '95 one, at least
that's sort of understandable) are behaving as they do.

As for locking up the sy

(Not sure what happened there.)
J. P. Gilliver. UMRA: 1960/1985 MB++G.5AL-IS-P--Ch++(p)Ar@T0H+Sh0!:`)DNAf

# 10^-12 boos = 1 picoboo # 2*10^3 mockingbirds = 2 kilo mockingbird
# 10^21 piccolos = 1 gigolo # 10^12 microphones = 1 megaphone
# 10**9 questions = 1 gigawhat

BSOD error message

0x0000007f (ox0000000000000008, 0x0000000080031, ox00000000000006f8, oxfffff800028dabd0)

Just curious what the stuff in the parenthesis means? i believe ox7f is hardware/driver issue, but i'm not a doctor. i don't know.

This has been happening it seems almost randomly. I have been working my computer pretty hard but i expect the best. I was pondering replacing some parts because I realize machines get old. shouldn't be, but the first thing i'm addressing is heat. new computer case in the mail for more fan room, and the first building block when i build a new system

OS Name Microsoft Windows 7 Home Premium
Version 6.1.7601 Service Pack 1 Build 7601
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name TIMMY-PC
System Manufacturer BIOSTAR Group
System Model TA790GX 128M
System Type x64-based PC
Processor AMD Phenom(tm) II X4 940 Processor, 3000 Mhz, 4 Core(s), 4 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. 080014, 1/13/2009
SMBIOS Version 2.5
Windows Directory C:Windows
System Directory C:Windowssystem32
Boot Device DeviceHarddiskVolume2
Locale United States
Hardware Abstraction Layer Version = "6.1.7601.17514"
User Name Timmy-PCTimmy
Time Zone US Mountain Standard Time
Installed Physical Memory (RAM) 6.00 GB
Total Physical Memory 6.00 GB
Available Physical Memory 4.51 GB
Total Virtual Memory 12.0 GB
Available Virtual Memory 10.3 GB
Page File Space 6.00 GB
Page File C:pagefile.sys

Just in case you need that.

Thanks for your help! Attached Files W7F_13-04-2013.rar (287.1 KB, 21 views) Share Share this post on Digg Technorati Twitter
Reply With Quote .postbitlegacy .postfoot .textcontrols a.post_info_button, .postbit .postfoot .textcontrols a.post_info_button { background: url(/images/post_infobox.png) no-repeat transparent left; padding-left: 20px; } .postbitlegacy .postfoot .textcontrols a.post_info_button:hover, .postbit .postfoot .textcontrols a.post_info_button:hover { background: url(/images/post_infobox-hover.png) no-repeat transparent left; JavaScript must be enabled 04-14-2013 #2 usasma Microsoft Community Contributor This member is a certified Microsoft Community Contributor at Windows 7 Forums. Click here for more information from Microsoft. Microsoft MVP - Windows Expert
- Consumer
Join Date Mar 2010 Posts 1,333 Re: BSOD - w7f and error codes attached Info on the STOP 0x7F error: BSOD Index
Please note the "Usual Causes" section up near the top of that section
Also, you'll have to scroll down to see what the stuff in the parentheses means:
Code: WinDbg Help File Entry: The UNEXPECTED_KERNEL_MODE_TRAP bug check has a value of 0x0000007F. This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap. This trap could be a bound trap (a trap the kernel is not permitted to catch) or a double fault (a fault that occurred while processing an earlier fault, which always results in a system failure).Parameters The first parameter that appears on the blue screen specifies the trap number. The most common trap codes include the following: 0x00000000, or Divide by Zero Error, indicates that a DIV instruction is executed and the divisor is zero. Memory corruption, other hardware problems, or software failures can cause this error.0x00000004, or Overflow, occurs when the processor executes a call to an interrupt handler when the overflow (OF) flag is set.0x00000005, or Bounds Check Fault, indicates that the processor, while executing a BOUND instruction, finds that the operand exceeds the specified limits. A BOUND instruction ensures that a signed array index is within a certain range.0x00000006, or Invalid Opcode, indicates that the processor tries to execute an invalid instruction. This error typically occurs when the instruction pointer has become corrupted and is pointing to the wrong location. The most common cause of this error is hardware memory corruption.0x00000008, or Double Fault, indicates that an exception occurs during a call to the handler for a prior exception. Typically, the two exceptions are handled serially. However, there are several exceptions that cannot be handled serially, and in this situation the processor signals a double fault. There are two common causes of a double fault: A kernel stack overflow. This overflow occurs when a guard page is hit, and the kernel tries to push a trap frame. Because there is no stack left, a stack overflow results, causing the double fault. If you think this overview has occurred, use !thread to determine the stack limits, and then use kb (Display Stack Backtrace) with a large parameter (for example, kb 100) to display the full stack.A hardware problem. The less-common trap codes include the following: 0x00000001 A system-debugger call0x00000003 A debugger breakpoint0x00000007 A hardware coprocessor instruction with no coprocessor present0x0000000A A corrupted Task State Segment0x0000000B An access to a memory segment that was not present0x0000000C An access to memory beyond the limits of a stack0x0000000D An exception not covered by some other exception; a protection fault that pertains to access violations for applications For other trap numbers, see an Intel architecture manual.Cause Bug check 0x7F typically occurs after you install a faulty or mismatched hardware (especially memory) or if installed hardware fails. A double fault can occur when the kernel stack overflows. This overflow occurs if multiple drivers are attached to the same stack. For example, if two file system filter drivers are attached to the same stack and then the file system recurses back in, the stack overflows.Resolving the Problem Debugging: Always begin with the !analyze extension. If this extension is not sufficient, use the kv (Display Stack Backtrace) debugger command. If kv shows a taskGate, use the .tss (Display Task State Segment) command on the part before the colon.If kv shows a trap frame, use the .trap (Display Trap Frame) command to format the frame.Otherwise, use the .trap (Display Trap Frame) command on the appropriate frame. (On x86-based platforms, this frame is associated with the procedure NT!KiTrap.) After using one of these commands, use kv again to display the new stack. Troubleshooting: If you recently added hardware to the computer, remove it to see if the error recurs. If existing hardware has failed, remove or replace the faulty component. Run hardware diagnostics that the system manufacturer supplies to determine which hardware component failed. The memory scanner is especially important. Faulty or mismatched memory can cause this bug check. For more informaiton about these procedures, see the owner's manual for your computer. Check that all adapter cards in the computer are properly seated. Use an ink eraser or an electrical contact treatment, available at electronics supply stores, to ensure adapter card contacts are clean. If the error appears on a newly installed system, check the availability of updates for the BIOS, the SCSI controller, or network cards. These kind of updates are typically available on the Web site or BBS of the hardware manufacturer. Confirm that all hard disk drives, hard disk controllers, and SCSI adapters are listed in the Microsoft Windows Marketplace Tested Products List. If the error occurred after the installation of a new or updated device driver, you should remove or replace the driver. If, under this circumstance, the error occurs during the startup sequence and the system partition is formatted with NTFS, you might be able to use Safe Mode to rename or delete the faulty driver. If the driver is used as part of the system startup process in Safe Mode, you have to start the computer by using the Recovery Console in order to access the file. Also restart your computer, and then press F8 at the character-based menu that displays the operating system choices. At the Advanced Options menu, select the Last Known Good Configuration option. This option is most effective when you add only one driver or service at a time. Overclocking (setting the CPU to run at speeds above the rated specification) can cause this error. If you have overclocked the computer that is experiencing the error, return the CPU to the default clock speed setting. Check the System Log in Event Viewer for additional error messages that might help identify the device or driver that is causing the error. You can also disable memory caching of the BIOS to try to resolve the problem. If you encountered this error while upgrading to a new version of the Windows operating system, the error might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version. If possible, remove all third-party device drivers and system services and disable any virus scanners before you upgrade. Contact the software manufacturer to obtain updates of these tools. Also make sure that you have installed the latest Windows Service Pack. Finally, if all the above steps do not resolve the error, take the system motherboard to a repair facility for diagnostic testing. A crack, a scratched trace, or a defective component on the motherboard can also cause this error. WinDbg Output Example: UNEXPECTED_KERNEL_MODE_TRAP (7f) This means a trap occurred in kernel mode, and it's a trap of a kind that the kernel isn't allowed to have/catch (bound trap) or that is always instant death (double fault). The first number in the bugcheck params is the number of the trap (8 = double fault, etc) Consult an Intel x86 family manual to learn more about what these traps are. Here is a *portion* of those codes: If kv shows a taskGate use .tss on the part before the colon, then kv. Else if kv shows a trapframe use .trap on that value Else .trap on the appropriate frame will show where the trap was taken (on x86, this will be the ebp that goes with the procedure KiTrap) Endif kb will then show the corrected stack. Arguments: Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT Arg2: 0000000080050031 Arg3: 00000000000006f8 Arg4: fffff80002af243d There are no memory dumps included in the uploaded files, please zip up the contents of the C:WindowsMinidump folder and upload it with your next post. Please check this page to ensure the system is set to save minidumps: Set MiniDump Finally, don't use disk cleaning programs (such as CCleaner) while we're troubleshooting (they delete the files that we need).

Only 118 Windows Updates installed. Most systems have 150 or more. Please visit Windows Update and get ALL available updates (it may take several trips to get them all).

As there's no evidence of BSOD's in the WER section of MSINFO32, I'd have to suspect that this might be a hardware problem. Please start with these free hardware diagnostics: Hardware Diagnostics

Good luck!

re-format it and start over

-----Original Message-----
I am unable to install Sun's Java.
I know there's a whole fight between MS and Sun, but
still, I'd like to install it.

I have tried what they have suggested in their FAQs, and
I will enclude my letter to them which has information
that maybe useful to helping me problem solve this.

Their Response is that it is a "Windows Configuration
Problem." And then they say nothing more!!!!!!!!!

I don't have a clue as to what they mean by that, and if
it is a Windows Configuration problem what things should
I do to try to change that configuration?

This is what I wrote to them:

Dear Tech Support.

I am unable to install Java.

I will out line my role on the computer, My hard and
software, The Error message, and what I have tried.

My Role:

I am the sole owner/builder/Installer/administrator/only
user/ of this non-networked home PC used for non-business


Asus P4C800-E Deluxe Motherboard
2 GB DDR 400 RAM
Intel Pentium 4 3.2 GHz Processor
Adaptec 29320 Ultra320 SCSI Card
Segate SCSI 320 Hard drives
ATI Radeon 9800 XT Video Card
Soundblaster Audigy 2 Audio Card


Please be aware, that all of my Windows, drivers, and
programs are nerotically kept up to date!
Windows XP Home Ed. Service Pack 1
Internet Explorer 6+
Norton System Works 2004

Problem and Error Message:

I am unable to install Sun Java of any version
automatically or manually.

The install fails and gives the following message:

"Error 1722. There is a problem with this Windows
Installer Package. A program run as part of the setup did
not finish as expected. Contact your support personnel
or package vendor."

What I Have Tried:

I have:

Read the FAQs and trouble shooting section at the Java
web site.
Read the information about Error 1722 located at
Completed all of the instructions in that article.
Uninstalled all versions of Java from Control Panel
Add/Remove programs.
Deleted all folders with Java or Sun from C:,
C:documents and SettingsUser, and from C:Program files.
Renamed Java folder from C:Windows and moved it to a
different drive.
Ran Utility to remove all junk files, invalid registry
items, and cleaned out all temp folders.
In Windows Computer Management, services, I disabled
cyrptographic services and all services related to
Norton/Symantec. As well as doing this in MSCONFIG.
Rebooted and checked to make sure that all services that
I disabled were still disabled.
Cleaned out all my temp folders again.
Attempted to install J3re1.2.4.05 downloaded for
manually as instructed.

Same Error occured again. What can you suggest to me to
try next.

Thank You for your help


Please forgive -- I am a brand new user and don't even have navigation skills for this Website. Only registered a few minutes ago, and with so many threads I don't see any way to "search" if something like my question has been posed and answered in the past. Forgive my ignorance.

I have a question re. use of Office 2010 products in a school environment. I am a "refugee" from the mainframe database world, finally forced out and now teach at a community college. I have no MS certifications, but am merely a "computer guy" who was hired in a business dept. to teach two versions of beginning computer skills (meaning essentially introductions to Word, PowerPoint, and Excel, and possibly Access). One is for 4 year college students who will transfer out after 2 years, the other to those getting some sort of 2 year degree from the community college.

The textbook used is decided at the department level. The tests are "standardized," using a company that provides online testing, and the tests are put together by the "lead" instructor of those in the business dept. that teach these computer classes.

We have a network drive, which has lots of "starter files" for the students to use as they learn various beginner skills (and new functionality skills as we've moved from 2003 to 2007 to 2010 Office). The students copy these read-only versions from this networked drive on the school's server to their own computers, or flash drives, and then they follow their textbook instructions (lots of pictures) to produce a finished product. I review (i.e. grade) the finished products which they turn into me. These assignments are obviously for the purpose of getting them ready for the tests (which include interactive questions as well as T/F and multiple-choice).

Cheating has always been a small problem with these assignments, as a student (usually a girl) will complete an assignment and then give the file to someone else (usually a boy) who may or may not have the sense to check it and replace her name with his own before turning it in as his work. I can often spot this -- how could this assignment have EXACTLY the same 5 errors that I've never seen anybody do before as I saw on a previous assignment.

But the cheating has gotten out of hand. I now understand that groups of students will make a day of it in the learning lab at school, picking different assignments to do and sharing the results. It has become a tidal wave in the last year.

I would like some way to determine that a file turned in with Xs name in the header or footer actually was their initial copy from the network drive. Do MS office products -- particularly Word, Excel and Power Point provide some functionality where I could monitor this? These products all have file headers (as I learned to call them) -- in fact I usually, the first week of class, rename one or several of these files with the .txt file extension and show them all the "stuff" (most illegible but some in ASCII) that causes a file with one sentence in it to be so large compared to a Notepad file with only 1 sentence in it.

If there was something easy I could do to about 30 files and then send them off myself to each of my ~130 students each semester I would do that. But I would obviously prefer a way for them to simply copy the read only versions from the networked drive as in the past, and then mark the file in some field with THEIR name in a read only field that I could then read later.

I am sorry for the length of this post -- I'm sure this is considered way too long, but I'm not a pc guy and not a chat room participant, and wanted to be explicit about my circumstances.

Thank you.