Tripredacus

Still nothing on the wireless. Here is what I did: - uninstalled the Air Plus from Add/Remove Programs - installed the 2.00 drivers (no change) - backed up the ntkern.vxd from vmm32 - put the new ntkern.vxd into C:\Windows\System\Vmm32 reboot = no change - put it in c:\windows\options\cabs (found online it needed to be in there too) = no change So still got nothing going on with that. I was hopeful when installing the 2.00 drivers because it actually installed different files than the other versions, notably the HLPs from PCHEALTH folder, but to no avail. I did try to boot into Safe Mode and delete the drivers and see if there were any ghosts in there, but the video flips. For some reason the default video output (used during POST and in the BIOS and Boot Menu) as well as in the Windows F8 menu and Safe Mode is grayscale and the video constantly flips. This is because my video out is S-Video to a television. I keep forgetting to get that extra CRT to hook up to it.

Ah you didn't mention using WinME (except in the thread title) and only talked about Windows 98 in your first two posts. I should have asked for clarification on the OS you were actually using.

Please explain how that modem, when used in it's default configuration, will not be acting or performing as a NAT-router, and as such will be blocking all unsolicited in-bound packets, and therefore will be operating as a 100% effective in-bound firewall. It depends on how the ISP configured it. Different ISPs or regions may configure the settings differently based on what kind of system it is going to be used on. Since mine is not in the default modes, I cannot say what all the settings were. I did know that the firewall was not turned on. These things are just 1 port routers, or mine only has 1 private side port. They did have DHCP enabled on it, however.

If you are fine with removing all the data on the drive, you need to boot off the XP Pro CD to install. Do not put the CD in while booted into Windows, it will not always let you install the OS from there.

I found some other things maybe... First I found someone had this problem on Win95 and 98 on an Intel board: http://www.computing.net/answers/windows-95/soundmax-drivers-w-intel-d845grg/147107.html Which led me to this page on SourceForge: http://ac3filter.sourceforge.net/ac3filter_eng.html#w98

As noted, the Westell 6100F does not come with any firewall settings turned on. I am using this modem as well. I currently have it configured in Bridge Mode (like the old DSL Modems) and it is connected to a wireless router. No DHCP enabled (but WPA2) on either side, using static IPs and DNS Servers. If you switch it to bridge mode, the light pattern will be different. You won't see an orange light anymore if you lose the network connection. Also, you will need to configure your router (or PC) to connect with the PPPoE settings in the modem. If you lose these you can get the numbers from support. Basically what they did was make it so the modem could start the PPPoE handshake on its own instead of relying on a single computer to do it. As far as OS requirements on networking hardware, with exception to IPv6 or other OS dependent technologies, the requirements are bound to two things only: 1. The software that comes with the product 2. The OSes that the technical support department will help you with.

Moved topic from Software Hangout and added poll. Unpinned the old thread. I use Windows ICF in combination with a hardware firewall.

If that does not help, this was posted in the WinPE forum a while ago:

Is this any ASPX anywhere, like multiple websites? Typically ASPX is handled server-side like PHP and HTML code given to the browser.

Have you tried Anytime Upgrade from the Start Menu?

In order to store an image for Windows 7, you need to sysprep and generalize it, and this should be done from Audit Mode. Then you can save it as a WIM. When you save the image, you only capture the OS volume, do not capture the System volume. When you restore, you create the system volume but do nothing with it. Then create the OS volume and drop the WIM on it. When the system boots, Sysprep will configure the system volume. I recommend you make the system volume the same size as it was when you captured the image originally.

That should not be a problem. My 2008 x64 WDS currently has 4 different boot images to choose from: 1. Atomic Bomb (WinPE 3.0 x86) ImageX Deployment Platform 2. BurnInTest (WinPE 2.1 x86) 3. Imagex (x86) (WinPE 2.1 x86) ImageX Deployment Platform 4. Imagex (x64) (WinPE 3.0 x64) ImageX Deployment Platform So the WDS does not care what architecture the boot image is. WDSNBP figures out what the client can handle. If the client is only x86 CPU (like Celerons or Atoms or older) it will only show 1-3. The x64 boot image only appears in the menu if the CPU can handle 64bit OS.

