pmshah

Member
  • Content count

    292
  • Joined

  • Last visited

Community Reputation

0 Neutral

About pmshah

  • Birthday 07/31/1946

Profile Information

  • Country
  1. I have no idea what happened but the command that worked on x86 and not on x64 suddenly started working on x64 also. I just realised that this is M$ Windows after all
  2. I guess I will have to live with it, hopefully only till I reinstall the OS.
  3. I have Realtek Gigalan chip on board and a Belkin wifi pci addon card. For quick identification I named them Realtek and Belkin ( I monitor the transfer rates by 2 instances of NetWorx portable.) As I mentioned earlier the command did not work with the specified name so am planning to remove the name and revert to the default name assigned by windows, namely "Local Area Connection" and see. Well after all it is M$ Windows, so all is not easy and hunky dory!.
  4. @MagicAndre I have tried all kinds of variation after thoroughly reading the netsh.chm and Netsh_TechnicalReference.chm. including the one suggested by you. I have only mentioned the actual command line that WORKED on the 32 bit version. And it does so in less than a couple of seconds. @IcemanND I think I will try your variation by removing the name I have assigned to the NIC and letting it default to "Local Area Connection". Thanks to both of you.
  5. As quoted above - I have no experience - you might find x64 to be faster if you have 3.2 + GB of ram. I have 6 gb - but am not a heavy graphics user. On the flip side, migrating from XP-SP3 to win7 was painful enough. It took me over a month to get all my background configuration scripting files working. It is proving close to impossible to adapt these Win7 x86 scripts to work under Win7 x64. If performance is not an issue I would say stick with 32 bit version.
  6. I have 2 machines. One running Win7 x86 and the other running Win7 x64. I can't figure this out but the command that works with x86 to disable a wired NIC simply does not work on the x64 version. I of course changed the name of the nic appropriately. The command line I used on the x86 was ..... netsh interface set interface "nvidia" DISABLED this works perfectly. the same on x64 was ... netsh interface set interface "realtek" DISABLED This simply does not work and the cursor simply blinks !!! I wonder why M$ engineers thought it prudent to have them work differently. Only reason I use x64 version is its capacity to access more than 3.2 GB of ram. I don;t see any other advantage to it. Any and all help / suggestions welcome.
  7. When I try to do a full download it gets stuck at file number 207 out of 286. Has abuone else encountered this problem or found a workaround for it? All suggestions welcome.
  8. No need to tinker with registry. Simply right click on the concerned file, select the "open with...." option, "choose program..." , browse down to & highlight the application you want to open the file with and check mark the "always use the selected...". That should fix the problem.
  9. For Wake on lan to work there are a few basic requirements. If your ethernet card is an addon one there should be a short jumper link from the card to the mother board. You should also have the wol feature turned on in your bios. Lastly your power supply must be able to supply 700 ma of power in S1 standby mode. AlthoughI have not used this feature in quite a while never had a problem with this feature. One more thing I would look out for is the fact that on some motherboards I have come across an experience that due to low battery condition while the clock is maintained other bios settings get reset to factory defaults. Hope this helps.
  10. It may boot but what is the status on Activation?
  11. I too found the fonts displayed disconcerting. You will have to go in the display setting & change the icon scaling as well adjust the font setting to get sharp display. Original setting by Vista are very fuzzy. Of course I only have a 17" lcd & use 1024x767 resolution only although 1280x1024 is supposed to be the native resolution for the device.
  12. Unfortunately swap function available for floppy drives is not available for hdd. Try "BootIT NG" from Terabyteunlimited. as your boot manager. It will allow you to swap primary & secondary drives in memory. Just what you are trying to do. It works flawlessly.
  13. I have been using BootITNg (Bing) for nearly 3 years now. I presently have 2 version of XP, 2 versions of 2k3 & TWO versions of Vista - Ultimate & Business - installed on my system apart from several versions of Linux. There is no interference from any OS with any other OS. The way Bing does it is it maintains all the data in its own partition called EMBR. When ever you opt any specific OS to boot it presents a special Partition table to the OS - which always runs in memory. The way Vista would see areas used by other OS is as - "Unused Space" You will never have to use Vista bootmanager. You also have th option of making other partitions visible/available to other OSes - up to 3 primaries & 1 extended - at your option. There is one caveat though. You must never never use any other partitioning software when you have Bing installed. Bing can create all kinds of partitions but cannot format them other than the standard fat & fat32 partitions. It will only mark thenmas such - ntfs, linux, linux swap or what have you. You have to let the installation software do that bit. Most installations (except Linux) will overwrite your MBR. It is a simple matter to boot from Bing disk to reactivate itself. All your choices are once again available to you. I can assure you Neither Vista nor any other OS will ever be aware of existence of any other OS. Some Linux partitions are finicky when partitions for their installation are not formatted. It is a simple matter to boot live version of either DSL or Puppy Linux to format these partitions & install Linux. Only time I Had problem with it was when Ububtu 6.06 trashed my entire Partition table & I almost lost my entire hard disk worth of data. Bing was able to undelete & restore every one of those partitions without loss of a single byte of data. So what I do is ALWAYS create a fresh bootable CD/DVD from Any installation cd whatsoever by including BCDW 2.01 as cd/dvd boot manager & also including Bing + other diagnostic + partitioning/formatting software on it. Try it, you will love it.
  14. "The worst thing is, its the paying customers who get messed about the most with stuff like this." You are learning fast !!!! Your best bet is to first do an install with all the required software & activate it. Then boot with something like Acronis true image or Paragon Partition manager & create an image file to a dvd. Mark it properly with the id of the specific machine & store it safely. Repeat for each machine. This way you got all your machines covered. If you are gigalan you can create these images across the lan & save them on the server for quick fast access without the need to handle dvd media.
  15. Visit TerabyteUnlimited.com & download their boot manager software. It is a 1 month full working trial version. It can install in its own partition & will allow any number of partitions. So Installing a new OS or deleting a partition will not affect any other OS or your boot choice. It has turned out to be the best investment I ever made. BTW I have 6 + versions of Windows & 6 + versions of Linux installed & running on my pc.