Data Corruption with DBF files on Windows 2008 server

Aug 09
2011

Recently I had several cases of missing records on a customers network: sometimes added records were missing, indices were corrupted or records incomplete.

Since this occurred with an application that on all other customers worked very well for years without any problems, I have researched until I found this link:

http://www.alaska-software.com/fixes/smb2/overview.shtm

This MSI adds three entries at

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanmanWorkstation\Parameters

In my application I have added the following code:

This solved the problem.

Save your old XP machine to your new Windows7 machine

Aug 04
2011

Basically, if you would save your old Windows XP machine to your new Windows 7 machine, the best thing you can do is to virtualize your old machine.

There are three cost-free virtualization solutions available:

I have tried all three, and I’m preferring VirtualBox for this because it seems to be the solution with the smallest overhead. VMware has become very fat, and also Virtual PC seems a little bit slow.

For the conversion of a living machine, there are only two handy tools available:

  • Sysinternals Disk2VHD tool creates a VHD image from a living machine (but please pay attention: there is a 127 GB limit) and can prepare it for use in MS Virtual PC ( live.sysinternals.com )
  • VMware vCenter Converter Standalone from VMware creates a complete VMware virtual machine (VMDK file) ( www.vmware.com )

The easiest way is using of VMware Converter to create a virtual machine and use these in VMware Player or server.

The Microsoft way can be easy also, but when there is something that does not work you can spend several hours until the entire thing works (there are two limits: 127 GB max for the virtual disk, and as host you need a Windows 7 Professional or Ultimate, no Home).

The personally preferred solution is to use VMware Converter to create a VMDK file, and use this then in VirtualBox, and this will be described more detailled here:

  • before launching the conversion with VMware Converter, you need to apply the MergeIDE tool (you can find the link here )
  • convert the machine saving the files to a network or USB drive
  • copy the virtual machine to the host machine
  • create the new virtual machine using the copied virtual machine files
  • in the settings of the virtual machine, you need these settings:
    enable APIC

    Enable APIC in VirtualBox

    select PIIX4 als IDE controller

    Enable PIIX4 in VirtualBox

  • After this you can try to start your machine. Unfortunately, probably you will have to re-activate Windows because of the “hardware” change.
    It is not so easy because before activating Windows over the network, you will need to make the network to work.
    If you are lucky, you have 3 days to do this, but on a Fujitsu Siemens machine (with a BIOS locked XP license) the only way to logon was a prior activation over the phone: the network can be configured only after login, but without activation a login was impossible.
  • if your machine was member of a Windows domain, its will be the best to configure the network as passthrough, not as NAT, because otherwise the domain controller cannot be reached.

Links:

Howto convert from VMware to VirtualBox
VMware Download Center
Howto migrate a Windows machine to VirtualBox