There is a ton of info about ActionScript online. It looks complicated at first but once you start using it, it is pretty easy. If you can't afford to purchase Flash, there are other alternatives such as Swish among others.

We have a (large) dedicated thread about RT7Lite here you can check out: I believe the correct term for "zillions" is "zounds..."

Is this the same thing that the USB drivers required to be installed first? Here is the instructions: http://www.technical-assistance.co.uk/kb/win98fe-usb-mass-storage-drivers.php

Yeah, both SecPol and GPO for power options was introduced in Vista. However that page you linked to had an ADM file you can create and import it. However you may need to have that ADM file on the XP Clients as well, I'm not really sure. But this is a supported option using POWERCFG with AD: http://support.microsoft.com/kb/915160

Merged topics. Same question, different page. Almost all games on websites are either written in Flash or Java. Almost none with SVG.

I haven't had any problems with the D510MO that I can remember... You may just need a new PSU or go get a green PSU like Antec's Earthwatts or similar type. My regular PC uses a Sparkle PSU and (as long as my IDE HDD is asleep) Its so quiet that I sometimes think its not even on!

I believe even AOL now allows you to connect via the Windows Dial-Up app and just open a browser without ever having to open the AOL software.

I haven't liked any Atoms yet so far that I've tried. I also wouldn't get a fanless because those things heat up faster than my PS3. I've burned my hand once on a fanless mini before. Right now, my current favorite is the AOpen DE965-HG, but its end of life and replaced by the DE45-HG. They are pretty quit even tho there is a fan in them. Plus they have built in HDMI as well, but there is a limitation as to it displaying properly on some resolutions (such as 1440x900) while on the desktop. Otherwise, get something with a really big fan OR use effective fan management in the BIOS of your system, which most people don't even set up. FWIW I use my Windows 98 PC as a "media server" to play my SNES games on...

