allen2

Ok found a solution: Instead of using %1, you need to use %D but it contains "\\" before the computername. I created a small batch (launchrdp.cmd) to do it: set dest=%1 mstsc -v %dest:~2% and the reg entry is: HKEY_CLASSES_ROOT\NetServer\shell\remotedesktop\command @=launchrdp.cmd %D

It seems to be added by photoshop 4 if we trust this.

When using robocopy, it may hide the destination folders. To undo this, you'll have to do : attrib /S /D -h folder for each root folder.

I don't understand your way thinking: - If you install an unsupported system, you'll have to maintain it yourself. - most 32 bit software don't need more than 3Gb of ram (and that's the maximal amount you get with 32bit XP) - you'll have you have to either join the domain at your work but also comply to their security rules - if you are printing with print servers, you won't be able to do it anymore as 32bit print drivers don't work on x64. - if you still need to install an x64 OS, why not installing Windows 7 ? - you'll need x64 antivirus as most of them need a specific version for x64 OS. - and then if you're caught, you'll may be fired as in some companies, playing with some rules is a fault. The right way for doing something similar would be booting from CD or usb.

Some gpo settings when applied once need another gpo to be removed properly and that's likely the case. The default settings for allow logon through RDP on a computer is the groups: "administrators" and "remote desktop users".

1) The W2k3 R2 i connected has all the lastest patches. 2) The XP rdp Client was taken from a XP CD from the support folder and its installer version number is 6.0.2526. 3) There wasn't any update on the W98SE. 4) The RDP client is 128bit and the OS languages are US.

Most likely you didn't add the url to your browser proxy exceptions. To be sure, remove any proxy configuration and retry. If it still doesn't work you should check if your dns answer correctly: do from a command line a nslookup intranet.dlp.cu and check if it answer correctly.

The XP RDPCLI works fine on W98SE (i just tried a rdp connection to a W2K3 R2). Most likely your rdp server isn't listening or there is a firewall (or another thing) blocking. You could try the Win32 port of Rdesktop if you want to try another client.

I would try to replace the video card of course if you have already one at hand. I would also run memtest for at least two passes.

Depency walker can identify which files are needed for the specified .exe or .dll. Filemon and regmon can track every access made (respectively to files and registry entries). Running dependency walker on your working win2k against the modem software will show which files are needed. Then you'll need to find your FDVfiles what part was needed. Using filemon and regmon is another way: run them and log on bothe the working win2k and non working one and then compare both logs and you should see what is missing.

You should try dependency walker or filemon/regmon to see what files/registry are needed on the working win2000.

The only tool i use to clean the registry is autoruns from sysinternals (now microsoft) which is free. I also clean when needed manually only the needed keys. Some cleaner tools, might in fact do bad thing if they remove a key used. The last cleaner i tried was for windows 95 and i had to repair after. Before using a cleaner, i would run regshot and then after cleanning do a comparison to see the removed keys. Unless you have a size of registry problem, you shouldn't need to clean it.

Depending on data type and volume, you'll need a different solution.

Here is the sticky thread: http://www.msfn.org/board/topic/130003-creating-memory-dumps/ You'll need to do the "Memory dump of the entire system:" part. The step 1 isn't needed for you as XP will crash by itself if docked. And when you 'll be at step 3 also uncheck automatic restart. This way you'll see when XP crash and you'll be able to write down the Stop error code as sometimes it is the only needed thing.

What are you calling boot up loop ? Do you see the the Windows XP screen ? If it seem to boot XP normaly and then reboot, it is probably crashing. If it is the case, you should disable the automatic reboot after a crash and configure XP to make a full dump when crashing.

Ok i made an archive of the needed files and registry: http://www.megaupload.com/?d=TLEIA8E9 . You should make a backup of your windows 98 Se before testing (a partiton image should be the best ) as we never now what could happen when replacing files and reg entries. As for the win.ini, only one line is removed: in [Compatibility] section, the line SETUP=0x00000000.

I had a similar case and it was solved modifying the dns options in the dhcp config: http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/Windows_Server_2008/Q_26422992.html and screenshot

Ok using installrite in a 98se virtual machine, i was able to clone the drivers install: Here is the list of added files, modified files, registry key added, registry keys modified. I could repackage the needed files if you need them. Also as i made this on a clean 98Se some files already newer on your computer might exist and you'll probably only need the newer ones.

Here is what i'll try (using the virtual machine trick) : - create an offline disk image of the 200 MMX computer. - restore it in a virtual machine on a faster computer. - install the hp software. - create an offline image of the virtual machine. - restore it to the physical machine. I'll look the drivers and see if they can be cloned for Windows 98SE.

Could you post the printer/scanner model (so i can try to clone the driver/software install) ? Do you have a faster computer with vmware or any other virtualisation tool (you could easily install the driver in the virtual machine and then get it back in the physical one) ? Sorry if you already tried this method.

As for the universal driver, perhaps it would allow to install xp in ahci mode (even on lastest intel chipset mobo that i doubt as even old intel drivers doesn't work for those and the universal sata driver was lastly updated in 2008) but if it's for using a cheap trick. I would use compatible mode (in bios) and then after install use driverInjection. Also, i won't ever install drivers made from a third party and there are two reasons: - any low level driver could contain a root kit and even if i'm not familiar with driver dev, seeing the source code might help (and in this case, the site provide the source code). - only the hardware manufacturer kows perfectly how its hardware will react to a driver and i often saw that using a too old driver or an inappropriate one would cause problems (BSOD or memory leaks). Sometimes the easiest way is to follow the manual and do a F6 at install startup, provide the drivers and let windows do its install and if you want a cheap trick, you can always image a generic XP install (a wmare one for example) and then add the storage driver after (most imaging commercial tools like Acronis or BESR offer this opportunity).

There aren't generic sata drivers and that's a good thing. If there were, that would mean every sata controler would have the same specs and real world speeds. That would also mean no improvement to the sata drivers...

It should work if your child domain doesn't go crazy. When you set up a test domain, it can happen a lot that you won't be able to foresee and that's the reason for 2 physically independent networks. If anything goes wrong on the test network, it won't affect the production.

You should only need to setup the 2 computers so the users don't have admin password and aren't admin (to prevent them from installing anything). Then for "the going to bad site part", you'll have to either setup a proxy or modify each computer browser configuration. You could use a .pac file and/or a host file for example.

If you want to play safe, you should physically separate both networks and set up a router between so you can choose what to route. As you described the wanted setup, you DON'T want both dhcp to answer whenever a computer will ask for an ip. And by design dhcp will answer to a computer if it is on same physical lan or on the same logical vlan. So with the switch thingy, you'll still need to setup a router to allow some of the traffic to go to your production network. But this is the bad way, any error on your test network could make your production network to fall (like a loop).