packman

AlecStaar, these extra Backgrounds that I want to add aren't Web pictures, as it happens. I just want to put the extra ones together with WinXP's default Backgrounds, so that you can use the dropdown list in Display Properties to select them. I doubt that the default Backgrounds that are built into WinXP are in a Web folder.

I use an external 56K modem on my Win2K machine. It's a modem of German manufacture and performs quite well. Unfortunately, a reliable driver for it was never produced and I constantly find that, when I need to reinstall the modem (such as when reinstalling Windows and my apps), TWO instances of the modem get installed, rather than one. I've tried all sorts of methods and tricks to avoid this but to no avail. I'm wondering if the problem is due to a semi-permanent setting in the Registry and, if so, how I might correct it. The modem's called "Microlink Office" and the driver is a beta driver for Win2K [censored] back to 2000. A more up-to-date driver isn't available. There's one available in Windows 2K itself but that one's a very basic driver and makes no difference, in any event, if I try to install that instead. I find that, whichever way I install the beta driver, in Device Manager I end up with "Microlink Office #2", rather than just "Microlink Office". I've experimented ad nauseum, uninstalling and reinstalling the driver but I still end up with #2. I find that, rather than Windows picking up the extracted modem driver file mdmelsa3.inf and installing just that (I use "Update Driver" and point it to the extracted location), it goes to C:\winnt\inf instead and picks up a Windows driver called oem5.inf. It then adds this on top of the required driver. Unfortunately, even though I've tried temporarily removing the oem driver from Windows, Device Manager still ends up as "Modem #2". I've looked for the modem settings in the REgistry and found the location as: HKEY LOCAL MACHINE/System/Current Control Set/Services/Modem/Enum There, I find: (Default) -------REG_SZ --------(value not set) 0----------------REG_SZ---------SERENUM\ELS8548\4&107bc923&0&0000 Count----------REG_DWORD----0x00000001 (1) Next Instance---REG_DWORD----0x00000001 (1) That second line looks sensible, as ELS8548 is the required driver command set (I think), but I've no idea what those other Registry entries mean. There's also a Parameters folder in the Registry and there it says: Default----------REG_SZ---------(value not set) With two drivers installed for the modem, it still appears to function okay, but clearly this is undesirable. Can anybody suggest what's going wrong and how I can fix it? Whenever I uninstall the driver, to try again, I make sure I delete all other entries for that modem (including the ISP account). It's those Registry eniries I'm not sure about.

AlecStaar, Sorry I've not responded for some time. Been needing a clear weekend when I can experiment. I tried editing the mdmelsa3.inf file, as you suggested, putting a semicolon at the start of the line. I tried it separately in both the Strings section and the Models section but it made no difference at all. Device Manager still listed it as "Microlink Office #2". I suspect that that Registry listing has got an extra entry and that it gets left there irrespective of whether you uninstall the modem. Looking at the earlier description of the Registry entry that I gave in this thread, have you any idea as to how I can delete a certain line, like the line that begins "Next Instance..."? Is it just a matter of highlighting the line, rt-clicking it and choosing Delete? How could I replace the line, should that mod not work? Can I just type the line in, for instance, or is there a specific Add command to use?

For the life of me, I can't seem to hide one of my partitions (haven't tried any of the others). I'm using Win2K Pro but with FAT32 partitions. Okay, I go into DriveImage DOS and I can highlight and set the partition to Hide. The Drive Image DOS window labels the partition as hidden. I then exit and reboot but when I look in Windows Explorer, the partition's still there! An e-mail contact of mine regularly hides/unhides partitions on a variety of machines (Win98/ME/XP), where the partitions are FAT32s. He uses Drive Image 4.0 and he says he has no problem at all, regardless of whether they're Primaries or Logicals. Are there any administrative restrictions for this kind of thing, in Win2K? Or restrictions on partition size? The logical partition I'm trying to hide is a 7.6GB one. Any suggestions about what might be wrong would be most welcomed.

