jaclaz

It's the same old story, Clint, From The Good, The Bad, and The Ugly: You have the loaded gun.... jaclaz

You can scan the registry. All devices connected once should have an entry. They should be in: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB but check also in HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\USB HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Enum\USB Mass storage devices will have additional entries in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USBSTOR jaclaz

More "rareware": http://htmole.altervista.org/rareware.htm jaclaz

I think the setting is the same used to change BSOD (Blue Screen Of Death) colour: http://www.petri.co.il/change_bsod_color.htm jaclaz

Let's start from the beginning. Modern telephones are made along an International Standard (on the phone part). The power supply may be different, i.e. 115 V AC 60Hz in the states 230/240 V AC 50 hz practically everywhere else. However it is many years that MOST low-power electronic devices are "Universal voltage". The "radio" part of a cordless device will work, of course, everywhere, if properly powered (atmosphere is roughly the same, with the possible exception of Manhattan and downtown Athens ) What I don't understand is what the problem is. Usually on a cordless device there are two pieces, a "base" and a "handset". The base is powered by mains, the handset by batteries. Even without connecting the base to the phone line, by pressing the "call" button on the base, the handset should ring. If it does not it means that one of the units is either not properly powered or defective. This sometimes is also shown as a blinking light, meaning that the base or handset cannot connect with the other piece. If the above test succeeds, there might be a problem in the connection to the phone line.(NO PHONE SIGNAL) In the US, and generally in most base units the connection is made with "plugs" standard RJ-11: http://kropla.com/rj11.htm in Britain, the standard wall plug is the British Telecom one: http://kropla.com/uk.htm http://web.ukonline.co.uk/freshwater/howpst.htm See the diagrams to make sure the connection is properly made, the two center slots on both plugs must be connected. Usually a telephone set, to be LEGALLY used in a country, should be approved by the telecom authority of the country, since most manufacturer are international, all recent phones are approved everywhere, though. Depending on the number of telephones that you have connected in your house, you might have an impedance or REN (Ringer Equivalent Number); on some phones there is a switch, either internal or external to set the REN. http://web.ukonline.co.uk/freshwater/ren.htm Posting here the EXACT make and model of the phone you have might help, I am afraid that your description as didn't help much. jaclaz

Happy it worked. jaclaz

I guess that this is supposed to be defined as "teasing" Cannot say if the above matches the requirements for "cruel"" teasing, but I suspect so. No way to have a howto, a list of files, anything? jaclaz

I would really be interested in it. I once made a "non-decent" Win2k in 80 Mb: http://www.msfn.org/board/index.php?showtopic=41208 jaclaz

Nice one. Actually I use command line gsar: http://gnuwin32.sourceforge.net/packages/gsar.htm http://home.online.no/~tjaberg/ jaclaz

Oh, come off it, if you don't have a browser capable of showing that page ?? Get OPERA! Or if you don't want to install anything, get Off by one, it does not have javascript as well, but at least it shows you the links to screenshots and download: http://www.patcher.homestead.com/files/screen.html http://members.fortunecity.com/strictly_nitro/Downloads.html You will need to set off by one as to "show noscript"/"show noframes" If it's too difficult for you, here are direct download links: http://members.fortunecity.com/strictly_ni...ads/patcher.zip http://members.fortunecity.com/strictly_ni...uickpatcher.zip http://members.fortunecity.com/strictly_ni...ds/turn2pax.zip Runtimes if you need them: http://members.fortunecity.com/strictly_ni...ads/system1.zip jaclaz

Here: http://www.patcher.homestead.com/ jaclaz

The "standard" reference for CF card XP installs and EWF is Sfiorito. Search for post by him on the board and check his page: http://osf1.gmu.edu/~sfiorito/eXPinstall.htm and the MP3car forum: http://www.mp3car.com/vbulletin/forumdisplay.php?f=70 jaclaz

This method works, tested and verified: http://www.911cd.net/forums//index.php?showtopic=16713 You will need a bootable USB stick, but you can easily adapt it to a multiboot solution (you format and install DOS 7.1 from Windows 98 to the hard disk, boot from it, then run WINNT.EXE, hinted here: If you are satisfied with FAT32 formatting. Or if you are satisfied with at least one partition formatted as FAT32, in a multipartitioned drive. FAT32 partitions can be later converted to NTFS by using command line utility convert, though actually I do prefer having First Active Primary Partition formatted as FAT16 or FAT32. A different approach is hinted here: http://www.msfn.org/board/index.php?showtopic=61384 and here: http://www.911cd.net/forums//index.php?showtopic=17425 ( a rather more complex and NOT tested/verified method) Or you can simply run, on the "other" system, and with the PROPER <driveletter> and <path>: <path>\winnt32.exe /s:<path> /syspart:<partition_drive_letter> /tempdrive:<partition_drive_letter> /makelocalsource /noreboot this will setup your drive in a way that, as soon as it is booted it will start setup, using install files copied to the same HD and not needing any external CD. You will have to add to the hard disk, before moving it to the laptop, ALL the needed drivers and EVERY other file that might be needed before another means of accessing "outside" sources (say network) is available. some reference: http://www.quepublishing.com/articles/article.asp?p=102260 http://winsupersite.com/showcase/win2k_cmdline_setup.asp (syntax of WINNT32 parameters is still the same) jaclaz

