System corruption is the worst that could happen to your Windows installation. We show you how to get Windows 10 back on track when suffering from BSODs, driver errors, or other unexplained issues.
To install a Fortran compiler (gFortran) to be used within the Code::Blocks IDE editor:
- Go to http://www.codeblocks.org/downloads
- Click on “Download the binary release”
- Click on “Windows 2000/XP/Vista/7//8”
- Click on “codeblocks-13.12mingw-setup.exe” to download from SourceForge.net
- Once downloaded (~100MB), install Code::Blocks IDE
- Full installation
- Destination “Program Files\CodeBlocks”
- “Do you want to run CodeBlocks now?” NO
- Start Code::Blocks from the shortcut on Desktop (or find in programs)
- When the IDE opens, go to “Settings” > “Compiler…”
- From the “Selected Compiler” option, select the “GNU Fortran Compiler” from the list
- From below, select “Toolchain executables” TAB
- Now check that the “Compilers installation directory” is set to the MinGW folder within Codeblocks
- Click Ok to close the options dialog, close Code::Blocks and re-open
- You should now be able to create and compile Fortran sources
Create a simple program (try .f90 or .f95 or .f) and compile:
print*, ‘Hello Fortran’
This is what you need to do if your Sage Accounts application has been corrupt and you can’t open it:
[text]Save your data files directory (Sage\Accounts)
Uninstall/completely remove the Sage installation
Re-install Sage Line 50 v9.x
Start Sage and complete the Company wizard with typical information
Copy the ACCDATA folder with contents to your new installed Sage
Start Sage and type your username (if one did exist when you created this data)
In some cases deleting the QUERY.DTA file from your data dir could help resolve the problems of login errors.
1. Install Visual Basic 6.0 (as Administrator)
Select custom install as follows:
Microsoft VB 6.0
2. Skip MSDN and all other install options (Source Safe, VC++, etc).
3. Uncheck registration and complete the setup.
4. Run VB (should run fine).
Note: VB should run fine, but in some cases may need the vb6.exe set with compatibility settings on:
path: c:\Program Files\Microsoft Visual Studio\VB98\vb6.exe
R-click > Properties > Compatibility and check the following:
Run in Windows XP mode
Disable Visual Thems
Disable Desktop Composition
Disable display scalling on high DPI settings
5. Install VB 6.0 SP6 if needed (there should be no issues and previous SPs are not needed).
Note: MDAC 2.5 are NOT needed for Windows Vista and later.
credits: Ask the FortyPoundHead
Creating a System Repair Disc can solve you a few boot problems encountered with Windows 7.
- Note the OS type (x32 or x64 bit)
- Insert an empty DVD into your drive
- Start > Programs > Maintenance > Create a System Repair Disc
- Select the drive and click on Create disc
Your repair disc is now ready to take over the world of corrupt booting Windows.
Note: The repair disc will support only the relative OS type i.e. 32 or 64 bit.
Note: Some business-line PCs may come with pre-installed non Windows OS like FreeDOS. These systems most probably use Linux as there main boot system and this is why a typical Windows installation may not boot properly in some cases.
Case: Install Windows 7 (64bit)
- Boot with a Windows 7 (64bit) setup DVD and install windows
- If your system loops on restart then you may need to do as follows:
- Boot with a Windows 7 (64bit) and select Repair System or Create a Windows 64bit System Repair Disc
- Select your operating system drive from what is listed
- Select Command Prompt and enter the following:
[bash]#Type the following to take you to MS DiskPart prompt
#The next command will select a disk to proceed
select disk 0
#Type the next command to see a list with system volumes.
#Note down the CD/DVD drive letter i.e. “E”
#The next command will take you back to command prompt
#Type the following to take you to drive E
#cd into the boot dir
#Type next command to reset the MBR
bootsect /nt60 SYS /mbr[/bash]