AlecStaar, here are the contents of the mdmelsa3.inf file. There's obviously lots of redundant lines here, as far as useful analysis goes. Let me know if you spot anything that might account for this 'driver' not getting installed properly. Yes, it's an INF file and you can muse over semantics but, as far as Windows is concerned, it's treated as a driver and, when successfully installed, shows as a driver from Elsa and is v1.0.0.7. Incidentally, in the same temporary folder into which the modem exec file is extracted, a file called Elsawave.inf exists. That also gets installed. Judging by its name, it's a sound driver of some sort for the modem. ; Windows Modem Setup File ; Copyright © 1993-2000 ELSA AG ; Manufacturer: ELSA AG (sl/hd) [Version] Signature="$CHICAGO$" Class=Modem ClassGUID={4D36E96D-E325-11CE-BFC1-08002BE10318} Provider=%Mfg% DriverVer = 03/07/2000,1.0.0.7 [ControlFlags] ExcludeFromSelect=SERENUM\ELS8548 ;Modem26 [Modem26.NoResDup] UNIMODEMDC9757C8 [Manufacturer] %Mfg% = Models [Models] %Modem26PNP% = Modem26, SERENUM\ELS8548 ; ML Office (PNP) %Modem26% = Modem26,UNIMODEMDC9757C8 ; ML Office ; Installation sections [sourceDisksNames] 1 = "ELSA MicroLink CD",,, [sourceDisksFiles] elsawave.inf = 1,, [DestinationDirs] DefaultDestDir = 11 copy_wave = 17 [copy_wave] elsawave.inf [Modem26] ; ML Office delfiles = copy_wave copyfiles = copy_wave AddReg=All, MfgAddReg, Modem26.AddReg, ELSA_Speaker_ALL, ELSA_VOICE_SERWAVE, CID, External, AdaptiveAnswer [Modem26.NT] ; ML Office AddReg=All, MfgAddReg, Modem26.AddReg, ELSA_Speaker_ALL, ELSA_VOICE_SERWAVE, CID, External, AdaptiveAnswer ; AddReg sections [Modem26.AddReg] ; ML Office HKR,, Properties, 1, 80,01,00,00, 64,00,00,00, ff,00,00,00, 07,00,00,00, 0f,00,00,00, 77,03,00,00, 00,c2,01,00, c0,da,00,00 HKR,, VoiceProfile, 1, 27,12,09,02 ; User visible strings [strings] Mfg = "ELSA" ; Model strings Modem26PNP="MicroLink Office " Modem26="MicroLink Office" [All] HKR,,FriendlyDriver,,unimodem.vxd HKR,,DevLoader,,*vcomm HKR,,PortSubClass,1,02 HKR,,ConfigDialog,,modemui.dll HKR,,EnumPropPages,,"modemui.dll,EnumPropPages" HKR, Init, 1,, "AT<cr>" [EXTERNAL] HKR,, DeviceType, 1, 01 [ELSA_VOICE_SERWAVE] HKR,, Enumerator,,serwave.vxd HKR, WaveDriver, WaveDevices, 1, 02, 00 HKR, WaveDriver, WaveHardwareID,, "HALFDUPLEX" HKR, WaveDriver, XformID, 1, 07, 00 HKR, WaveDriver, XformModule,, "umdmxfrm.dll" HKR, WaveDriver, BaudRate, 1, 00, c2, 01, 00 HKR,,VoiceBaudRate ,1, 00,c2,01,00 HKR, LineSetPlayFormat, 1,, "at+vsm=130,7200,0,0<cr>" HKR, LineSetRecordFormat, 1,, "at+vsm=130,7200,0,0<cr>" HKR, VoiceToDataAnswer, 1,, "at+fclass=0<cr>" HKR, VoiceToDataAnswer, 2,, "ata<cr>" HKR, StartPlay, 1,, "at+vtx<cr>" HKR, StopPlay, 1,, "None" HKR, StopPlay, 2,, "NoResponse" HKR, StartRecord, 1,, "at+vrx<cr>" HKR, StopRecord, 1,, "None" HKR, StopRecord, 2,, "NoResponse" HKR,, TerminateRecord,, "<h10><h1B>" HKR,, TerminatePlay,, "<h10><h03>" HKR,, AbortPlay,, "<h10><h03>" HKR, VoiceAnswer, 1,, "at+fclass=8<cr>" HKR, VoiceAnswer, 2,, "at+vtd=50<cr>" HKR, VoiceAnswer, 3,, "at+vsm=130,7200,0,0<cr>" HKR, VoiceAnswer, 4,, "at+vls=1<cr>" HKR, VoiceDialNumberSetup, 1,, "at+fclass=8<cr>" HKR, VoiceDialNumberSetup, 2,, "at+vls=0<cr>" HKR, VoiceDialNumberSetup, 3,, "at+vrn=0<cr>" HKR, VoiceDialNumberSetup, 4,, "at+vtd=10<cr>" HKR, VoiceDialNumberSetup, 5,, "at+vsm=130,7200,0,0<cr>" HKR, GenerateDigit, 1,, "at+vts=<Digit><cr>" HKR,, VariableTerminator,, <cr><lf> [ELSA_Speaker_ALL] HKR, HandsetSetRecordFormat, 1,, "at+vsm=130,7200,0,0<cr>" HKR, HandsetSetPlayFormat, 1,, "at+vsm=130,7200,0,0<cr>" HKR, OpenHandset, 1,, "at+fclass=8<cr>" HKR, OpenHandset, 2,, "at+vls=2<cr>" HKR, CloseHandset, 1,, "at+vls=0<cr>" HKR, CloseHandset, 2,, "at+fclass=0<cr>" HKR,, HandsetCloseDelay, 1, 1e,00,00,00 HKR,, ForwardDelay, 1,88,13 HKR,, VoiceProductIDHandsetWaveIn, 1, 82,00 HKR,, VoiceProductIDHandsetWaveOut,1, 83,00 HKR,, VoiceMixerMid, 1,02,00 HKR,, VoiceMixerPid, 1,99,01 HKR,, VoiceMixerLineID, 1,00,00,05,00 HKR,, SpeakerPhoneSpecs, 1, A0,00,00,00, 0f,00,00,00, 96,00,00,00, 00,00,00,00 HKR, SpeakerPhoneEnable, 1,, "at+vsp=1<cr>" HKR, SpeakerPhoneEnable, 2,, "at+vgs=130;+vgm=120<cr>" HKR, SpeakerPhoneDisable, 1,, "at+vsp=0<cr>" HKR, SpeakerPhoneDisable, 2,, "at<cr>" HKR, SpeakerPhoneMute, 1,, "at+vsp=1<cr>" HKR, SpeakerPhoneMute, 2,, "at+vls=30<cr>" HKR, SpeakerPhoneUnMute, 1,, "at+vsp=1<cr>" HKR, SpeakerPhoneUnMute, 2,, "at+vls=31<cr>" HKR, SpeakerPhoneSetVolumeGain, 1,, "at+vsp=1<cr>" HKR, SpeakerPhoneSetVolumeGain, 2,, "at+vgs=<Vol>;+vgm=<Gain><cr>" [CID] HKR, EnableCallerID, 1,, "at+vcid=1<cr>" HKR,, CallerIDPrivate,, P HKR,, CallerIDOutSide,, O HKR,, VariableTerminator,,<cr><lf> HKR, Responses, "<cr><lf>VCON<cr><lf>", 1, 00, 00, 00,00,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>DATE = ", 1, 93, 00, 00,00,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>TIME = ", 1, 94, 00, 00,00,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>NMBR = ", 1, 95, 00, 00,00,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>NAME = ", 1, 96, 00, 00,00,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>MESG = ", 1, 97, 00, 00,00,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>ERRM = ", 1, 97, 00, 00,00,00,00, 00,00,00,00 [AdaptiveAnswer] HKR,Fax\Class1\AdaptiveAnswer\AnswerCommand,1,,"AT&FE0\V0S0=0&C1&D2+MR=0;+DR=1;+ER=1;+ILRR=0" HKR,Fax\Class1\AdaptiveAnswer\AnswerCommand,2,,"ATS7=60M1+ES=3,0,2;+DS=3;+IFC=2,2;" HKR,Fax\Class1\AdaptiveAnswer\AnswerCommand,3,,"AT+FAE=1" HKR,Fax\Class1\AdaptiveAnswer\AnswerCommand,4,,"ATA" HKR,Fax\Class1\AdaptiveAnswer,ModemResponseFaxDetect,,"FAX" HKR,Fax\Class1\AdaptiveAnswer,ModemResponseFaxConnect,,"CONNECT" HKR,Fax\Class1\AdaptiveAnswer,ModemResponseDataDetect,,"DATA" HKR,Fax\Class1\AdaptiveAnswer,ModemResponseDataConnect,,"CONNECT" HKR,Fax\Class1\AdaptiveAnswer,HostCommandDataDetect,, "ATO" HKR,Fax\Class1\AdaptiveAnswer,SerialSpeedDataDetect,, "57600" [MfgAddReg] HKR,, InactivityScale,1,0a,00,00,00 HKR, Init, 1,, "AT<cr>" HKR, Init, 2,, "AT&FE0&D2&C1S0=0\V0+MR=0;+DR=1;+ER=1;+ILRR=0<cr>" HKR, Monitor, 1,, "ATS0=0<cr>" HKR, Monitor, 2,, "None" HKR, Hangup, 1,, "ATH<cr>" HKR, Answer, 1,, "ATA<cr>" HKR,, Reset,, "ATZ<cr>" HKR, Settings, Prefix,, "AT" HKR, Settings, Terminator,, "<cr>" HKR, Settings, DialPrefix,, "D" HKR, Settings, DialSuffix,, "" HKR, Settings, SpeakerVolume_Low,, "L0" HKR, Settings, SpeakerVolume_Med,, "L2" HKR, Settings, SpeakerVolume_High,, "L3" HKR, Settings, SpeakerMode_Off,, "M0" HKR, Settings, SpeakerMode_Dial,, "M1" HKR, Settings, SpeakerMode_On,, "M2" HKR, Settings, SpeakerMode_Setup,, "M3" HKR, Settings, FlowControl_Off,, "+ifc=0,0;" HKR, Settings, FlowControl_Hard,, "+ifc=2,2;" HKR, Settings, FlowControl_Soft,, "+ifc=1,1;" HKR, Settings, ErrorControl_On,, "+es=3,0,2;" HKR, Settings, ErrorControl_Off,, "+es=1,0,1;" HKR, Settings, ErrorControl_Forced,, "+es=3,2,4;" HKR, Settings, Compression_On,, "+ds=3,0;" HKR, Settings, Compression_Off,, "+ds=0,0;" HKR, Settings, Modulation_CCITT,, "+ms=V90,1;" HKR, Settings, Modulation_Bell,, "+ms=B212A,1;" HKR, Settings, Pulse,, "P" HKR, Settings, Tone,, "T" HKR, Settings, Blind_Off,, "X4" HKR, Settings, Blind_On,, "X3" HKR, Settings, CallSetupFailTimer,, "S7=<#>" HKR, Settings, InactivityTimeout,, "S30=<#>" HKR, Fax, SerialSpeedInit,, "57600" HKR, Fax, SetupCommand,, "AT&FE0&D2&C1\V0+MR=0;+DR=1;+ER=1;+ILRR=0" HKR, Fax, HardwareFlowControl,, "1" HKR, Responses, "<cr>", 1, 01, 00, 00,00,00,00, 00,00,00,00 HKR, Responses, "<lf>", 1, 01, 00, 00,00,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>OK<cr><lf>", 1, 00, 00, 00,00,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>RING<cr><lf>", 1, 08, 00, 00,00,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>NO CARRIER<cr><lf>", 1, 04, 00, 00,00,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>ERROR<cr><lf>", 1, 03, 00, 00,00,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>DELAYED<cr><lf>", 1, 03, 00, 00,00,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>NO DIALTONE<cr><lf>", 1, 05, 00, 00,00,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>BUSY<cr><lf>", 1, 06, 00, 00,00,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>NO ANSWER<cr><lf>", 1, 07, 00, 00,00,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>CONNECT<cr><lf>", 1, 02, 00, 00,00,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>CONNECT 300<cr><lf>", 1, 02, 00, 2c,01,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>CONNECT 1200<cr><lf>", 1, 02, 00, b0,04,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>CONNECT 1200/HX<cr><lf>", 1, 02, 00, b0,04,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>CONNECT 1200/75<cr><lf>", 1, 02, 00, b0,04,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>CONNECT 75/1200<cr><lf>", 1, 02, 00, 4b,00,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>CONNECT 2400<cr><lf>", 1, 02, 00, 60,09,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>CONNECT 4800<cr><lf>", 1, 02, 00, c0,12,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>CONNECT 7200<cr><lf>", 1, 02, 00, 20,1c,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>CONNECT 9600<cr><lf>", 1, 02, 00, 80,25,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>CONNECT 12000<cr><lf>", 1, 02, 00, e0,2e,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>CONNECT 14400<cr><lf>", 1, 02, 00, 40,38,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>CONNECT 16800<cr><lf>", 1, 02, 00, a0,41,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>CONNECT 19200<cr><lf>", 1, 02, 00, 00,4b,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>CONNECT 21600<cr><lf>", 1, 02, 00, 60,54,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>CONNECT 24000<cr><lf>", 1, 02, 00, c0,5d,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>CONNECT 26400<cr><lf>", 1, 02, 00, 20,67,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>CONNECT 28800<cr><lf>", 1, 02, 00, 80,70,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>CONNECT 31200<cr><lf>", 1, 02, 00, E0,79,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>CONNECT 33600<cr><lf>", 1, 02, 00, 40,83,00,00, 00,00,00,00 ; 56k Responses (56k-flex, V.90) HKR, Responses, "<cr><lf>CONNECT 28000<cr><lf>", 1, 02, 00, 60,6D,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>CONNECT 29333<cr><lf>", 1, 02, 00, 95,72,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>CONNECT 30667<cr><lf>", 1, 02, 00, CB,77,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>CONNECT 32000<cr><lf>", 1, 02, 00, 00,7D,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>CONNECT 33333<cr><lf>", 1, 02, 00, 35,82,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>CONNECT 34000<cr><lf>", 1, 02, 00, D0,84,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>CONNECT 34667<cr><lf>", 1, 02, 00, 6B,87,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>CONNECT 36000<cr><lf>", 1, 02, 00, A0,8C,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>CONNECT 37333<cr><lf>", 1, 02, 00, D5,91,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>CONNECT 38000<cr><lf>", 1, 02, 00, 70,94,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>CONNECT 38667<cr><lf>", 1, 02, 00, 0B,97,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>CONNECT 40000<cr><lf>", 1, 02, 00, 40,9C,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>CONNECT 41333<cr><lf>", 1, 02, 00, 75,A1,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>CONNECT 42000<cr><lf>", 1, 02, 00, 10,A4,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>CONNECT 42667<cr><lf>", 1, 02, 00, AB,A6,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>CONNECT 44000<cr><lf>", 1, 02, 00, E0,AB,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>CONNECT 45333<cr><lf>", 1, 02, 00, 15,B1,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>CONNECT 46000<cr><lf>", 1, 02, 00, B0,B3,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>CONNECT 46667<cr><lf>", 1, 02, 00, 4B,B6,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>CONNECT 48000<cr><lf>", 1, 02, 00, 80,BB,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>CONNECT 49333<cr><lf>", 1, 02, 00, B5,C0,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>CONNECT 50000<cr><lf>", 1, 02, 00, 50,C3,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>CONNECT 50667<cr><lf>", 1, 02, 00, EB,C5,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>CONNECT 52000<cr><lf>", 1, 02, 00, 20,CB,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>CONNECT 53333<cr><lf>", 1, 02, 00, 55,D0,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>CONNECT 54000<cr><lf>", 1, 02, 00, F0,D2,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>CONNECT 54667<cr><lf>", 1, 02, 00, 8B,D5,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>CONNECT 56000<cr><lf>", 1, 02, 00, C0,DA,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>+DR: V42B<cr><lf>", 1, 01, 01, 00,00,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>+DR: ALT<cr><lf>", 1, 01, 01, 00,00,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>+DR: NONE<cr><lf>", 1, 01, 00, 00,00,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>+ER: NONE<cr><lf>", 1, 01, 00, 00,00,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>+ER: LAPM<cr><lf>", 1, 01, 02, 00,00,00,00, 00,00,00,00 HKR, Responses, "<cr><lf>+ER: ALT<cr><lf>", 1, 01, 02, 00,00,00,00, 00,00,00,00 HKR, Responses, "0<cr>", 1, 00, 00, 00,00,00,00, 00,00,00,00 ; OK HKR, Responses, "1<cr>", 1, 02, 00, 00,00,00,00, 00,00,00,00 ; CONNECT or CONNECT 300 HKR, Responses, "2<cr>", 1, 08, 00, 00,00,00,00, 00,00,00,00 ; RING HKR, Responses, "3<cr>", 1, 04, 00, 00,00,00,00, 00,00,00,00 ; NO CARRIER HKR, Responses, "4<cr>", 1, 03, 00, 00,00,00,00, 00,00,00,00 ; ERROR HKR, Responses, "5<cr>", 1, 02, 00, b0,04,00,00, 00,00,00,00 ; CONNECT 1200 HKR, Responses, "6<cr>", 1, 05, 00, 00,00,00,00, 00,00,00,00 ; NO DIALTONE or DIAL LOCKED HKR, Responses, "7<cr>", 1, 06, 00, 00,00,00,00, 00,00,00,00 ; BUSY HKR, Responses, "8<cr>", 1, 07, 00, 00,00,00,00, 00,00,00,00 ; NO ANSWER HKR, Responses, "10<cr>", 1, 02, 00, 60,09,00,00, 00,00,00,00 ; CONNECT 2400

