- Dell PowerEdge 2600
- Toshiba SD-C2502 DVD-ROM Drive
When you try and install an edition of NT 6 x86 on a Dell PowerEdge 2600 using self-created DVD media (DVD-R, DVD+R, DVD-RW, DVD+RW) the setup program takes a very long time to start and after around 30 minutes of “Expanding files” sitting on 0% setup fails with the error code 0x80070022.
The problem isn’t an incompatibility with the systems and NT6, it’s most likely the DVD ROM drive itself. You should of course check to make sure that the DVD-R(W) media that you are using is integral and hasn’t failed to burn properly. If the media works fine on other systems then check to see if the machine has a Toshiba SD-C2502 drive.
If it does then it is probably manufactured in or around August 2002 using firmware 1D13 (dates 03/08/2001) before all of the DVD media specifications were standardised. Dell unhelpfully neglected to supply the firmware update for the drive to support improved media compatibility. As you may have guessed, the media can get you into the setup program, but the slow speed is because of an increased number of forced read errors.
The good news is that there is firmware available that may resolve this for you. Although Dell neglected to make it available on their PowerEdge support section, the drive is a plain old IDE drive, one that Dell used on a number of other systems. To be precise:
- Inspiron 2500
- Inspiron 2100
- Inspiron 4100
- Inspiron 8000
- Inspiron 8100
- Inspiron 2600
- Inspiron 8200
- Inspiron 2650
- Inspiron 4150
- Latitude C500
- Latitude C510
- Latitude C540
- Latitude V710
- Latitude LS
- Latitude C400
- Latitude C600
- Latitude C610
- Latitude C800
- Latitude C810
- Latitude L400
- Latitude C640
- Latitude V740
- OptiPlex GX150
- OptiPlex GX240
- OptiPlex GX260
- OptiPlex GX260N
- Dell Precision Mobile WorkStation M50
So if you head to the support pages on Dell for one of those you will find the SD-C2502 firmware update which addresses:
This firmware addresses various readability related issues.
The firmware at shipping is 1D13, this updates it to 1D23 and will hopefully get you installing. If you want to search Dell Support for the file name look for br59016.exe
If that doesn’t fix it, it’s a standard IDE drive, simply grab one from any > 2003 laptop and you should be good to go.
- Windows Vista
- Windows Server 2008, R2
- Windows 7
Take the hypothetical situation: Windows 7 fails to boot, you don’t want to lose your user data so you install 7 onto a clean partition. However your old user profile is associated with the random SAM ID from the old installation and the new Windows installation cannot mount the profile. You can copy your data files back over, but you really don’t want to configure the start menu settings for the 1,000,000th time.
Or how about: Your only domain controller failed leaving disassociated roaming profiles on a roaming profile share and you want to recover as much of the user settings and data as possible for use on the newly build AD forest. <– That actually happened to Matt, hence I day dreamed this up.
NT user accounts are associated to a Security Account Manager (SAM) ID. The SAM ID is Windows’s SAM or the Active Directory domain user services way of identifying a user, in effect the SAM ID is a super key that identifies a user account on a windows system, acting as a GUID for that profile.
The user name itself is irrelevant and plays no part in identifying the user account apart from being used to performing a reverse lookup to get to the SAM ID, on which Windows bases its logon activities and security token generation in AD.
When you reinstall Windows, the new installation has no awareness of any of the accounts, so if you copy the profiles back into the Windows users directory you will be unable to re-associate that profile with the local SAM database.
The simplest way of restoring user data and crucially environment settings (such as desktop wallpaper, window settings and the like) is to follow this process:
- Create a new user account for the user you want to migrate onto the new domain/installation
- Set the accounts roaming profile settings (if dealing with a roaming profile)
- Logon to the machine with Administrator rights
- Load Regedit
- Click on HKEY_USERS
- From the File menu, select Load Hive…
- Browse to the NTUser.dat from the previous install/roaming profile for the profile that you are trying to recover and click OK e.g.
- When prompted for a name just enter temp and click OK
- Expand and click on:
- From File select export and save the export file as:
- From File, select Unload Hive…
- Exit Regedit
- Open c:\temp.reg
- From the Edit menu select Replace…
- In Find What: enter:
In Replace With: enter:
Press Replace All
- Save the reg file and exit notepad
- Log off of Administrator
- Log on as the new user
- Double click on c:\temp.reg and import the reg file into the new (completely default) user account. If you are using a system with UAC you will need to import the reg file using an administrators account.
- Immediately log off
- Log back in as Administrator
- Go to the recovered profile folder e.g.
- Select all files in the folder apart from NTUser.dat, NTUser.ini and NTUser.dat.log and copy them
- Paste the data into the new user profile e.g.
- The data and the profile settings have now been recovered. Logging back in as the recovered user will restore much of the user profile and all of their data.
Note: It may be necessary to reset folder permissions and ownership on all of the files pasted into the folder to match that of the new user account.
Thanks to Matt Gillard of MGComputing for some testing of my theory.
- Windows NT 4.0
- Windows 2000
- Windows XP
- Windows Server 2003
- Windows Vista
- Windows Server 2008
- Windows 7
When you attempt to connect to a Microsoft Access database using the ODBC provider Microsoft.Jet.OLEDB.4.0 you receive the error message:
There are a number of issues that can cause this error, they are poorly documented elsewhere online but the information is there; connection string, registry values slightly offset and so fourth. This document deals with one specific issue which is related to the idea of this being caused by an incompatible type value.
The chances of you running into this are quite extreme, however it is an issue in JET (Microsoft Access) that doesn’t exist in Microsoft SQL Server and thus if you are dealing with code transitioning you may want to know about the problem in this very extreme and unlikely situation.
You shouldn’t need to reboot to solve the problem, it didn’t in my case. However, if nothing happens do restart before progressing to the next step.
The following SQL Statement will execute on Microsoft SQL Server and return a RecordSet however the same SQL on JET 4.0 will result in the error message outlined above.
No, it isn’t the T-SQL LEFT() statement that is the problem. The issue lies in the “null AS studentPhotoBLOB”.
The idea behind this is that space has been reserved in the record set. Why would you want to do this? If you want to drop the record set directly into an array, then ADO can do this for you using the GetRecords method. However if you want to change the structure you have to re-parse the array and relocate the data into a new structure. You can inset a null named record and use the space in the GetRecords array later for other purposes.
The problem here is that null is not a data type that is supported by JET; it is supported by Microsoft SQL Server however.
The simplest way to remedy the situation is to either change the SQL or dynamically detect JET to change the variable type to a commonly supported data type, for example a String.
This is naughty, however in a weak typed language such as ASP it isn’t a real problem given the situation outlined above. The use of ” instead of null forces the data type of the column into a string and thus it can be parsed by JET.
- Windows Vista SP1
- Windows Server 2008
So, you get fed-up of trying to get PCI sound cards working under Vista and opted for the integrated sound CPU clogging solution?! I don’t blame you.
The P4S333 may be old kit, but it’s a solid motherboard, very much Vista capable with the right upper end P4 and enough RAM, particularly if you flashed the P4S333 with the P4S533’s BIOS to make use of the 533 MHz FSB. The difficulty we have is however in that the C-Media CMI8738 AC97′ chip that the board uses cannot be matched to any of Windows Updates hardware ID’s and Asus, naturally, do not offer a Vista driver.
Thankfully, C-Media do provide generic drivers, and there is a January 2009 driver release for the CMI8738 as of writing. The driver does work once you get it out of the RAR file, however:
- The driver does not have the necessary hardware ID to install automatically against the customised chip on the P4S333 / P4S533
- The driver is not digitally signed
Despite that, I’ve not seen any problems with it, and despite the CPU connotations, it got rid of irritating buzzing that the Creative Labs Sound Blaster Live! 5.1 was causing with the useless Vista driver set.
Very simply, you need to manually install the driver.
- Download the latest CMI8738 driver from C-Media (http://www.cmedia.com.tw/). As of writing the driver version was 8.17.33 and it worked a treat
- Deflate the RAR into the file system
- Open the Control Panel
- Open the Device Manager
- Find the uninstalled multimedia device in the Other Devices section, right click, Update Driver Software
- Click Browse my computer for driver software
- Click let me pick from a list of device drivers on my computer
- Hit the have disk button
- Browse to the path that you inflated the RAR file to, for example if you inflated the RAR file to c:\temp\ you want to browse to the following location:
c:\temp\PCI-8738-090109-8.17.33(Vista3264-RC-01)\SoftwareDriver\driverNote that if the driver version you are using is newer, then the version in the file name will clearly be different. Ultimately however you are looking to point to the SoftwareDriver\driver folder (there are several INF’s and some CAT files in here)
- In the manufacturer list from the available select:
- From the Model list select:
C-Media PCI Audio Device
- Click Next
- Windows will notify you that the driver has not been digitally signed. You’re going to have to tough this one out I’m afraid and install it.
- At that point the audio should just start working.