Actually, to be on the safe side, best thing is to use Unmount by Christoph H. Hochstaetter, yes it was written in 1995 for NT4, but it still works on 2K and XP . Here: http://www.uwe-sieber.de/usbstick_e.html http://www.uwe-sieber.de/files/unmnt10.zip From the docs: Or, better still, one of the two proggies written by Uwe Sieber, same address: http://www.uwe-sieber.de/usbstick_e.html http://www.uwe-sieber.de/files/removedrive.zip http://www.uwe-sieber.de/files/ejectmedia.zip Also, you can use devcon: http://support.microsoft.com/?kbid=311272 devcon remove @usb\* Will remove ALL USB devices Finally, check this: http://portableapps.com/node/639 jaclaz

No, letters are "software" assigned, there is no difference in the bytes in MBR and/or bootrecord. The "theoretically" when coupled to "4000 Mb" leaves some doubts in my mind. Each partitioning/formatting utility, expecially windows GUI ones, have their own way of counting bytes.... Just one sector (512 bytes) shift will make the "old" Bootsect.dat not working, IF this is the problem. Unless you post some more details on the steps you took, I am not even sure that THIS is the problem. jaclaz

No, you are right, but maybe you missed something. The NTLDR (the real one) will parse boot.ini and, based on user selection, will invoke ntdetect.com to boot if a NT/2K/XP/2003 has been chosen or simply pass control to a bootsector. The "PE" NTLDR (actually SETUPLDR.BIN renamed to NTLDR) will read WINNT.SIF and boot whatever is specified there. See also my posts here: http://www.911cd.net/forums//index.php?showtopic=17538 If I get right your original setup, you had in boot.ini an entry like: multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP" /fastdetect that booted XP, and one like: C:\bootsect.dat="Windows PE" Since the boosect.dat is actually a bootsector, it will try to load another NTLDR. So you have now a situation where the data in the bootsector, which contains partition information, is no more correct (since you changed partition size), and thus it cannot find the file. The use of GRLDR is very convenient, but if you want, it is possible to fix the problem in some other way. I need to understand how your original setup was made, and how your hard disk is currently formatted if it is FAT16 or 32, recreating a bootsector is very convenient using bootpart, then you can rename setupldr.bin to (for example) PELDR and hexedit the bootsector accordingly.... Or, you can use, even from batch a combination of dsfo and gsar to copy your current bootsector to a file, then sustituting in it "NTLDR" wit "PELDR".... jaclaz

And of course fdisk /mbr actually replaces the MBR code with the "standard" dos/windows one, not really smart if you use GRUB, Partita or any other Boot Manager that is installed on the MBR. And yes, MBR is ALWAYS on sector 1 of the hard disk, sometimes called Track0, CHS 0/0/1, NOT in any flash/rom. Fdisk /mbr defaults to 1st hard disk. Just for the record, the command fdisk /cmbr x exists also: http://www.mdgx.com/secrets.htm#FDISK-C that allows the same action on 2nd, 3rd hard disks, etc. jaclaz

Using MBRWIZARD or MBRFIX, for example, or any of a number of DOS based programs or Dubaron's diskimage: http://mbrwizard.tripod.com/ http://www.sysint.no/Nedlasting/MbrFix.htm http://home.graffiti.net/jaclaz:graffiti.net/index.html http://www.partition-saving.com/ http://dubaron.com/diskimage/ jaclaz

@deltawing from what you say it DOES seem like a bad floppy. The bootblock is what makes the BEEPS and the Insert System Disk, so it should be working. Try making another floppy, doublecheck it, try booting with it on another machine (REMming out the awdflash commands !!!) jaclaz

Please find the info you need about BOOT.INI and the NTLDR in my posts here: http://www.msfn.org/board/index.php?showtopic=25365 http://www.msfn.org/board/index.php?showtopic=33030 About the logical partition prroblem, also have a look here: http://www.911cd.net/forums//index.php?showtopic=17144 jaclaz

Dear Word 2003 user, go here: http://www.openoffice.org/ jaclaz

Well, the problem is of course the "HEURISTIC" engine. http://whatis.techtarget.com/definition/0,...i212246,00.html Life is tough. You cannot expect to increase the probability of stopping a new virus, for which there is NO signature/experience, WITHOUT risking to increase the probability of false alarms. Decisions, always decisions..... jaclaz

You'll probably need to make a Repair install: http://www.michaelstevenstech.com/XPrepairinstall.htm jaclaz

I remember using once Excelfix and it did a very good job, but cannot say if it would work on your infected files. I would try taking the first 4660 bytes from an old copy of the same file (I hope you have a copy or a backup of at least ONE file!) and paste it in the infected file, then try using recovery programs. It might work, or it might not. Getting most of the text, maybe NOT the formatting, from an average WORD file should not be difficult using the same method. jaclaz

What about this FREE one: http://www.lansweeper.com/ls/default.aspx jaclaz