AlecStaar, how do I copy and paste the contents of the mdmelsa3.inf file to this topic? Please excuse my ignorance.

Well, AlecStaar, with what you've stated so far, I'm none the wiser. What I'm particularly wondering about are those listings in the Modems\Enum folder of the Registry. Should it be reading "Next Instance", for example? I've used this modem for something like 3 years now and, although it's always been a bit hit-and-miss to get the Win2000 driver (mdmelsa3.inf) installed and showing properly in Device Manager, it HAS shown correctly on many occasions. But of late when I've been trying to install it, I get "#2" EVERY time. That suggests to me that there's a background record of either mdmelsa3.inf or of the Windows default driver permanently left in the configuration somewhere. And that's why I'm wondering about the Registry and whether if I deleted the appropriate line in the Registry it would correct the matter.

I've just finished a major change to my Win2K PC - going from Win2K under the FAT32 file system to Win2K under NTFS. Not a conversion but instead a change from ground zero, involving deletion and reconstruction of the partitions and then reinstallation of Windows and apps. My programs open much the same as before and files are no faster or slower to access than before, either. However, I've noticed that the bootup time is noticeably longer, and shutdown seems to take an eternity. I timed it a moment ago and Windows and open programs took 80 secs to shut down. That's ridiculous. I've not installed anything different to before on the machine. In fact, I've installed one fewer app (Nero). I'm using three partitions, 15GB each. 600MHz CPU, 394MB PC133, UDMA66. BIOS and Device Manager settings for HD transfer rate are okay. I've been told that this can happen and that there's a fix available for it. Anyone know what that fix is?

