Understanding File Shredding and the Wipe Disk Process
RecoverySoft / June 13, 2018

File shredding, which is also referred to as file wiping or as wipe disk, is a process that involves securely deleting a computer file. Through file shredding, the information that was saved on the file cannot be retrieved by any means. There are a couple methods you can use to shred a file. One of these methods is to use special file shredder software, while the other method is to write a “secure delete” demand. If you simply write a “delete” command, the saved information can be retrieved with the right software and computer skills. This is because it is considered a waste of resources to completely delete a file. Therefore, when a file is deleted within an operating system, the space previously occupied by the saved information will simply be marked as a available and the file is removed from the directory. The actual contents, however, remain on the disk. This also makes it possible for files that have been deleted to be restored and recovered. This can easily be accomplished with the “undelete” command. In order to conduct file shredding, the file must actually be overwritten several times. As such, a file that has undergone defragmentation cannot be…

Microsoft Great Plains: Customization Upgrade & Recovery – Visual Studio VB 6.0
RecoverySoft / May 2, 2018

Microsoft Great Plains, former Great Plains Software Dynamics, eEnterprise has very long, about 12 years customization & integration history. In earlier 1990th – the customization tool was mostly Great Plains Dexterity, later on when Great Plains was successfully moved to MS SQL Server 6.5, 7.0 and 2000 – we see more historical custom projects done in SQL stored procedures and front ends coded in VB in Visual Studio 6.0. This was probably wise and natural choice in that time (around 1997-2001), but if you consider Microsoft move to .Net platform and reshaping its own programming environments (ADO, OLE, VB, etc) – you would nowdays rather be nervous disgusting on VB 6.0 custom front end, calling stored procs via ADO. Let's consider your options: o Upgrade to .Net. As natural it might sound and look, however it might not be feasible. The reason is – .Net is the whole revolution to Windows object model (or its its introduction, somewhat more revolutionary, than J2EE / EJB / Java). Your old VB code is not object oriented in the sense of .Net and majority of technologies are now obsolete or in phase out mode o Move Front End to Web Application. Or recreate…