Years ago, I broke a Frank Zappa CD into over 100 peices and taped it all back together and tried to play it. All it did was make an awful sound in the CD player. If you think about how CDs work (frickin' LASERS) the laser would hit any of the broken parts and reflect (or refract) the laser into some unknown direction instead of back into the lense. This is a reason why you can't read the disc because the laser probably isn't returning back to the lense when it gets to that part. If the lense does not get a laser beam back, it thinks there is no disc there. Just like TCP/IP!

Nope those didn't work either. Do you think it would be wise to try replacing those two VXD files with the Win98SE copies? It may be that this NIC needs Win98SE instead of FE. Oh I didn't try the 2.0 driver yet, I got sidetracked playing Dr Mario...

Welcome to the MSFN!

Opening up the topic now, as I have encountered a problem during deployment. They were: - started deploying from 64bit WinPE, durr MBR.EXE is 32bit app! - started deploy from x86 WinPE but didn't have NIC drivers installed - now the wrong partitions get hidden. Using the following: MBR.EXE 0 0 /h Hides the BOOT partition instead of the WINRE partition. I need to research the MBR.EXE commands to figure out why it did this. Also the second diskpart script above in deployment is tentatively on hold as it removes the drive letters for all the volumes, instead of R. The recovery partition works, with the only problem being that JPG I am using is the wrong size... OR setres isn't working... Update1: The problems with the XPe image not booting after deployment was caused by the XPe install itself. It was created with the idea the C drive was the first partition. It would not boot because the BOOT.INI was pointing to the wrong partition. Also the RAM Overlay is protecting the wrong partition as well. Going to remake the entire XPe install and start over. Also going to use GPO to remove the ability to delete the recovery partition from Windows. I am likely going to take out the 'nodefaultdriveletter' option as it does not seem to make any sort of difference.

This is a new project using WinPE v3.0 x86 to make a custom recovery partition along similar lines to this: That project ended up failing because XP support in the OEM Channel was finished. In this case, SoftThinks does not work on the target motherboard (nor on the new Wind models) and XPe is still supported in the channel. NOTE: As with previous topics, I am using the OPK Tools not WAIK. If you use WAIK the paths will be different for adding packages! The system we are going to be making this for is a 2 partition Windows XP Embedded (XPe) that is using the EWF bootloader and RAM Overlay on the Boot partition. The partition order I have planned will be as such: 0 0 WINRE 10240MB NTFS HIDDEN 0 1 BOOT 10240MB NTFS 0 2 STORAGE (remaining space) NTFS The previous attempt to use this for a WinRE replacement failed and was not solved. Hopefully I will not have these problems this time. This thread is to document my entire process. Here are the steps as I complete them: 1. Find all source files from previous project and arrange them into a new folder. The files are as follows... x:\windows\system32\fscommand\admin.exe (wrapper to open command prompt) x:\windows\system32\fscommand\restart.exe (program to restart the computer) x:\windows\system32\resources\custom.png (branding image) x:\windows\system32\resources\imagex.gif (animated gif to appear when recovering) x:\windows\system32\resources\setres.exe (sets screen resolution at boot) x:\windows\system32\resources\welcome.png x:\windows\system32\resources\winpe1024x768.jpg (image background of HTA) x:\windows\system32\full.hta (runs the full recovery) x:\windows\system32\full_diskpart.txt (for full recovery) x:\windows\system32\MBR.EXE (to hide drives, set F key for boot) x:\windows\system32\recovery1024x768.hta x:\windows\system32\repair.exe (runs a repair recovery) x:\windows\system32\setres.bat x:\windows\system32\winpe.bmp x:\windows\system32\winpeshl.ini 2. Rebrand winpe1024x768.jpg from original PNG file. 3. change various infos in the HTA files, specifically the name of the WIM. I will not document these changes now because I may end up changing them later. 4. Develop a ballpark Deployment workflow: [diskpart] sel vol c assign letter=j sel vol d assign letter=k sel disk 0 clean create part pri size=10240 assign letter=r format fs=ntfs quick label=WinRE create part pri size=10240 sel part 2 active assign letter=c format fs=ntfs quick label=Boot create part pri sel part 3 format fs=ntfs quick label=Storage assign letter=d [/diskpart] imagex /apply z:\folder\winre.wim 1 r: (the recovery partition) imagex /apply z:\folder\image.wim 1 c: (the OS partition) [diskpart] sel disk 0 sel vol r att vol set nodefaultdriveletter [/diskpart] mbr 0 /install selm 5 11 "Press F11 for Recovery" 0x7 0x17 mbr 0 0 /h 5. Capture the OS to the WDS Server. 6. Create the WinPE for the recovery partition: copype.cmd x86 c:\winpe_x86\S_RE xcopy c:\winpe_x86\S_RE\winpe.wim c:\winpe_x86\S_RE\ISO\sources\boot.wim Dism /Mount-Wim /WinFile:c:\winpe_x86\S_RE\ISO\sources\boot.wim /index:1 /MountDir:c:\winpe_x86\mount Dism /image:c:\winpe_x86\mount /Add-Package /PackagePath:"C:\Program Files\Windows OPK\tools\PETools\x86\WinPE_FPs\winpe-hta.cab" Dism /image:c:\winpe_x86\mount /Add-Package /PackagePath:"C:\Program Files\Windows OPK\tools\PETools\x86\WinPE_FPs\winpe-mdac.cab" Dism /image:c:\winpe_x86\mount /Add-Package /PackagePath:"C:\Program Files\Windows OPK\tools\PETools\x86\WinPE_FPs\winpe-scripting.cab" Dism /image:c:winpe_x86\mount /Add-Package /PackagePath:"C:\Program Files\Windows OPK\tools\PETools\x86\WinPE_FPs\winpe-wmi.cab" ** copy source files to mount\windows\system32 ** copy imagex from the Tools folder to system32 Dism /unmount-Wim /MountDir:c:\winpe_x86\mount /commit ** these files are the ones listed above. I will be doing this manually. 7. Test standard redeployment of the OS image (from step 5) onto a machine PASSED 8. Take the entire S_RE folder, copy MBR.EXE into the root. Copy the image.wim into the root, then: Imagex /capture c:\winpe_x86\S_RE c:\winpe_x86\winre.wim "WinRE" /compress fast 9. Test deployment from a 32bit WinPE, as the MBR.EXE is a 32bit app. *** more steps to follow/correct ***