Bursar, I found Services and then Indexing Service. In the Properties of the latter I found some unknown tabs. There appears to be no way of changing from automatic to manual, though, and the remainder of your instructions bear no relationship to what I found. Are you sure you're referring to Win2K?

Whenever I've done a major system reinstall (one in the last few days, actually) I've invariably needed IE5.5 SP2 again and, like you, have needed to download it. And, again, like you, I've wondered if there's a way to download it to the Desktop, so as to later put it on a CD. However, IE5.5 SP2 download seems to consist of just a 400KB installer followed by IE5.5 itself and it installs immediately, preventing you from getting at it separately. I'll be watching this space to see if someone's found a way of getting it on to the Desktop before installing.

Which indexing? Please explain.

AOL e-mail appears to be incompatible with other more-standard mail clients, but clearly some people do like certain aspects of AOL. I'm no fan of AOL at all. I use a standard dial-up ISP account myself, in conjunction with Outlook Express 5.5. I find that, whenever contacts of mine who use AOL send me messages in HTML, not only is the whole received text block-highlighted (I happen to use a coloured background and the highlighting is white, so this is why it shows) but also my AOL contacts complain of missing numerals and missing special symbols in the messages I send THEM. Communicating with them in any sort of technical way becomes a bit hit-and-miss, therefore. I don't get this from any of my other contacts.

