I want to run tally on Windows XP Pro but whenever I try it gives me an error message as the files are not enough to run it. Can anyone help me to solve this problem?
Printable View
I want to run tally on Windows XP Pro but whenever I try it gives me an error message as the files are not enough to run it. Can anyone help me to solve this problem?
The only solution to this problem is downgrade to windows 98
Tried that option but no luck
Which version are you using? If it is 4.5 then open the file c:\config.sys with notepad and add this line to the end:
FILES=20
Reboot and try again. You may need to tweak this number by trial and error.
You can also run tally 4.5 on XP through virtual pc 2004.
Download, Install:
- Download the free Virtual PC from the Microsoft's site and the Win98 Bootdisk ISO image from AllBootDisks.
- Install the Virtual PC 2004 on to your system.
- After installation, start the program and start by creating a new Virtual Machine by using the Virtual Machine Wizard, name this "MS DOS Machine" or "Tally Machine". Select OS as "MS DOS".
- During the process, the Wizard will ask whether you want an existing virtual hard disk, or a new virtual hard disk. Select "new virtual hard disk". Enter a name for the file, something like "Tally.vfd".
- Save the settings.
Format, Prepare and Get ready:
- Start this newly created virtual machine by selecting it and clicking Start button. After few seconds of bios output, the screen will say unable to find a bootable device. This is normal, since we haven't made our virtual hard disk bootable.
- Now click on CD menu and select the "Capture ISO image ..." option. This will popup a file selection dialong box. Select the ISO image that we have downloaded from AllBootDisks.
- Now restart the virtual machine by selecting the Action menu and select the "Ctrl+Alt+Del". After restart the VM (virtual machine) will boot using the Windows 98 boot disk ISO we just loaded and come to A:> prompt.
- Now run the FDISK program and create the "Primary DOS partition" on the drive. After exiting FDISK, restart the VM and again boot from the CD again.
- Now when at the A:> prompt, issue a format command with parameters something like this: format c:/u/s/v:TALLY
- After the format is complete, switch to C: drive, create a directory by the name of DOS, by issuing the command MD C:\DOS
- Now copy all the files from the A: drive or the bootable CD drive to the C:\DOS directory.
- Select the "Release CD" from the CD menu and restart the VM.
- Now the machine would have booted from the C drive and come to a C:> prompt.
- Now select the "Capture Floppy Disk Image" option from the Floppy menu. This would open up a file selection dialog box. Goto the directory where you had installed the Virtual PC. Should be something like this C:\Program Files\Microsoft Virtual PC; Now in this directory there should be directory by the name Virtual Machine Additions; Select this and then select the file with the name of DOS Virtual Machine Additions.vfd; You have just loaded a virtual floppy.
- Switch to A:> drive. And run the command DOSADD.BAT. This will add the required additional features like folder share, etc to this Dos VM.
- Select the "Release Floppy" from the Floppy menu and restart the VM.
Installing and Running Tally:
- After the restart, the DOS will load additional programs. After the booting is done; right-click the "Folder Icon" on the bottom status bar and select "Share Folder" option. Select the folder in which your tally installation or installed folder is and select the drive letter as Z.
- Copy the data from the Z drive to the C drive by creating appropriate folder; After its done, switch to the C:\TALLY folder and start tally and viola, you are done.
I'm using VPC for running Tally 4.5. When I run Tally, it starts in monochrome mode and flashes "Working" for about thirty-forty seconds. After the delay, it goes to colour mode and displays the menu. The delay occurs ONLY if there is a drive which is mapped to a network drive (NET USE drive) or a drive which is used for a shared folder (VPC Share folder). It happens even if Tally does not use any of these drives and the "Data" folder is in the VHD itself (booting VHD or any other VHD). Just the presence of a mapped/shared drive considerably slows down the startup of Tally irrespective of whether Tally uses that drive or not. Why does this happen? What does happen when Tally starts? What is the solution?