From the MS Knowledge Base article 329251, it would appear that MS Windows 2000 Pro SP3 isn't relevant for this fix. My guess is that most of us are using SP3.

The reason for me wanting to hide certain of my partitions is to prevent inter-partition interaction and thus corruption of partitions. It's possible for DOS to cause this. I've certainly had a number of instances of it. In order to fully hide a partition with something like Drive Image or Partition Magic, it turns out that, with Win2K, you need to both remove the appropriate driveletter in Disk Management AND hide the partition in Drive Image. It's misleading that Drive Image, by itself, gives no positive indication of hiding the partition, outside the application. I've confirmed that this is the case by booting with a floppy (it's a FAT32 set of partitions) and testing to see if DOS can access the hidden partition. I hope this helps others who are users of Drive Image, and especially those who are Win2K users.

Norton Ghost has been quite popular with Win2K users over the last few years. I was given to understand, though, that Drive Image had a slight edge on it. Still, these reviewers never seem to find the bugs that I IMMEDIATELY find. I'm not in the mood for shelling out more money on what might turn out to be yet another incomplete design of software (quite apart from the fact that I'm early-retired due to ill-health and have to live on next to nothing), but I'll look into Norton Ghost a bit more perhaps. I know that a couple of my Win2K contacts use it. My original topic remains basically unanswered, as you'll no doubt realise. It seems that Drive Image 5.0 (and probably other versions around that) simply can't hide logical partitions and, in fact, gives erroneous indications in this respect. It's just as easy, if not more so, to use Win2K's Disk Mngt to hide partitions instead.

Yes, like I say, it was browntrousersville, especially this afternoon, when I realised I couldn't boot into Windows and had corrupted the boot sector. I'm still very suspicious of DI, though. What seems so hard to believe is that Powerquest ever tested out DI 5.0 on either Win2K or WinXP for real. I mean, it's FULL of bugs. It reported things like telling me that my destination path/filename was invalid and inaccessible when, quite clearly, it wasn't. For some unknown reasons, imaging will only work in the Windows version (called QuickImage) and restoring would only work in the Caldera DOS version. Then there's hiding the partitions - that wouldn't work at all, despite DI saying to the contrary. How on earth can a company like Powerquest ever put out a product like that with so many obvious bugs in it? No wonder they won't offer any support on it any more; they're probably too embarassed about it! No, I have to admit that, whilst in this instance I managed to restore my C partition, I'm not at all happy with ANY of the so-called ghosting programs that are on the market. They all claim to be the last word but they sure ain't. You'll probably know that Powerquest has just released Drive Image 2002, which apparently is an all-Windows version.

Hmm. It's been a long day for me today, Alecstaar. A real brown trousers job, in fact, as I put my imaging to the ultimate test! By the way, to answer Adam, that program was only a trial DOS version, to see if it'd work as regards hiding, and it didn't, so I've removed it now and am just using Drive Image. BTW, a year ago I paid full whack for DI and now Powerquest won't give any support. Nice one, Powerquest. Anyway, to cut a long story short, today I experimented at length with the hide function in DI but it still wouldn't hide either of my two logical partitions. In the end, I left that and decided to image C on to one of the logicals (this was the first ever attempt). It would only work in the Windows version of DI and I got some stupid error messages en route. I then retried hiding but still no joy. Someone else I know suggested using Win2K's Disk Mngt for hiding partitions, like you did, AlecStaar, so I investigated that and it worked. It hid the partitions in W. Explorer but didn't alter the drive-letter assignment, which is great. It's simple to unhide them, as well. Leaving them hid, I then started a Restore, just to see if DI would even see the Win2K-hidden partition (as I had doubts about that). Unfortunately, it immediately started the full-blooded restore and I panicked and somehow aborted. When the PC rebooted, it stopped, saying BOOT DISK FAILURE. PLEASE INSERT SYSTEM DISK. **** I'd corrupted the boot sector (NTLDR was missing). I started to use my Win2K backup floppies to try to repair Windows but in the end aborted that and switched to the newly-made DI recovery floppies. All or nothing, I reckoned. But it worked! I was able to restore 99.9% of C. I'm not very impressed with DI, though. It's clearly imperfect. It's also taken a while to get Windows back up to speed again. Internet access was sluggish after that, and I also found I was locked out of these forums or to e-mailing a moderator for help. But now it seems to have sorted itself out.

Yeh, I feel terrible about the disaster as well. I imagine most people who follow the Space Programme and world news will. The crew were indeed very special people and we should honour them totally. Seven brave souls. That's not taking it away from other 'everyday' trajedies, though, and from those who die in more conventional military service. I think the vast majority of people want the Space Programme, as currently planned, to continue. "The dinosaurs became extinct because they didn't have a space programme" - Arthur C. Clarke.

Another contact of mine has sent me files sufficient to make a bootable DOS version of Partition Magic 6.0, to try. Well, I've done the business and tried it, and that doesn't hide the partitions, either! I reckon that you can't hide logical partitions, therefore. You can only hide primary partitions. Either that, or there's something really weird about Win2K with regard to hiding.

AlecStaar, take a look at: http://support.microsoft.com/default.aspx?scid=kb;en-us;231289 You'll see there the approved way of hiding partitions, if you wish to do it in Windows. I discovered that KB article several days ago. I actually went into MMC, to see if I could open the sections User Configuration, Windows Explorer, etc, but they simply weren't in the list to add. And, like I say, this is "in-house" hiding; it's a diversion; it doesn't answer my basic question about Drive Image.

Bear in mind, AlecStaar, that once hidden (by Drive Image), my partitions need to be recoverable both from inside Windows and from the DOS-type environment that Drive Image provides (because there's always the potential for the primary partition to fail and the machine to become unbootable) . There's no guarantee that if I were to hide my partitions using the method you've suggested, Drive Image DOS would still work as it should, allowing me to recover the good partition(s) and restoring a good bootable primary partition. In effect, you're guessing at the way Drive Image works (and you freely admit that you've never used Drive Image!). No, I'll hang on in the hope that somebody versed in the usage of Drive Image replies.

Well, thanks for the idea, AlecStaar but I'd rather confine myself to Drive Image. It's a real bummer that Powerquest won't provide support any more. I'm familiar with partitioning and drive-letter assignment in Win2K's Disk Management but I'm not aware that you can hide a partition by simply not giving it a letter. Given that my partitions already exist and have data in them anyway, my guess is that Win2K would prevent non-assignment of a drive letter. I'm not willing to mess around with that, quite frankly, because if something goes wrong, I'll lose the very data I'm trying to secure. I'm hoping that someone who's a Win2K user and who's used Drive Image for both imaging and hiding will see this query and enlighten me - and us all. Like I say, either I'm missing a special configuration setting in Win2K or Powerquest has singularly failed to say that hiding partitions won't actually work for Win2K (they state quite clearly in their handbook that DI is compatible with Win2K/WinXP but, of course, that can mean anything you like). Or perhaps, with products like Drive Image and Partition Magic, only PRIMARY partitions can be hidden?

And don't ask the obvious question - Powerquest no longer offer support for Drive Image versions up to v2002.

No, this is not a half-baked multiboot setup. I'm not running a multiboot arrangement; I've no need for that. I do run three partitions, though - one the primary bootable and two logicals. One of the logicals is reserved for an image of the primary, the other one is for safekeep of drivers, utilities, etc. The principal reason I'm wanting to hide one (in fact, both) of the logical partitions is to protect it from being written to by Windows (Win2K, in my bootable primary partition), except when it's supposed to. Believe it or not, mere partitioning does NOT prevent the erroneous writing by Windows to other partitions under error conditions, but hiding the partitions should get around that problem. Over the past couple of years, I've had instances of where visits to what-have-turned-out-to-be badly-designed websites have resulted in strange code being executed (no, not a virus) and causing Windows to corrupt both the primary and logical partitions. This is a situation that should concern ALL serious users. Drive Image (as well as Partition Magic) should certainly allow partitions to be hidden. At least, that's what it states in the DI handbook, and it gives the procedure for it in detail. However, I can't get it to work. DI itself indicates that it's hidden the partition but when I subsequently look in Windows Explorer, the partition's still there! I'm wondering if there's something special about Win2K that prevents it, or possibly you can't hide logical partitions, only primaries. However, a distant contact of mine is adamant that you can, and he says he's done exactly what I want to do, using DI, on Win98, WinME and WinXP machines, all using FAT32. I have a personal preference for FAT32 for several reasons - being a single-machine, single-person user, I don't need the file encryption and extra security of NTFS. I concede that NTFS has better recovery from error conditions but I specifically want access to DOS-proper. Also, FAT32 works faster than NTFS, for all but the largest of partition sizes. Still, this is not a discussion of FAT32 v NTFS, it's a discussion about hiding partitions in Win2K. I'm wondering whether perhaps Permissions has something to do with it?

Thc129, You state "Make sure that the user is listed under both computers". WHICH user, and why? Please explain.